[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BZM721VDKENSCXM6DMA3QJ":3,"skill-same:01M7BZM721VDKENSCXM6DMA3QJ":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BZM721VDKENSCXM6DMA3QJ","roblox-physics",null,"Design or review Roblox assemblies, constraints, collision, hit detection, and network ownership.","HungryKelvin123\u002Fdstack","HungryKelvin123","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F195409251?v=4","01M7BZFDP7VJGY9KM0GNMKK9AC","hungry","01M7BZFDPSBC011AZHFTCSJR2A",2,"MIT","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Froblox-physics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: roblox-physics\ndescription: \"Design or review Roblox assemblies, constraints, collision, hit detection, and network ownership.\"\n---\n\n# Roblox physics\n\nRead [`..\u002F..\u002Freferences\u002Froblox-engineering.md`](..\u002F..\u002Freferences\u002Froblox-engineering.md). Inspect the authored hierarchy, assemblies, roots, anchoring, attachments, constraints, collision groups, and current ownership code before changing behavior.\n\n## Treat simulation as distributed and untrusted\n\n- Decide network ownership at the assembly level as both a responsiveness and authority choice. Client ownership reduces input latency and server work, but the client can manipulate its simulation.\n- Keep gameplay-critical assemblies server-owned when practical. For responsive player-controlled physics, assign ownership deliberately and validate server-observed position, speed, state transitions, and outcomes within game-specific tolerances.\n- Reapply or release explicit ownership when seats, characters, tools, assemblies, or round state change. Anchoring and reconnecting parts can change the ownership model.\n- Do not treat `Touched` alone as proof of authoritative damage, collection, or completion. Confirm server-side identity, spatial plausibility, state, cooldown, and duplicate behavior; use an appropriate ray or swept spatial query for fast motion.\n- Prefer attachments and constraints for simulated mechanisms. Apply forces or impulses to the intended assembly instead of fighting physics with repeated per-frame transforms or velocity assignments.\n- Make collision groups and query filters explicit. Exclude the source assembly, validate returned instances and ancestry, and separate physical collision from detection when gameplay requires different rules.\n- Bound active simulated assemblies, query frequency, and per-frame work. Measure server physics cost, replication, and mobile client behavior before optimizing.\n\n## Deliverable\n\nState the assembly root, owner through each lifecycle state, authority checks, collision and query rules, constraint model, cleanup, and failure behavior. Verify pure hit-validation and state-transition logic locally. Give the user exact Studio checks for ownership visualization, multiple clients, latency, reset, and high-speed contact; never invoke the playtest through MCP.\n","# Roblox physics\n\nRead [`..\u002F..\u002Freferences\u002Froblox-engineering.md`](..\u002F..\u002Freferences\u002Froblox-engineering.md). Inspect the authored hierarchy, assemblies, roots, anchoring, attachments, constraints, collision groups, and current ownership code before changing behavior.\n\n## Treat simulation as distributed and untrusted\n\n- Decide network ownership at the assembly level as both a responsiveness and authority choice. Client ownership reduces input latency and server work, but the client can manipulate its simulation.\n- Keep gameplay-critical assemblies server-owned when practical. For responsive player-controlled physics, assign ownership deliberately and validate server-observed position, speed, state transitions, and outcomes within game-specific tolerances.\n- Reapply or release explicit ownership when seats, characters, tools, assemblies, or round state change. Anchoring and reconnecting parts can change the ownership model.\n- Do not treat `Touched` alone as proof of authoritative damage, collection, or completion. Confirm server-side identity, spatial plausibility, state, cooldown, and duplicate behavior; use an appropriate ray or swept spatial query for fast motion.\n- Prefer attachments and constraints for simulated mechanisms. Apply forces or impulses to the intended assembly instead of fighting physics with repeated per-frame transforms or velocity assignments.\n- Make collision groups and query filters explicit. Exclude the source assembly, validate returned instances and ancestry, and separate physical collision from detection when gameplay requires different rules.\n- Bound active simulated assemblies, query frequency, and per-frame work. Measure server physics cost, replication, and mobile client behavior before optimizing.\n\n## Deliverable\n\nState the assembly root, owner through each lifecycle state, authority checks, collision and query rules, constraint model, cleanup, and failure behavior. Verify pure hit-validation and state-transition logic locally. Give the user exact Studio checks for ownership visualization, multiple clients, latency, reset, and high-speed contact; never invoke the playtest through MCP.\n",{"name":5,"description":7},"main","98fe3fc28d9374ab74cd7f9040e2c6faed5fda78","plugins\u002Fdstack\u002Fskills\u002Froblox-physics",0,"https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack","https:\u002F\u002Fgithub.com\u002FHungryKelvin123","playgreenshell.com","luau","2026-09-04 11:43:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add HungryKelvin123\u002Fdstack --skill roblox-physics",{"tool":39,"command":40},"bunx","bunx skills add HungryKelvin123\u002Fdstack --skill roblox-physics",{"tool":42,"command":43},"pnpm","pnpm dlx skills add HungryKelvin123\u002Fdstack --skill roblox-physics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Froblox-physics\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",238,"https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Froblox-physics\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7BZNBM5WZXTYJC028VGJPWF","why","Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7BZN9KES3TZAZ5VJRKRET78","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7BZN61NNQ5XZD5D3ZR26R1S","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7BZN2RWWRD0F30HNCYEZ5YH","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BZN0A2K431TFETWP5FE95R","tdd","Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BZMW9WKXQ1JDAS78B95A5Q","swarm","Coordinate independent routine execution or exploration batches and return one reviewed report. Use for $swarm or large separable work that justifies parallel overhead.","https:\u002F\u002Fgithub.com\u002FHungryKelvin123\u002Fdstack\u002Fblob\u002Fmain\u002Fplugins\u002Fdstack\u002Fskills\u002Fswarm\u002FSKILL.md",[],[]]