[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M780EYF176V19ZPJJJSHKS01":3,"skill-same:01M780EYF176V19ZPJJJSHKS01":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M780EYF176V19ZPJJJSHKS01","scrapbot-feature-development",null,"Use when adding, changing, documenting, or auditing Scrapbot engine features, public APIs, ECS components, rendering, scripting, native extensions, examples, or project tooling. Covers cross-surface implementation, component documentation, generated types, and verification expectations.","scrapbotengine\u002Fscrapbot","scrapbotengine","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F299915117?v=4","01M780DWPZF6KY1RNA11SYVNWG","01M780DWQSDY0XMHV21KGMAVX6",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-feature-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scrapbot-feature-development\ndescription: Use when adding, changing, documenting, or auditing Scrapbot engine features, public APIs, ECS components, rendering, scripting, native extensions, examples, or project tooling. Covers cross-surface implementation, component documentation, generated types, and verification expectations.\n---\n\n# Scrapbot Feature Development\n\n## Before Editing\n\n1. Read the relevant roadmap section in `README.md`, open items in `docs\u002FTODO.md`, and related ADRs\u002FFDRs.\n2. Trace the existing implementation end to end before choosing a design. Prefer established package boundaries and public APIs.\n3. Call out material choices when multiple user-visible or architectural options remain. Breaking changes are acceptable, but accidental surface divergence is not.\n4. Inspect the worktree and assigned scope. In multi-agent work, keep writers file-disjoint and leave shared registries, generated files, indexes, and integration checks to an explicit integration owner.\n5. Read `docs\u002Farchitecture\u002FINDEX.md` and use the `scrapbot-architecture-inventory` skill when the work changes systems, components, ownership or invalidation, major data flows, or package responsibilities.\n\n## Public Surface Audit\n\nFor every feature, decide explicitly which layers it affects:\n\n- Core Odin implementation and ECS\u002Fruntime behavior.\n- Luau runtime bindings and generated Luau declarations.\n- Project-local Odin extension wrapper and raw extension ABI.\n- Scene\u002Fproject file parsing and validation.\n- Standalone project-resource schemas, UUID references, registry lifetimes, and hot reload.\n- CLI behavior and diagnostics.\n- Example projects.\n- README, TODO, ADRs, FDRs, and documentation website.\n\nDo not assume every feature belongs on every surface. When one surface intentionally trails another, record that decision or follow-up rather than overlooking it.\n\nFor project-resource work, keep persistent identity separate from runtime storage: authored resources live outside ECS, scene\u002Fproject files reference stable UUIDs, registries expose generational handles and versions, and ECS components hold resolved handles. Audit recursive discovery, duplicate\u002Freference validation, disappearance\u002Freappearance, packaging, hot reload, editor create\u002Fduplicate\u002Frename\u002Fmove\u002Fdelete, reference-aware deletion, Save\u002FRevert\u002FUndo\u002FRedo, and the distinction between authored and transient runtime resources. Lifecycle edits remain in-memory authoring until explicit Save; Save must derive create\u002Fwrite\u002Fdelete operations from the disk baseline and commit them through the recoverable project transaction.\n\nProject-resource, playback, persistence, world-replacement, and hot-reload changes must update `docs\u002Farchitecture\u002Fresources.md` and\u002For `docs\u002Farchitecture\u002Flifecycle.md`. Record actual rollback boundaries: do not describe a replacement as transactional when a registry or other owner mutates before candidate validation and is not restored on failure.\n\nFor ECS UI work, also use the `scrapbot-ui-development` skill. The editor must remain a consumer of the public UI contract, and a public field is incomplete until every applicable authoring and runtime surface agrees.\n\nFor spatial hierarchy work, keep `scrapbot.transform.parent` UUID-based and local TRS as the only authored pose. Keep display order independent from live ECS storage handles; audit scene-block ordering, structural Save, and Undo\u002FRedo when adding hierarchy reorder behavior. Also audit scene validation, Luau and native writeback, world-transform consumers (render instances, cameras, lights, picking, and gizmos), cycle rejection, parent removal, and world-pose-preserving editor reparent Undo\u002FRedo. Use `tests\u002Ffixtures\u002Fui\u002Fscene-hierarchy.json` for the visual tree companion; semantic drags can target the top\u002Fcenter\u002Fbottom of destination rows.\n\n## Generated Luau Types\n\nWhen changing built-in components, Luau APIs, query types, or component schemas:\n\n1. Update the canonical type generator in `src\u002Fscrapbot\u002Fcomponent\u002Fluau_types.odin`.\n2. Build the CLI.\n3. Run `bin\u002Fscrapbot check \u003Cexample>` for every affected example.\n4. Run `mise luau-workspace-types` when an example schema or shared Luau API changes. It refreshes the tracked repository-wide declaration aggregate used by the root VS Code workspace; project-local generated state remains ignored and must not be hand-edited or committed.\n5. Inspect generated `.scrapbot\u002Ftypes\u002Fscrapbot.d.luau` output and run the Luau analyzer through the normal test suite.\n\nNever hand-edit generated example declarations without changing their generator.\n\n## Verification And Documentation\n\n- Add focused unit and integration tests at the changed ownership boundaries.\n- Use the `scrapbot-testing` skill for full-suite, example, WGPU, framegrab, and visual checks.\n- Renderer work whose output can change across frames is incomplete until a consecutive capture\n  range has been inspected. A successful final frame does not verify streaming, LOD, temporal\n  history, animation, hot reload, or other transitional behavior.\n- Update behavioral FDRs when a feature's supported behavior or design changes.\n- Add or amend an ADR only for a durable architectural decision.\n- Keep `README.md`, `docs\u002FTODO.md`, examples, and the documentation website synchronized with shipped behavior.\n- Keep `docs\u002Farchitecture\u002F` synchronized with architectural surfaces and run its inventory audit when applicable.\n- Finish with `mise test`, `git diff --check`, and any feature-specific verification.\n- When integrating delegated work, review the combined diff rather than trusting per-agent test reports; cross-surface omissions usually appear only at integration time.\n\n## Documentation Audits\n\nTreat `src\u002Fscrapbot\u002Fcomponent\u002Fregistry.odin` as the source of truth for machine component facts. Treat `docs\u002Farchitecture\u002Fcomponents.md` as the complete engineering directory and `docs-website\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcomponents.md` as the canonical public usage reference. Do not duplicate internal ownership\u002Finvalidation prose into the website or exhaustive public field\u002Fdefault documentation into the architecture directory.\n\nWhen adding, removing, renaming, or changing an engine component:\n\n1. Update the canonical component page with its registry name, public fields, scene name, Luau handle, native descriptor\u002Faccess pattern, defaults, constraints, ownership, and renderer-only behavior where applicable.\n2. Update the component's standardized entry in `docs\u002Farchitecture\u002Fcomponents.md` when its storage, lifecycle, producers, consumers, invalidation, surfaces, or implementation\u002Ftest anchors change.\n3. Run both `node .agents\u002Fskills\u002Fscrapbot-feature-development\u002Fscripts\u002Fcheck_component_docs.mjs` and `node .agents\u002Fskills\u002Fscrapbot-architecture-inventory\u002Fscripts\u002Fcheck_inventory.mjs`.\n4. Check `reference\u002Fproject-files.md`, `reference\u002Fluau-api.md`, `guides\u002Fnative-extensions.md`, and `guides\u002Fecs-ui.md` only for surface-specific behavior. Link to the component page instead of duplicating exhaustive field inventories.\n5. Audit both `docs\u002FGLOSSARY.md` and the public website glossary for stale feature-state language.\n6. Build the documentation website with `pnpm run build` from `docs-website\u002F`.\n","# Scrapbot Feature Development\n\n## Before Editing\n\n1. Read the relevant roadmap section in `README.md`, open items in `docs\u002FTODO.md`, and related ADRs\u002FFDRs.\n2. Trace the existing implementation end to end before choosing a design. Prefer established package boundaries and public APIs.\n3. Call out material choices when multiple user-visible or architectural options remain. Breaking changes are acceptable, but accidental surface divergence is not.\n4. Inspect the worktree and assigned scope. In multi-agent work, keep writers file-disjoint and leave shared registries, generated files, indexes, and integration checks to an explicit integration owner.\n5. Read `docs\u002Farchitecture\u002FINDEX.md` and use the `scrapbot-architecture-inventory` skill when the work changes systems, components, ownership or invalidation, major data flows, or package responsibilities.\n\n## Public Surface Audit\n\nFor every feature, decide explicitly which layers it affects:\n\n- Core Odin implementation and ECS\u002Fruntime behavior.\n- Luau runtime bindings and generated Luau declarations.\n- Project-local Odin extension wrapper and raw extension ABI.\n- Scene\u002Fproject file parsing and validation.\n- Standalone project-resource schemas, UUID references, registry lifetimes, and hot reload.\n- CLI behavior and diagnostics.\n- Example projects.\n- README, TODO, ADRs, FDRs, and documentation website.\n\nDo not assume every feature belongs on every surface. When one surface intentionally trails another, record that decision or follow-up rather than overlooking it.\n\nFor project-resource work, keep persistent identity separate from runtime storage: authored resources live outside ECS, scene\u002Fproject files reference stable UUIDs, registries expose generational handles and versions, and ECS components hold resolved handles. Audit recursive discovery, duplicate\u002Freference validation, disappearance\u002Freappearance, packaging, hot reload, editor create\u002Fduplicate\u002Frename\u002Fmove\u002Fdelete, reference-aware deletion, Save\u002FRevert\u002FUndo\u002FRedo, and the distinction between authored and transient runtime resources. Lifecycle edits remain in-memory authoring until explicit Save; Save must derive create\u002Fwrite\u002Fdelete operations from the disk baseline and commit them through the recoverable project transaction.\n\nProject-resource, playback, persistence, world-replacement, and hot-reload changes must update `docs\u002Farchitecture\u002Fresources.md` and\u002For `docs\u002Farchitecture\u002Flifecycle.md`. Record actual rollback boundaries: do not describe a replacement as transactional when a registry or other owner mutates before candidate validation and is not restored on failure.\n\nFor ECS UI work, also use the `scrapbot-ui-development` skill. The editor must remain a consumer of the public UI contract, and a public field is incomplete until every applicable authoring and runtime surface agrees.\n\nFor spatial hierarchy work, keep `scrapbot.transform.parent` UUID-based and local TRS as the only authored pose. Keep display order independent from live ECS storage handles; audit scene-block ordering, structural Save, and Undo\u002FRedo when adding hierarchy reorder behavior. Also audit scene validation, Luau and native writeback, world-transform consumers (render instances, cameras, lights, picking, and gizmos), cycle rejection, parent removal, and world-pose-preserving editor reparent Undo\u002FRedo. Use `tests\u002Ffixtures\u002Fui\u002Fscene-hierarchy.json` for the visual tree companion; semantic drags can target the top\u002Fcenter\u002Fbottom of destination rows.\n\n## Generated Luau Types\n\nWhen changing built-in components, Luau APIs, query types, or component schemas:\n\n1. Update the canonical type generator in `src\u002Fscrapbot\u002Fcomponent\u002Fluau_types.odin`.\n2. Build the CLI.\n3. Run `bin\u002Fscrapbot check \u003Cexample>` for every affected example.\n4. Run `mise luau-workspace-types` when an example schema or shared Luau API changes. It refreshes the tracked repository-wide declaration aggregate used by the root VS Code workspace; project-local generated state remains ignored and must not be hand-edited or committed.\n5. Inspect generated `.scrapbot\u002Ftypes\u002Fscrapbot.d.luau` output and run the Luau analyzer through the normal test suite.\n\nNever hand-edit generated example declarations without changing their generator.\n\n## Verification And Documentation\n\n- Add focused unit and integration tests at the changed ownership boundaries.\n- Use the `scrapbot-testing` skill for full-suite, example, WGPU, framegrab, and visual checks.\n- Renderer work whose output can change across frames is incomplete until a consecutive capture\n  range has been inspected. A successful final frame does not verify streaming, LOD, temporal\n  history, animation, hot reload, or other transitional behavior.\n- Update behavioral FDRs when a feature's supported behavior or design changes.\n- Add or amend an ADR only for a durable architectural decision.\n- Keep `README.md`, `docs\u002FTODO.md`, examples, and the documentation website synchronized with shipped behavior.\n- Keep `docs\u002Farchitecture\u002F` synchronized with architectural surfaces and run its inventory audit when applicable.\n- Finish with `mise test`, `git diff --check`, and any feature-specific verification.\n- When integrating delegated work, review the combined diff rather than trusting per-agent test reports; cross-surface omissions usually appear only at integration time.\n\n## Documentation Audits\n\nTreat `src\u002Fscrapbot\u002Fcomponent\u002Fregistry.odin` as the source of truth for machine component facts. Treat `docs\u002Farchitecture\u002Fcomponents.md` as the complete engineering directory and `docs-website\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fcomponents.md` as the canonical public usage reference. Do not duplicate internal ownership\u002Finvalidation prose into the website or exhaustive public field\u002Fdefault documentation into the architecture directory.\n\nWhen adding, removing, renaming, or changing an engine component:\n\n1. Update the canonical component page with its registry name, public fields, scene name, Luau handle, native descriptor\u002Faccess pattern, defaults, constraints, ownership, and renderer-only behavior where applicable.\n2. Update the component's standardized entry in `docs\u002Farchitecture\u002Fcomponents.md` when its storage, lifecycle, producers, consumers, invalidation, surfaces, or implementation\u002Ftest anchors change.\n3. Run both `node .agents\u002Fskills\u002Fscrapbot-feature-development\u002Fscripts\u002Fcheck_component_docs.mjs` and `node .agents\u002Fskills\u002Fscrapbot-architecture-inventory\u002Fscripts\u002Fcheck_inventory.mjs`.\n4. Check `reference\u002Fproject-files.md`, `reference\u002Fluau-api.md`, `guides\u002Fnative-extensions.md`, and `guides\u002Fecs-ui.md` only for surface-specific behavior. Link to the component page instead of duplicating exhaustive field inventories.\n5. Audit both `docs\u002FGLOSSARY.md` and the public website glossary for stale feature-state language.\n6. Build the documentation website with `pnpm run build` from `docs-website\u002F`.\n",{"name":5,"description":7},"main","9127ecf5d9735db333cd08b4d01de9f48208df57",".agents\u002Fskills\u002Fscrapbot-feature-development",1,"https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot","https:\u002F\u002Fscrapbot.dev","https:\u002F\u002Fgithub.com\u002Fscrapbotengine","2026-10-07 16:25:44",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add scrapbotengine\u002Fscrapbot --skill scrapbot-feature-development",{"tool":37,"command":38},"bunx","bunx skills add scrapbotengine\u002Fscrapbot --skill scrapbot-feature-development",{"tool":40,"command":41},"pnpm","pnpm dlx skills add scrapbotengine\u002Fscrapbot --skill scrapbot-feature-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-feature-development\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Fcheck_component_docs.mjs","SCRIPT","脚本",1751,"https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-feature-development\u002Fscripts\u002Fcheck_component_docs.mjs",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M780FHB90ZFW7PCDF4T2CZWJ","todo-list","Establish and maintain a lightweight project task list in docs\u002FTODO.md. Use when the user asks to track todos, maintain a TODO.md, preserve follow-up work while implementing features, or keep an agent-readable list of outstanding project tasks.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftodo-list\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M780FDCA3A3V1MFHC7WBBH1V","technical-writing","Invoke this skill whenever you need to create, update, review, restructure, or audit technical documentation such as README files, user manuals, API documentation, architecture notes, setup guides, troubleshooting guides, or developer docs. Use it to align docs with source code, existing project conventions, and the intended audience.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M780F8P241XCW3QBSTHGDMGT","scrapbot-ui-development","Use when adding, changing, debugging, reviewing, or documenting Scrapbot ECS UI components, layout, controls, interaction state, styling, reconciliation, project TOML UI, Luau UI APIs, native UI payloads, or editor UI composition. Enforces one reusable public UI contract across projects and the editor.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-ui-development\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M780F3BX29AFTG4HVCMYNNZH","scrapbot-testing","Use when testing or verifying Scrapbot changes, especially scene persistence and authoring savepoints, lifecycle integrity, CLI behavior, generated Luau types, example projects, ECS rendering, WGPU smoke tests, headless framegrabs, PNG artifacts, documentation builds, or before committing.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-testing\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M780ERXV207J7X3VD3RNJM7H","scrapbot-architecture-inventory","Maintain and audit Scrapbot's source-oriented architecture inventory in docs\u002Farchitecture. Use when adding, removing, renaming, or changing engine systems, component registrations, component ownership\u002Flifecycle, project resources, runtime registries, UUID\u002Fhandle\u002Fversion semantics, load\u002Fspawn\u002Fplayback\u002Fpersistence\u002Fhot-reload lifecycles, authoritative or derived state, dirty queues\u002Frevisions\u002Fcaches, frame\u002Frender\u002FUI data flows, package responsibilities, or architectural documentation; also use for architecture overviews and inventory drift audits.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fscrapbot-architecture-inventory\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M780EN88Y59XE1QNEN545ZEF","odin-language","Work effectively in Odin programming language codebases. Use when reading, writing, reviewing, testing, refactoring, or documenting `.odin` files; when choosing idiomatic Odin syntax, packages, allocators, error handling, foreign bindings, tests, build flags, or data-oriented designs; or when translating concepts from C, C++, Go, Lua, or scripting languages into Odin.","https:\u002F\u002Fgithub.com\u002Fscrapbotengine\u002Fscrapbot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fodin-language\u002FSKILL.md",[],[]]