[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPYJ4N976H8NJF4WQWP2YN":3,"skill-same:01M6HPYJ4N976H8NJF4WQWP2YN":77},{"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":27,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":76},"01M6HPYJ4N976H8NJF4WQWP2YN","map-systems",null,"Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fmap-systems\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"map systems","systems","map","design-system","concept","hand","true","name","dependencies","next","decompose","design","edit","write","read","grep","pick","system","game","prioritize","create","2026-11-10 10:12:30",false,"---\nname: map-systems\ndescription: \"Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.\"\nargument-hint: \"[optional: 'next' to pick highest-priority undesigned system, or a system name to hand off to \u002Fdesign-system]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, TodoWrite\n---\n\nWhen this skill is invoked:\n\n## 1. Parse Arguments\n\nTwo modes:\n\n- **No argument**: `\u002Fmap-systems` — Run the full decomposition workflow (Phases 1-5)\n  to create or update the systems index.\n- **`next`**: `\u002Fmap-systems next` — Pick the highest-priority undesigned system\n  from the index and hand off to `\u002Fdesign-system` (Phase 6).\n\n---\n\n## 2. Phase 1: Read Concept (Required Context)\n\nRead the game concept and any existing design work. This provides the raw material\nfor systems decomposition.\n\n**Required:**\n- Read `design\u002Fgdd\u002Fgame-concept.md` — **fail with a clear message if missing**:\n  > \"No game concept found at `design\u002Fgdd\u002Fgame-concept.md`. Run `\u002Fbrainstorm` first\n  > to create one, then come back to decompose it into systems.\"\n\n**Optional (read if they exist):**\n- Read `design\u002Fgdd\u002Fgame-pillars.md` — pillars constrain priority and scope\n- Read `design\u002Fgdd\u002Fsystems-index.md` — if exists, **resume** from where it left off\n  (update, don't recreate from scratch)\n- Glob `design\u002Fgdd\u002F*.md` — check which system GDDs already exist\n\n**If the systems index already exists:**\n- Read it and present current status to the user\n- Use `AskUserQuestion` to ask:\n  \"The systems index already exists with [N] systems ([M] designed, [K] not started).\n  What would you like to do?\"\n  - Options: \"Update the index with new systems\", \"Design the next undesigned system\",\n    \"Review and revise priorities\"\n\n---\n\n## 3. Phase 2: Systems Enumeration (Collaborative)\n\nExtract and identify all systems the game needs. This is the creative core of the\nskill — it requires human judgment because concept docs rarely enumerate every\nsystem explicitly.\n\n### Step 2a: Extract Explicit Systems\n\nScan the game concept for directly mentioned systems and mechanics:\n- Core Mechanics section (most explicit)\n- Core Loop section (implies what systems drive each loop tier)\n- Technical Considerations section (networking, procedural generation, etc.)\n- MVP Definition section (required features = required systems)\n\n### Step 2b: Identify Implicit Systems\n\nFor each explicit system, identify the **hidden systems** it implies. Games always\nneed more systems than the concept doc mentions. Use this inference pattern:\n\n- \"Inventory\" implies: item database, equipment slots, weight\u002Fcapacity rules,\n  inventory UI, item serialization for save\u002Fload\n- \"Combat\" implies: damage calculation, health system, hit detection, status effects,\n  enemy AI, combat UI (health bars, damage numbers), death\u002Frespawn\n- \"Open world\" implies: streaming\u002Fchunking, LOD system, fast travel, map\u002Fminimap,\n  point of interest tracking, world state persistence\n- \"Multiplayer\" implies: networking layer, lobby\u002Fmatchmaking, state synchronization,\n  anti-cheat, network UI (ping, player list)\n- \"Crafting\" implies: recipe database, ingredient gathering, crafting UI,\n  success\u002Ffailure mechanics, recipe discovery\u002Flearning\n- \"Dialogue\" implies: dialogue tree system, dialogue UI, choice tracking, NPC\n  state management, localization hooks\n- \"Progression\" implies: XP system, level-up mechanics, skill tree, unlock\n  tracking, progression UI, progression save data\n\nExplain in conversation text why each implicit system is needed (with examples).\n\n### Step 2c: User Review\n\nPresent the enumeration organized by category. For each system, show:\n- Name\n- Category\n- Brief description (1 sentence)\n- Whether it was explicit (from concept) or implicit (inferred)\n\nThen use `AskUserQuestion` to capture feedback:\n- \"Are there systems missing from this list?\"\n- \"Should any of these be combined or split?\"\n- \"Are there systems listed that this game does NOT need?\"\n\nIterate until the user approves the enumeration.\n\n---\n\n## 4. Phase 3: Dependency Mapping (Collaborative)\n\nFor each system, determine what it depends on. A system \"depends on\" another if\nit cannot function without that other system existing first.\n\n### Step 3a: Map Dependencies\n\nFor each system, list its dependencies. Use these dependency heuristics:\n- **Input\u002Foutput dependencies**: System A produces data System B needs\n- **Structural dependencies**: System A provides the framework System B plugs into\n- **UI dependencies**: Every gameplay system has a corresponding UI system that\n  depends on it (but UI is designed after the gameplay system)\n\n### Step 3b: Sort by Dependency Order\n\nArrange systems into layers:\n1. **Foundation**: Systems with zero dependencies (designed and built first)\n2. **Core**: Systems depending only on Foundation systems\n3. **Feature**: Systems depending on Core systems\n4. **Presentation**: UI and feedback systems that wrap gameplay systems\n5. **Polish**: Meta-systems, tutorials, analytics, accessibility\n\n### Step 3c: Detect Circular Dependencies\n\nCheck for cycles in the dependency graph. If found:\n- Highlight them to the user\n- Propose resolutions (interface abstraction, simultaneous design, breaking the\n  cycle by defining a contract between the two systems)\n\n### Step 3d: Present to User\n\nShow the dependency map as a layered list. Highlight:\n- Any circular dependencies\n- Any \"bottleneck\" systems (many others depend on them — these are high-risk)\n- Any systems with no dependents (leaf nodes — lower risk, can be designed late)\n\nUse `AskUserQuestion` to ask: \"Does this dependency ordering look right? Any\ndependencies I'm missing or that should be removed?\"\n\n---\n\n## 5. Phase 4: Priority Assignment (Collaborative)\n\nAssign each system to a priority tier based on what milestone it's needed for.\n\n### Step 4a: Auto-Assign Based on Concept\n\nUse these heuristics for initial assignment:\n- **MVP**: Systems mentioned in the concept's \"Required for MVP\" section, plus their\n  Foundation-layer dependencies\n- **Vertical Slice**: Systems needed for a complete experience in one area\n- **Alpha**: All remaining gameplay systems\n- **Full Vision**: Polish, meta, and nice-to-have systems\n\n### Step 4b: User Review\n\nPresent the priority assignments in a table. For each tier, explain why systems\nwere placed there.\n\nUse `AskUserQuestion` to ask: \"Do these priority assignments match your vision?\nWhich systems should be higher or lower priority?\"\n\nExplain reasoning in conversation: \"I placed [system] in MVP because the core loop\nrequires it — without [system], the 30-second loop can't function.\"\n\n### Step 4c: Determine Design Order\n\nCombine dependency sort + priority tier to produce the final design order:\n1. MVP Foundation systems first\n2. MVP Core systems second\n3. MVP Feature systems third\n4. Vertical Slice Foundation\u002FCore systems\n5. ...and so on\n\nThis is the order the team should write GDDs in.\n\n---\n\n## 6. Phase 5: Create Systems Index (Write)\n\n### Step 5a: Draft the Document\n\nUsing the template at `.claude\u002Fdocs\u002Ftemplates\u002Fsystems-index.md`, populate the\nsystems index with all data from Phases 2-4:\n- Fill the enumeration table\n- Fill the dependency map\n- Fill the recommended design order\n- Fill the high-risk systems\n- Fill progress tracker (all systems \"Not Started\" initially, unless GDDs already exist)\n\n### Step 5b: Approval\n\nPresent a summary of the document:\n- Total systems count by category\n- MVP system count\n- First 3 systems in the design order\n- Any high-risk items\n\nAsk: \"May I write the systems index to `design\u002Fgdd\u002Fsystems-index.md`?\"\n\nWait for approval. Write the file only after \"yes.\"\n\n### Step 5c: Update Session State\n\nAfter writing, update `production\u002Fsession-state\u002Factive.md` with:\n- Task: Systems decomposition\n- Status: Systems index created\n- File: design\u002Fgdd\u002Fsystems-index.md\n- Next: Design individual system GDDs\n\n---\n\n## 7. Phase 6: Design Individual Systems (Handoff to \u002Fdesign-system)\n\nThis phase is entered when:\n- The user says \"yes\" to designing systems after creating the index\n- The user invokes `\u002Fmap-systems [system-name]`\n- The user invokes `\u002Fmap-systems next`\n\n### Step 6a: Select the System\n\n- If a system name was provided, find it in the systems index\n- If `next` was used, pick the highest-priority undesigned system (by design order)\n- If the user just finished the index, ask:\n  \"Would you like to start designing individual systems now? The first system in\n  the design order is [name]. Or would you prefer to stop here and come back later?\"\n\nUse `AskUserQuestion` for: \"Start designing [system-name] now, pick a different\nsystem, or stop here?\"\n\n### Step 6b: Hand Off to \u002Fdesign-system\n\nOnce a system is selected, invoke the `\u002Fdesign-system [system-name]` skill.\n\nThe `\u002Fdesign-system` skill handles the full GDD authoring process:\n- Gathers context from game concept, systems index, and dependency GDDs\n- Creates a file skeleton immediately\n- Walks through all 8 required sections one at a time (collaborative, incremental)\n- Cross-references existing docs to prevent contradictions\n- Routes to specialist agents for domain expertise\n- Writes each section to file as soon as it's approved\n- Runs `\u002Fdesign-review` when complete\n- Updates the systems index\n\n**Do not duplicate the \u002Fdesign-system workflow here.** This skill owns the systems\n*index*; `\u002Fdesign-system` owns individual system *GDDs*.\n\n### Step 6c: Loop or Stop\n\nAfter `\u002Fdesign-system` completes, use `AskUserQuestion`:\n- \"Continue to the next system ([next system name])?\"\n- \"Pick a different system?\"\n- \"Stop here for this session?\"\n\nIf continuing, return to Step 6a.\n\n---\n\n## 8. Phase 7: Suggest Next Steps\n\nAfter the systems index is created (or after designing some systems), suggest\nthe appropriate next actions:\n\n- \"Run `\u002Fdesign-system [system-name]` to write the next system's GDD\"\n- \"Run `\u002Fdesign-review [path]` on each completed GDD to validate quality\"\n- \"Run `\u002Fgate-check pre-production` to check if you're ready to start building\"\n- \"Prototype the highest-risk system with `\u002Fprototype [system]`\"\n- \"Plan the first implementation sprint with `\u002Fsprint-plan new`\"\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle at every phase:\n\n1. **Question -> Options -> Decision -> Draft -> Approval** at every step\n2. **AskUserQuestion** at every decision point (Explain -> Capture pattern):\n   - Phase 2: \"Missing systems? Combine or split?\"\n   - Phase 3: \"Dependency ordering correct?\"\n   - Phase 4: \"Priority assignments match your vision?\"\n   - Phase 5: \"May I write the systems index?\"\n   - Phase 6: \"Start designing, pick different, or stop?\" then hand off to `\u002Fdesign-system`\n3. **\"May I write to [filepath]?\"** before every file write\n4. **Incremental writing**: Update the systems index after each system is designed\n5. **Handoff**: Individual GDD authoring is owned by `\u002Fdesign-system`, which handles\n   incremental section writing, cross-referencing, design review, and index updates\n6. **Session state updates**: Write to `production\u002Fsession-state\u002Factive.md` after\n   each milestone (index created, system designed, priorities changed)\n\n**Never** auto-generate the full systems list and write it without review.\n**Never** start designing a system without user confirmation.\n**Always** show the enumeration, dependencies, and priorities for user validation.\n","When this skill is invoked:\n\n## 1. Parse Arguments\n\nTwo modes:\n\n- **No argument**: `\u002Fmap-systems` — Run the full decomposition workflow (Phases 1-5)\n  to create or update the systems index.\n- **`next`**: `\u002Fmap-systems next` — Pick the highest-priority undesigned system\n  from the index and hand off to `\u002Fdesign-system` (Phase 6).\n\n---\n\n## 2. Phase 1: Read Concept (Required Context)\n\nRead the game concept and any existing design work. This provides the raw material\nfor systems decomposition.\n\n**Required:**\n- Read `design\u002Fgdd\u002Fgame-concept.md` — **fail with a clear message if missing**:\n  > \"No game concept found at `design\u002Fgdd\u002Fgame-concept.md`. Run `\u002Fbrainstorm` first\n  > to create one, then come back to decompose it into systems.\"\n\n**Optional (read if they exist):**\n- Read `design\u002Fgdd\u002Fgame-pillars.md` — pillars constrain priority and scope\n- Read `design\u002Fgdd\u002Fsystems-index.md` — if exists, **resume** from where it left off\n  (update, don't recreate from scratch)\n- Glob `design\u002Fgdd\u002F*.md` — check which system GDDs already exist\n\n**If the systems index already exists:**\n- Read it and present current status to the user\n- Use `AskUserQuestion` to ask:\n  \"The systems index already exists with [N] systems ([M] designed, [K] not started).\n  What would you like to do?\"\n  - Options: \"Update the index with new systems\", \"Design the next undesigned system\",\n    \"Review and revise priorities\"\n\n---\n\n## 3. Phase 2: Systems Enumeration (Collaborative)\n\nExtract and identify all systems the game needs. This is the creative core of the\nskill — it requires human judgment because concept docs rarely enumerate every\nsystem explicitly.\n\n### Step 2a: Extract Explicit Systems\n\nScan the game concept for directly mentioned systems and mechanics:\n- Core Mechanics section (most explicit)\n- Core Loop section (implies what systems drive each loop tier)\n- Technical Considerations section (networking, procedural generation, etc.)\n- MVP Definition section (required features = required systems)\n\n### Step 2b: Identify Implicit Systems\n\nFor each explicit system, identify the **hidden systems** it implies. Games always\nneed more systems than the concept doc mentions. Use this inference pattern:\n\n- \"Inventory\" implies: item database, equipment slots, weight\u002Fcapacity rules,\n  inventory UI, item serialization for save\u002Fload\n- \"Combat\" implies: damage calculation, health system, hit detection, status effects,\n  enemy AI, combat UI (health bars, damage numbers), death\u002Frespawn\n- \"Open world\" implies: streaming\u002Fchunking, LOD system, fast travel, map\u002Fminimap,\n  point of interest tracking, world state persistence\n- \"Multiplayer\" implies: networking layer, lobby\u002Fmatchmaking, state synchronization,\n  anti-cheat, network UI (ping, player list)\n- \"Crafting\" implies: recipe database, ingredient gathering, crafting UI,\n  success\u002Ffailure mechanics, recipe discovery\u002Flearning\n- \"Dialogue\" implies: dialogue tree system, dialogue UI, choice tracking, NPC\n  state management, localization hooks\n- \"Progression\" implies: XP system, level-up mechanics, skill tree, unlock\n  tracking, progression UI, progression save data\n\nExplain in conversation text why each implicit system is needed (with examples).\n\n### Step 2c: User Review\n\nPresent the enumeration organized by category. For each system, show:\n- Name\n- Category\n- Brief description (1 sentence)\n- Whether it was explicit (from concept) or implicit (inferred)\n\nThen use `AskUserQuestion` to capture feedback:\n- \"Are there systems missing from this list?\"\n- \"Should any of these be combined or split?\"\n- \"Are there systems listed that this game does NOT need?\"\n\nIterate until the user approves the enumeration.\n\n---\n\n## 4. Phase 3: Dependency Mapping (Collaborative)\n\nFor each system, determine what it depends on. A system \"depends on\" another if\nit cannot function without that other system existing first.\n\n### Step 3a: Map Dependencies\n\nFor each system, list its dependencies. Use these dependency heuristics:\n- **Input\u002Foutput dependencies**: System A produces data System B needs\n- **Structural dependencies**: System A provides the framework System B plugs into\n- **UI dependencies**: Every gameplay system has a corresponding UI system that\n  depends on it (but UI is designed after the gameplay system)\n\n### Step 3b: Sort by Dependency Order\n\nArrange systems into layers:\n1. **Foundation**: Systems with zero dependencies (designed and built first)\n2. **Core**: Systems depending only on Foundation systems\n3. **Feature**: Systems depending on Core systems\n4. **Presentation**: UI and feedback systems that wrap gameplay systems\n5. **Polish**: Meta-systems, tutorials, analytics, accessibility\n\n### Step 3c: Detect Circular Dependencies\n\nCheck for cycles in the dependency graph. If found:\n- Highlight them to the user\n- Propose resolutions (interface abstraction, simultaneous design, breaking the\n  cycle by defining a contract between the two systems)\n\n### Step 3d: Present to User\n\nShow the dependency map as a layered list. Highlight:\n- Any circular dependencies\n- Any \"bottleneck\" systems (many others depend on them — these are high-risk)\n- Any systems with no dependents (leaf nodes — lower risk, can be designed late)\n\nUse `AskUserQuestion` to ask: \"Does this dependency ordering look right? Any\ndependencies I'm missing or that should be removed?\"\n\n---\n\n## 5. Phase 4: Priority Assignment (Collaborative)\n\nAssign each system to a priority tier based on what milestone it's needed for.\n\n### Step 4a: Auto-Assign Based on Concept\n\nUse these heuristics for initial assignment:\n- **MVP**: Systems mentioned in the concept's \"Required for MVP\" section, plus their\n  Foundation-layer dependencies\n- **Vertical Slice**: Systems needed for a complete experience in one area\n- **Alpha**: All remaining gameplay systems\n- **Full Vision**: Polish, meta, and nice-to-have systems\n\n### Step 4b: User Review\n\nPresent the priority assignments in a table. For each tier, explain why systems\nwere placed there.\n\nUse `AskUserQuestion` to ask: \"Do these priority assignments match your vision?\nWhich systems should be higher or lower priority?\"\n\nExplain reasoning in conversation: \"I placed [system] in MVP because the core loop\nrequires it — without [system], the 30-second loop can't function.\"\n\n### Step 4c: Determine Design Order\n\nCombine dependency sort + priority tier to produce the final design order:\n1. MVP Foundation systems first\n2. MVP Core systems second\n3. MVP Feature systems third\n4. Vertical Slice Foundation\u002FCore systems\n5. ...and so on\n\nThis is the order the team should write GDDs in.\n\n---\n\n## 6. Phase 5: Create Systems Index (Write)\n\n### Step 5a: Draft the Document\n\nUsing the template at `.claude\u002Fdocs\u002Ftemplates\u002Fsystems-index.md`, populate the\nsystems index with all data from Phases 2-4:\n- Fill the enumeration table\n- Fill the dependency map\n- Fill the recommended design order\n- Fill the high-risk systems\n- Fill progress tracker (all systems \"Not Started\" initially, unless GDDs already exist)\n\n### Step 5b: Approval\n\nPresent a summary of the document:\n- Total systems count by category\n- MVP system count\n- First 3 systems in the design order\n- Any high-risk items\n\nAsk: \"May I write the systems index to `design\u002Fgdd\u002Fsystems-index.md`?\"\n\nWait for approval. Write the file only after \"yes.\"\n\n### Step 5c: Update Session State\n\nAfter writing, update `production\u002Fsession-state\u002Factive.md` with:\n- Task: Systems decomposition\n- Status: Systems index created\n- File: design\u002Fgdd\u002Fsystems-index.md\n- Next: Design individual system GDDs\n\n---\n\n## 7. Phase 6: Design Individual Systems (Handoff to \u002Fdesign-system)\n\nThis phase is entered when:\n- The user says \"yes\" to designing systems after creating the index\n- The user invokes `\u002Fmap-systems [system-name]`\n- The user invokes `\u002Fmap-systems next`\n\n### Step 6a: Select the System\n\n- If a system name was provided, find it in the systems index\n- If `next` was used, pick the highest-priority undesigned system (by design order)\n- If the user just finished the index, ask:\n  \"Would you like to start designing individual systems now? The first system in\n  the design order is [name]. Or would you prefer to stop here and come back later?\"\n\nUse `AskUserQuestion` for: \"Start designing [system-name] now, pick a different\nsystem, or stop here?\"\n\n### Step 6b: Hand Off to \u002Fdesign-system\n\nOnce a system is selected, invoke the `\u002Fdesign-system [system-name]` skill.\n\nThe `\u002Fdesign-system` skill handles the full GDD authoring process:\n- Gathers context from game concept, systems index, and dependency GDDs\n- Creates a file skeleton immediately\n- Walks through all 8 required sections one at a time (collaborative, incremental)\n- Cross-references existing docs to prevent contradictions\n- Routes to specialist agents for domain expertise\n- Writes each section to file as soon as it's approved\n- Runs `\u002Fdesign-review` when complete\n- Updates the systems index\n\n**Do not duplicate the \u002Fdesign-system workflow here.** This skill owns the systems\n*index*; `\u002Fdesign-system` owns individual system *GDDs*.\n\n### Step 6c: Loop or Stop\n\nAfter `\u002Fdesign-system` completes, use `AskUserQuestion`:\n- \"Continue to the next system ([next system name])?\"\n- \"Pick a different system?\"\n- \"Stop here for this session?\"\n\nIf continuing, return to Step 6a.\n\n---\n\n## 8. Phase 7: Suggest Next Steps\n\nAfter the systems index is created (or after designing some systems), suggest\nthe appropriate next actions:\n\n- \"Run `\u002Fdesign-system [system-name]` to write the next system's GDD\"\n- \"Run `\u002Fdesign-review [path]` on each completed GDD to validate quality\"\n- \"Run `\u002Fgate-check pre-production` to check if you're ready to start building\"\n- \"Prototype the highest-risk system with `\u002Fprototype [system]`\"\n- \"Plan the first implementation sprint with `\u002Fsprint-plan new`\"\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle at every phase:\n\n1. **Question -> Options -> Decision -> Draft -> Approval** at every step\n2. **AskUserQuestion** at every decision point (Explain -> Capture pattern):\n   - Phase 2: \"Missing systems? Combine or split?\"\n   - Phase 3: \"Dependency ordering correct?\"\n   - Phase 4: \"Priority assignments match your vision?\"\n   - Phase 5: \"May I write the systems index?\"\n   - Phase 6: \"Start designing, pick different, or stop?\" then hand off to `\u002Fdesign-system`\n3. **\"May I write to [filepath]?\"** before every file write\n4. **Incremental writing**: Update the systems index after each system is designed\n5. **Handoff**: Individual GDD authoring is owned by `\u002Fdesign-system`, which handles\n   incremental section writing, cross-referencing, design review, and index updates\n6. **Session state updates**: Write to `production\u002Fsession-state\u002Factive.md` after\n   each milestone (index created, system designed, priorities changed)\n\n**Never** auto-generate the full systems list and write it without review.\n**Never** start designing a system without user confirmation.\n**Always** show the enumeration, dependencies, and priorities for user validation.\n",{"name":5,"description":7,"allowed-tools":54,"argument-hint":55,"user-invocable":56},"Read, Glob, Grep, Write, Edit, AskUserQuestion, TodoWrite","[optional: 'next' to pick highest-priority undesigned system, or a system name to hand off to \u002Fdesign-system]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fmap-systems",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-12 14:55:20",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":56},[66,69,72],{"tool":67,"command":68},"npx","npx skills add welflau\u002Fai-dev-system --skill map-systems",{"tool":70,"command":71},"bunx","bunx skills add welflau\u002Fai-dev-system --skill map-systems",{"tool":73,"command":74},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill map-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fmap-systems\u002FSKILL.md",[],[78,111,140,166,188,212],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":92,"publishedAt":110},"01M6HS9Z4B0YA8CJCS2Y2F04Y3","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fwebapp-testing\u002FSKILL.md",[86,89],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","with","for","2026-11-11 15:11:14",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":110},"01M6HRAGMG7JF0HXYHMA5QHS8A","internal-comms","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Finternal-comms\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[122,123,124,125,126,41,127,128,129,130,131,132,133,134,135,136,137,138,139],"internal comms","comms","status","help","SET","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":49},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[147],{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},[149,99,150,151,152,96,153,154,155,156,157,158,159,160,127,161,162,163,164,109,165],"web artifacts builder","artifacts","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":49},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[173,174,175],{"categoryNo":90,"categoryName":91,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},[96,39,177,153,99,154,155,178,48,179,150,180,105,181,127,182,183,184,185,108,186,187],"frontend design","react components","code","examples","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":49},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[195],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[197,198,199,48,179,200,201,202,203,127,204,205,29,206,108,207,208,209,210,211,187],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","users","Existing","request","generative","copyright","fields",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":216,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":49},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[219],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[221,222,223,224,101,225,150,126,226,227,181,228,229,183,230,108,231,232,233,109,234,235],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]