[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPZPNFB0J1FHT7BJTK3BN5":3,"skill-same:01M6HPZPNFB0J1FHT7BJTK3BN5":83},{"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":30,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":69,"install":70,"resources":82},"01M6HPZPNFB0J1FHT7BJTK3BN5","reverse-document",null,"Generate design or architecture documents from existing implementation. Works backwards from code\u002Fprototypes to create missing planning docs.","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\u002Freverse-document\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"reverse document","reverse","document","edit","Existing","path","true","ComBat","missing","type","gameplay","generate design","design","write","read","src","Bash","planning","code","generate","create","core","documents","architecture","2026-11-10 10:12:30",false,"---\nname: reverse-document\ndescription: \"Generate design or architecture documents from existing implementation. Works backwards from code\u002Fprototypes to create missing planning docs.\"\nargument-hint: \"\u003Ctype> \u003Cpath> (e.g., 'design src\u002Fgameplay\u002Fcombat' or 'architecture src\u002Fcore')\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write, Edit, Bash\n---\n\n# Reverse Documentation\n\nThis skill analyzes existing implementation (code, prototypes, systems) and generates\nappropriate design or architecture documentation. Use this when:\n- You built a feature without writing a design doc first\n- You inherited a codebase without documentation\n- You prototyped a mechanic and need to formalize it\n- You need to document \"why\" behind existing code\n\n---\n\n## Workflow\n\n### 1. Parse Arguments\n\n**Format**: `\u002Freverse-document \u003Ctype> \u003Cpath>`\n\n**Type options**:\n- `design` → Generate a game design document (GDD section)\n- `architecture` → Generate an Architecture Decision Record (ADR)\n- `concept` → Generate a concept document from prototype\n\n**Path**: Directory or file to analyze\n- `src\u002Fgameplay\u002Fcombat\u002F` → All combat-related code\n- `src\u002Fcore\u002Fevent-system.cpp` → Specific file\n- `prototypes\u002Fstealth-mech\u002F` → Prototype directory\n\n**Examples**:\n```bash\n\u002Freverse-document design src\u002Fgameplay\u002Fmagic-system\n\u002Freverse-document architecture src\u002Fcore\u002Fentity-component\n\u002Freverse-document concept prototypes\u002Fvehicle-combat\n```\n\n### 2. Analyze Implementation\n\n**Read and understand the code\u002Fprototype**:\n\n**For design docs (GDD):**\n- Identify mechanics, rules, formulas\n- Extract gameplay values (damage, cooldowns, ranges)\n- Find state machines, ability systems, progression\n- Detect edge cases handled in code\n- Map dependencies (what systems interact?)\n\n**For architecture docs (ADR):**\n- Identify patterns (ECS, singleton, observer, etc.)\n- Understand technical decisions (threading, serialization, etc.)\n- Map dependencies and coupling\n- Assess performance characteristics\n- Find constraints and trade-offs\n\n**For concept docs (prototype analysis):**\n- Identify core mechanic\n- Extract emergent gameplay patterns\n- Note what worked vs what didn't\n- Find technical feasibility insights\n- Document player fantasy \u002F feel\n\n### 3. Ask Clarifying Questions (Collaborative Protocol)\n\n**DO NOT** just describe the code. **ASK** about intent:\n\n**Design questions**:\n- \"I see a stamina system that depletes during combat. Was this for:\n  - Pacing (prevent spam)?\n  - Resource management (strategic depth)?\n  - Or something else?\"\n- \"The stagger mechanic seems central. Is this a core pillar, or supporting feature?\"\n- \"Damage scales exponentially with level. Intentional power fantasy, or needs rebalancing?\"\n\n**Architecture questions**:\n- \"You're using a service locator pattern. Was this chosen for:\n  - Testability (mock dependencies)?\n  - Decoupling (reduce hard references)?\n  - Or inherited from existing code?\"\n- \"I see manual memory management instead of smart pointers. Performance requirement, or legacy?\"\n\n**Concept questions**:\n- \"The prototype emphasizes stealth over combat. Is that the intended pillar?\"\n- \"Players seem to exploit the grappling hook for speed. Feature or bug?\"\n\n### 4. Present Findings\n\nBefore drafting, show what you discovered:\n\n```\nI've analyzed src\u002Fgameplay\u002Fcombat\u002F. Here's what I found:\n\nMECHANICS IMPLEMENTED:\n- 3-hit combo system with timing windows\n- Guard-break mechanic (heavy attack vs blocking enemy)\n- Stamina system (depletes on attack\u002Fdodge, regens when idle)\n- Stagger system (builds up, triggers vulnerable state)\n\nFORMULAS DISCOVERED:\n- Damage = Base * (1 + StrengthScaling * Level)\n- Stagger buildup = AttackStaggerValue \u002F (Enemy.Poise * 0.5)\n- Stamina cost = BaseStaminaCost * (1 - EfficiencyBonus)\n\nUNCLEAR INTENT AREAS:\n1. Stamina system — pacing or resource management?\n2. Stagger — core pillar or supporting feature?\n3. Damage scaling — power fantasy or needs tuning?\n\nBefore I draft the design doc, could you clarify these points?\n```\n\nWait for user to clarify intent before drafting.\n\n### 5. Draft Document Using Template\n\nBased on type, use appropriate template:\n\n| Type | Template | Output Path |\n|------|----------|-------------|\n| `design` | `templates\u002Fdesign-doc-from-implementation.md` | `design\u002Fgdd\u002F[system-name].md` |\n| `architecture` | `templates\u002Farchitecture-doc-from-code.md` | `docs\u002Farchitecture\u002F[decision-name].md` |\n| `concept` | `templates\u002Fconcept-doc-from-prototype.md` | `prototypes\u002F[name]\u002FCONCEPT.md` or `design\u002Fconcepts\u002F[name].md` |\n\n**Draft structure**:\n- Capture **what exists** (mechanics, patterns, implementation)\n- Document **why it exists** (intent clarified with user)\n- Identify **what's missing** (edge cases not handled, gaps in design)\n- Flag **follow-up work** (balance tuning, missing features)\n\n### 6. Show Draft and Request Approval\n\n**Collaborative protocol**:\n```\nI've drafted the combat system design doc based on your code and clarifications.\n\n[Show key sections: Overview, Mechanics, Formulas, Design Intent]\n\nADDITIONS I MADE:\n- Documented stamina as \"pacing mechanic\" per your clarification\n- Added edge cases not in code (what if stamina hits 0 mid-combo?)\n- Flagged balance concern: exponential damage scaling at high levels\n\nSECTIONS MARKED AS INCOMPLETE:\n- \"Enemy AI interaction with stagger\" (not fully implemented yet)\n- \"Weapon variety and scaling\" (only sword implemented so far)\n\nMay I write this to design\u002Fgdd\u002Fcombat-system.md?\n```\n\nWait for approval. User may request changes before writing.\n\n### 7. Write Document with Metadata\n\nWhen approved, write the file with special markers:\n\n```markdown\n---\nstatus: reverse-documented\nsource: src\u002Fgameplay\u002Fcombat\u002F\ndate: 2026-02-13\nverified-by: [User name]\n---\n\n# Combat System Design\n\n> **Note**: This document was reverse-engineered from the existing implementation.\n> It captures current behavior and clarified design intent. Some sections may be\n> incomplete where implementation is partial or intent was unclear.\n\n[Rest of document...]\n```\n\n### 8. Flag Follow-Up Work\n\nAfter writing, suggest next steps:\n\n```\n✅ Written to design\u002Fgdd\u002Fcombat-system.md\n\nFOLLOW-UP RECOMMENDED:\n1. Run \u002Fbalance-check on combat formulas (exponential scaling concern)\n2. Create ADR for stamina system architecture decision\n3. Implement missing edge cases:\n   - Stamina depletion mid-combo behavior\n   - Stagger state during dodge\n4. Extend design doc when weapon variety is implemented\n\nWould you like me to tackle any of these now?\n```\n\n---\n\n## Template Selection Logic\n\n| If analyzing... | Use template... | Because... |\n|----------------|-----------------|------------|\n| `src\u002Fgameplay\u002F*` | design-doc-from-implementation.md | Gameplay mechanics → GDD |\n| `src\u002Fcore\u002F*`, `src\u002Fai\u002F*` | architecture-doc-from-code.md | Core systems → ADR |\n| `prototypes\u002F*` | concept-doc-from-prototype.md | Experiments → concept doc |\n| `src\u002Fnetworking\u002F*` | architecture-doc-from-code.md | Technical systems → ADR |\n| `src\u002Fui\u002F*` | design-doc-from-implementation.md | UI\u002FUX → design spec |\n\n---\n\n## Example Session: Reverse-Document Combat Code\n\n```\nUser: \u002Freverse-document design src\u002Fgameplay\u002Fcombat\n\nAgent: I'll analyze your combat implementation to create a design doc.\n       [Reads code, discovers mechanics, formulas]\n\nAgent: I've analyzed src\u002Fgameplay\u002Fcombat\u002F. Here's what I found:\n       [Shows mechanics, formulas, unclear areas]\n\n       Before drafting, could you clarify:\n       1. Stamina system intent?\n       2. Is stagger a core pillar?\n       3. Damage scaling — intentional or needs tuning?\n\nUser: 1. Stamina is for pacing, prevent button mashing\n      2. Stagger is core — I want deliberate combat\n      3. Yeah, exponential is too much, should be linear\n\nAgent: Perfect, that clarifies the vision. Let me draft the design doc.\n       [Shows draft with clarified intent]\n\n       May I write this to design\u002Fgdd\u002Fcombat-system.md?\n\nUser: Yes, write it.\n\nAgent: ✅ Written to design\u002Fgdd\u002Fcombat-system.md\n       ✅ Marked as [REVERSE-DOCUMENTED]\n       ✅ Flagged damage scaling for rebalancing\n\n       Next steps:\n       - Update damage formula to linear scaling\n       - Run \u002Fbalance-check to validate progression curve\n       - Document stagger as core pillar in game-pillars.md\n```\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Analyze First**: Read code, understand implementation\n2. **Question Intent**: Ask about \"why\", not just \"what\"\n3. **Present Findings**: Show discoveries, highlight unclear areas\n4. **User Clarifies**: Separate intent from accidents\n5. **Draft Document**: Create doc based on reality + intent\n6. **Show Draft**: Display key sections, explain additions\n7. **Get Approval**: \"May I write to [filepath]?\"\n8. **Flag Follow-Up**: Suggest related work, don't auto-execute\n\n**Never assume intent. Always ask before documenting \"why\".**\n","# Reverse Documentation\n\nThis skill analyzes existing implementation (code, prototypes, systems) and generates\nappropriate design or architecture documentation. Use this when:\n- You built a feature without writing a design doc first\n- You inherited a codebase without documentation\n- You prototyped a mechanic and need to formalize it\n- You need to document \"why\" behind existing code\n\n---\n\n## Workflow\n\n### 1. Parse Arguments\n\n**Format**: `\u002Freverse-document \u003Ctype> \u003Cpath>`\n\n**Type options**:\n- `design` → Generate a game design document (GDD section)\n- `architecture` → Generate an Architecture Decision Record (ADR)\n- `concept` → Generate a concept document from prototype\n\n**Path**: Directory or file to analyze\n- `src\u002Fgameplay\u002Fcombat\u002F` → All combat-related code\n- `src\u002Fcore\u002Fevent-system.cpp` → Specific file\n- `prototypes\u002Fstealth-mech\u002F` → Prototype directory\n\n**Examples**:\n```bash\n\u002Freverse-document design src\u002Fgameplay\u002Fmagic-system\n\u002Freverse-document architecture src\u002Fcore\u002Fentity-component\n\u002Freverse-document concept prototypes\u002Fvehicle-combat\n```\n\n### 2. Analyze Implementation\n\n**Read and understand the code\u002Fprototype**:\n\n**For design docs (GDD):**\n- Identify mechanics, rules, formulas\n- Extract gameplay values (damage, cooldowns, ranges)\n- Find state machines, ability systems, progression\n- Detect edge cases handled in code\n- Map dependencies (what systems interact?)\n\n**For architecture docs (ADR):**\n- Identify patterns (ECS, singleton, observer, etc.)\n- Understand technical decisions (threading, serialization, etc.)\n- Map dependencies and coupling\n- Assess performance characteristics\n- Find constraints and trade-offs\n\n**For concept docs (prototype analysis):**\n- Identify core mechanic\n- Extract emergent gameplay patterns\n- Note what worked vs what didn't\n- Find technical feasibility insights\n- Document player fantasy \u002F feel\n\n### 3. Ask Clarifying Questions (Collaborative Protocol)\n\n**DO NOT** just describe the code. **ASK** about intent:\n\n**Design questions**:\n- \"I see a stamina system that depletes during combat. Was this for:\n  - Pacing (prevent spam)?\n  - Resource management (strategic depth)?\n  - Or something else?\"\n- \"The stagger mechanic seems central. Is this a core pillar, or supporting feature?\"\n- \"Damage scales exponentially with level. Intentional power fantasy, or needs rebalancing?\"\n\n**Architecture questions**:\n- \"You're using a service locator pattern. Was this chosen for:\n  - Testability (mock dependencies)?\n  - Decoupling (reduce hard references)?\n  - Or inherited from existing code?\"\n- \"I see manual memory management instead of smart pointers. Performance requirement, or legacy?\"\n\n**Concept questions**:\n- \"The prototype emphasizes stealth over combat. Is that the intended pillar?\"\n- \"Players seem to exploit the grappling hook for speed. Feature or bug?\"\n\n### 4. Present Findings\n\nBefore drafting, show what you discovered:\n\n```\nI've analyzed src\u002Fgameplay\u002Fcombat\u002F. Here's what I found:\n\nMECHANICS IMPLEMENTED:\n- 3-hit combo system with timing windows\n- Guard-break mechanic (heavy attack vs blocking enemy)\n- Stamina system (depletes on attack\u002Fdodge, regens when idle)\n- Stagger system (builds up, triggers vulnerable state)\n\nFORMULAS DISCOVERED:\n- Damage = Base * (1 + StrengthScaling * Level)\n- Stagger buildup = AttackStaggerValue \u002F (Enemy.Poise * 0.5)\n- Stamina cost = BaseStaminaCost * (1 - EfficiencyBonus)\n\nUNCLEAR INTENT AREAS:\n1. Stamina system — pacing or resource management?\n2. Stagger — core pillar or supporting feature?\n3. Damage scaling — power fantasy or needs tuning?\n\nBefore I draft the design doc, could you clarify these points?\n```\n\nWait for user to clarify intent before drafting.\n\n### 5. Draft Document Using Template\n\nBased on type, use appropriate template:\n\n| Type | Template | Output Path |\n|------|----------|-------------|\n| `design` | `templates\u002Fdesign-doc-from-implementation.md` | `design\u002Fgdd\u002F[system-name].md` |\n| `architecture` | `templates\u002Farchitecture-doc-from-code.md` | `docs\u002Farchitecture\u002F[decision-name].md` |\n| `concept` | `templates\u002Fconcept-doc-from-prototype.md` | `prototypes\u002F[name]\u002FCONCEPT.md` or `design\u002Fconcepts\u002F[name].md` |\n\n**Draft structure**:\n- Capture **what exists** (mechanics, patterns, implementation)\n- Document **why it exists** (intent clarified with user)\n- Identify **what's missing** (edge cases not handled, gaps in design)\n- Flag **follow-up work** (balance tuning, missing features)\n\n### 6. Show Draft and Request Approval\n\n**Collaborative protocol**:\n```\nI've drafted the combat system design doc based on your code and clarifications.\n\n[Show key sections: Overview, Mechanics, Formulas, Design Intent]\n\nADDITIONS I MADE:\n- Documented stamina as \"pacing mechanic\" per your clarification\n- Added edge cases not in code (what if stamina hits 0 mid-combo?)\n- Flagged balance concern: exponential damage scaling at high levels\n\nSECTIONS MARKED AS INCOMPLETE:\n- \"Enemy AI interaction with stagger\" (not fully implemented yet)\n- \"Weapon variety and scaling\" (only sword implemented so far)\n\nMay I write this to design\u002Fgdd\u002Fcombat-system.md?\n```\n\nWait for approval. User may request changes before writing.\n\n### 7. Write Document with Metadata\n\nWhen approved, write the file with special markers:\n\n```markdown\n---\nstatus: reverse-documented\nsource: src\u002Fgameplay\u002Fcombat\u002F\ndate: 2026-02-13\nverified-by: [User name]\n---\n\n# Combat System Design\n\n> **Note**: This document was reverse-engineered from the existing implementation.\n> It captures current behavior and clarified design intent. Some sections may be\n> incomplete where implementation is partial or intent was unclear.\n\n[Rest of document...]\n```\n\n### 8. Flag Follow-Up Work\n\nAfter writing, suggest next steps:\n\n```\n✅ Written to design\u002Fgdd\u002Fcombat-system.md\n\nFOLLOW-UP RECOMMENDED:\n1. Run \u002Fbalance-check on combat formulas (exponential scaling concern)\n2. Create ADR for stamina system architecture decision\n3. Implement missing edge cases:\n   - Stamina depletion mid-combo behavior\n   - Stagger state during dodge\n4. Extend design doc when weapon variety is implemented\n\nWould you like me to tackle any of these now?\n```\n\n---\n\n## Template Selection Logic\n\n| If analyzing... | Use template... | Because... |\n|----------------|-----------------|------------|\n| `src\u002Fgameplay\u002F*` | design-doc-from-implementation.md | Gameplay mechanics → GDD |\n| `src\u002Fcore\u002F*`, `src\u002Fai\u002F*` | architecture-doc-from-code.md | Core systems → ADR |\n| `prototypes\u002F*` | concept-doc-from-prototype.md | Experiments → concept doc |\n| `src\u002Fnetworking\u002F*` | architecture-doc-from-code.md | Technical systems → ADR |\n| `src\u002Fui\u002F*` | design-doc-from-implementation.md | UI\u002FUX → design spec |\n\n---\n\n## Example Session: Reverse-Document Combat Code\n\n```\nUser: \u002Freverse-document design src\u002Fgameplay\u002Fcombat\n\nAgent: I'll analyze your combat implementation to create a design doc.\n       [Reads code, discovers mechanics, formulas]\n\nAgent: I've analyzed src\u002Fgameplay\u002Fcombat\u002F. Here's what I found:\n       [Shows mechanics, formulas, unclear areas]\n\n       Before drafting, could you clarify:\n       1. Stamina system intent?\n       2. Is stagger a core pillar?\n       3. Damage scaling — intentional or needs tuning?\n\nUser: 1. Stamina is for pacing, prevent button mashing\n      2. Stagger is core — I want deliberate combat\n      3. Yeah, exponential is too much, should be linear\n\nAgent: Perfect, that clarifies the vision. Let me draft the design doc.\n       [Shows draft with clarified intent]\n\n       May I write this to design\u002Fgdd\u002Fcombat-system.md?\n\nUser: Yes, write it.\n\nAgent: ✅ Written to design\u002Fgdd\u002Fcombat-system.md\n       ✅ Marked as [REVERSE-DOCUMENTED]\n       ✅ Flagged damage scaling for rebalancing\n\n       Next steps:\n       - Update damage formula to linear scaling\n       - Run \u002Fbalance-check to validate progression curve\n       - Document stagger as core pillar in game-pillars.md\n```\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Analyze First**: Read code, understand implementation\n2. **Question Intent**: Ask about \"why\", not just \"what\"\n3. **Present Findings**: Show discoveries, highlight unclear areas\n4. **User Clarifies**: Separate intent from accidents\n5. **Draft Document**: Create doc based on reality + intent\n6. **Show Draft**: Display key sections, explain additions\n7. **Get Approval**: \"May I write to [filepath]?\"\n8. **Flag Follow-Up**: Suggest related work, don't auto-execute\n\n**Never assume intent. Always ask before documenting \"why\".**\n",{"name":5,"description":7,"allowed-tools":60,"argument-hint":61,"user-invocable":62},"Read, Glob, Grep, Write, Edit, Bash","\u003Ctype> \u003Cpath> (e.g., 'design src\u002Fgameplay\u002Fcombat' or 'architecture src\u002Fcore')",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Freverse-document",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":71,"prompt":81,"zipAvailable":62},[72,75,78],{"tool":73,"command":74},"npx","npx skills add welflau\u002Fai-dev-system --skill reverse-document",{"tool":76,"command":77},"bunx","bunx skills add welflau\u002Fai-dev-system --skill reverse-document",{"tool":79,"command":80},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill reverse-document","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Freverse-document\u002FSKILL.md",[],[84,117,140,164,189,213],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":55},"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.","Apache-2.0","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",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","routing","state management","state","file","Tailwind","use","single-file","simple","ui components","multi","for","single",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":55},"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",[124,125,126],{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},[101,43,128,102,97,103,104,129,51,49,98,130,131,132,110,133,134,135,136,137,138,139],"frontend design","react components","examples","applications","landing","ui design","pages","aesthetics","web ui","with","generic","when",{"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":88,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":55},"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",[147],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[149,150,151,51,49,152,153,154,155,110,156,157,158,159,137,35,160,161,162,163,139],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","request","generative","copyright","fields",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":55},"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",[171],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[173,174,175,176,177,50,98,178,179,180,132,181,182,134,183,137,184,185,186,115,187,188],"theme factory","factory","theme","docs","toolkit","SET","fly","slides","styling","artifact","themes","you","fonts","can","apply","new",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":55},"01M6HS74GASM6FJ77F83EY679E","browsing","Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fsuperpowers-chrome\u002Fskills\u002Fbrowsing\u002FSKILL.md",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[191,199,200,201,202,203,204,205,206,207,208,110,209,210,211,212,114,184,115,35],"MCP","automation","chrome","sessions","protocol","browser","devtools","chrome devtools","tool","direct","browser control","control","via","form",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":217,"sourceHtmlUrl":218,"categories":219,"keywords":226,"publishedAt":55},"01M6HS6BZT2CKDNQ6YF20DXN4T","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FSKILL.md",[220,223],{"categoryNo":221,"categoryName":222,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":224,"categoryName":225,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[227,228,229,230,231,232,233,234,235,110,236,159,237,238,239,115,160,139],"slack gif creator","slack","gif","creator","validation","Tools","constraints","Animation","knowledge","me","make","Utilities","concepts"]