[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPY1A4B27F9YWV92SEF1PC":3,"skill-same:01M6HPY1A4B27F9YWV92SEF1PC":72},{"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":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":71},"01M6HPY1A4B27F9YWV92SEF1PC","gate-check",null,"Validate readiness to advance between development phases. Produces a PASS\u002FCONCERNS\u002FFAIL verdict with specific blockers and required artifacts.","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\u002Fgate-check\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"gate check","gate","check","phase","design","true","with","verdict","readiness","systems","write","read","technical","grep","advance","polish","Bash","artifacts","release","development","validate","2026-11-10 10:12:30",false,"---\nname: gate-check\ndescription: \"Validate readiness to advance between development phases. Produces a PASS\u002FCONCERNS\u002FFAIL verdict with specific blockers and required artifacts.\"\nargument-hint: \"[target-phase: systems-design | technical-setup | pre-production | production | polish | release]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Bash, Write\n---\n\n# Phase Gate Validation\n\nThis skill validates whether the project is ready to advance to the next development\nphase. It checks for required artifacts, quality standards, and blockers.\n\n**Distinct from `\u002Fproject-stage-detect`**: That skill is diagnostic (\"where are we?\").\nThis skill is prescriptive (\"are we ready to advance?\" with a formal verdict).\n\n## Production Stages (7)\n\nThe project progresses through these stages:\n\n1. **Concept** — Brainstorming, game concept document\n2. **Systems Design** — Mapping systems, writing GDDs\n3. **Technical Setup** — Engine config, architecture decisions\n4. **Pre-Production** — Prototyping, vertical slice validation\n5. **Production** — Feature development (Epic\u002FFeature\u002FTask tracking active)\n6. **Polish** — Performance, playtesting, bug fixing\n7. **Release** — Launch prep, certification\n\n**When a gate passes**, write the new stage name to `production\u002Fstage.txt`\n(single line, e.g. `Production`). This updates the status line immediately.\n\n---\n\n## 1. Parse Arguments\n\n- **With argument**: `\u002Fgate-check production` — validate readiness for that specific phase\n- **No argument**: Auto-detect current stage using the same heuristics as\n  `\u002Fproject-stage-detect`, then validate the NEXT phase transition\n\n---\n\n## 2. Phase Gate Definitions\n\n### Gate: Concept → Systems Design\n\n**Required Artifacts:**\n- [ ] `design\u002Fgdd\u002Fgame-concept.md` exists and has content\n- [ ] Game pillars defined (in concept doc or `design\u002Fgdd\u002Fgame-pillars.md`)\n\n**Quality Checks:**\n- [ ] Game concept has been reviewed (`\u002Fdesign-review` verdict not MAJOR REVISION NEEDED)\n- [ ] Core loop is described and understood\n- [ ] Target audience is identified\n\n---\n\n### Gate: Systems Design → Technical Setup\n\n**Required Artifacts:**\n- [ ] Systems index exists at `design\u002Fgdd\u002Fsystems-index.md` with at least MVP systems enumerated\n- [ ] At least 1 GDD in `design\u002Fgdd\u002F` (beyond game-concept.md and systems-index.md)\n\n**Quality Checks:**\n- [ ] GDD(s) pass design review (8 required sections present)\n- [ ] System dependencies are mapped in the systems index\n- [ ] MVP priority tier is defined\n\n---\n\n### Gate: Technical Setup → Pre-Production\n\n**Required Artifacts:**\n- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)\n- [ ] Technical preferences configured (`.claude\u002Fdocs\u002Ftechnical-preferences.md` populated)\n- [ ] At least 1 Architecture Decision Record in `docs\u002Farchitecture\u002F`\n- [ ] Engine reference docs exist in `docs\u002Fengine-reference\u002F`\n\n**Quality Checks:**\n- [ ] Architecture decisions cover core systems (rendering, input, state management)\n- [ ] Technical preferences have naming conventions and performance budgets set\n\n---\n\n### Gate: Pre-Production → Production\n\n**Required Artifacts:**\n- [ ] At least 1 prototype in `prototypes\u002F` with a README\n- [ ] First sprint plan exists in `production\u002Fsprints\u002F`\n- [ ] All MVP-tier GDDs from systems index are complete\n\n**Quality Checks:**\n- [ ] Prototype validates the core loop hypothesis\n- [ ] Sprint plan references real work items from GDDs\n- [ ] Vertical slice scope is defined\n\n---\n\n### Gate: Production → Polish\n\n**Required Artifacts:**\n- [ ] `src\u002F` has active code organized into subsystems\n- [ ] All core mechanics from GDD are implemented (cross-reference `design\u002Fgdd\u002F` with `src\u002F`)\n- [ ] Main gameplay path is playable end-to-end\n- [ ] Test files exist in `tests\u002F`\n- [ ] At least 1 playtest report (or `\u002Fplaytest-report` has been run)\n\n**Quality Checks:**\n- [ ] Tests are passing (run test suite via Bash)\n- [ ] No critical\u002Fblocker bugs in any bug tracker or known issues\n- [ ] Core loop plays as designed (compare to GDD acceptance criteria)\n- [ ] Performance is within budget (check technical-preferences.md targets)\n\n---\n\n### Gate: Polish → Release\n\n**Required Artifacts:**\n- [ ] All features from milestone plan are implemented\n- [ ] Content is complete (all levels, assets, dialogue referenced in design docs exist)\n- [ ] Localization strings are externalized (no hardcoded player-facing text in `src\u002F`)\n- [ ] QA test plan exists\n- [ ] Balance data has been reviewed (`\u002Fbalance-check` run)\n- [ ] Release checklist completed (`\u002Frelease-checklist` or `\u002Flaunch-checklist` run)\n- [ ] Store metadata prepared (if applicable)\n- [ ] Changelog \u002F patch notes drafted\n\n**Quality Checks:**\n- [ ] Full QA pass signed off by `qa-lead`\n- [ ] All tests passing\n- [ ] Performance targets met across all target platforms\n- [ ] No known critical, high, or medium-severity bugs\n- [ ] Accessibility basics covered (remapping, text scaling if applicable)\n- [ ] Localization verified for all target languages\n- [ ] Legal requirements met (EULA, privacy policy, age ratings if applicable)\n- [ ] Build compiles and packages cleanly\n\n---\n\n## 3. Run the Gate Check\n\nFor each item in the target gate:\n\n### Artifact Checks\n- Use `Glob` and `Read` to verify files exist and have meaningful content\n- Don't just check existence — verify the file has real content (not just a template header)\n- For code checks, verify directory structure and file counts\n\n### Quality Checks\n- For test checks: Run the test suite via `Bash` if a test runner is configured\n- For design review checks: `Read` the GDD and check for the 8 required sections\n- For performance checks: `Read` technical-preferences.md and compare against any\n  profiling data in `tests\u002Fperformance\u002F` or recent `\u002Fperf-profile` output\n- For localization checks: `Grep` for hardcoded strings in `src\u002F`\n\n### Cross-Reference Checks\n- Compare `design\u002Fgdd\u002F` documents against `src\u002F` implementations\n- Check that every system referenced in architecture docs has corresponding code\n- Verify sprint plans reference real work items\n\n---\n\n## 4. Collaborative Assessment\n\nFor items that can't be automatically verified, **ask the user**:\n\n- \"I can't automatically verify that the core loop plays well. Has it been playtested?\"\n- \"No playtest report found. Has informal testing been done?\"\n- \"Performance profiling data isn't available. Would you like to run `\u002Fperf-profile`?\"\n\n**Never assume PASS for unverifiable items.** Mark them as MANUAL CHECK NEEDED.\n\n---\n\n## 5. Output the Verdict\n\n```\n## Gate Check: [Current Phase] → [Target Phase]\n\n**Date**: [date]\n**Checked by**: gate-check skill\n\n### Required Artifacts: [X\u002FY present]\n- [x] design\u002Fgdd\u002Fgame-concept.md — exists, 2.4KB\n- [ ] docs\u002Farchitecture\u002F — MISSING (no ADRs found)\n- [x] production\u002Fsprints\u002F — exists, 1 sprint plan\n\n### Quality Checks: [X\u002FY passing]\n- [x] GDD has 8\u002F8 required sections\n- [ ] Tests — FAILED (3 failures in tests\u002Funit\u002F)\n- [?] Core loop playtested — MANUAL CHECK NEEDED\n\n### Blockers\n1. **No Architecture Decision Records** — Run `\u002Farchitecture-decision` to create one\n   covering core system architecture before entering production.\n2. **3 test failures** — Fix failing tests in tests\u002Funit\u002F before advancing.\n\n### Recommendations\n- [Priority actions to resolve blockers]\n- [Optional improvements that aren't blocking]\n\n### Verdict: [PASS \u002F CONCERNS \u002F FAIL]\n- **PASS**: All required artifacts present, all quality checks passing\n- **CONCERNS**: Minor gaps exist but can be addressed during the next phase\n- **FAIL**: Critical blockers must be resolved before advancing\n```\n\n---\n\n## 6. Update Stage on PASS\n\nWhen the verdict is **PASS** and the user confirms they want to advance:\n\n1. Write the new stage name to `production\u002Fstage.txt` (single line, no trailing newline)\n2. This immediately updates the status line for all future sessions\n\nExample: if passing the \"Pre-Production → Production\" gate:\n```bash\necho -n \"Production\" > production\u002Fstage.txt\n```\n\n**Always ask before writing**: \"Gate passed. May I update `production\u002Fstage.txt` to 'Production'?\"\n\n---\n\n## 7. Follow-Up Actions\n\nBased on the verdict, suggest specific next steps:\n\n- **No game concept?** → `\u002Fbrainstorm` to create one\n- **No systems index?** → `\u002Fmap-systems` to decompose the concept into systems\n- **Missing design docs?** → `\u002Freverse-document` or delegate to `game-designer`\n- **Missing ADRs?** → `\u002Farchitecture-decision`\n- **Tests failing?** → delegate to `lead-programmer` or `qa-tester`\n- **No playtest data?** → `\u002Fplaytest-report`\n- **Performance unknown?** → `\u002Fperf-profile`\n- **Not localized?** → `\u002Flocalize`\n- **Ready for release?** → `\u002Flaunch-checklist`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Scan first**: Check all artifacts and quality gates\n2. **Ask about unknowns**: Don't assume PASS for things you can't verify\n3. **Present findings**: Show the full checklist with status\n4. **User decides**: The verdict is a recommendation — the user makes the final call\n5. **Get approval**: \"May I write this gate check report to production\u002Fgate-checks\u002F?\"\n\n**Never** block a user from advancing — the verdict is advisory. Document the risks\nand let the user decide whether to proceed despite concerns.\n","# Phase Gate Validation\n\nThis skill validates whether the project is ready to advance to the next development\nphase. It checks for required artifacts, quality standards, and blockers.\n\n**Distinct from `\u002Fproject-stage-detect`**: That skill is diagnostic (\"where are we?\").\nThis skill is prescriptive (\"are we ready to advance?\" with a formal verdict).\n\n## Production Stages (7)\n\nThe project progresses through these stages:\n\n1. **Concept** — Brainstorming, game concept document\n2. **Systems Design** — Mapping systems, writing GDDs\n3. **Technical Setup** — Engine config, architecture decisions\n4. **Pre-Production** — Prototyping, vertical slice validation\n5. **Production** — Feature development (Epic\u002FFeature\u002FTask tracking active)\n6. **Polish** — Performance, playtesting, bug fixing\n7. **Release** — Launch prep, certification\n\n**When a gate passes**, write the new stage name to `production\u002Fstage.txt`\n(single line, e.g. `Production`). This updates the status line immediately.\n\n---\n\n## 1. Parse Arguments\n\n- **With argument**: `\u002Fgate-check production` — validate readiness for that specific phase\n- **No argument**: Auto-detect current stage using the same heuristics as\n  `\u002Fproject-stage-detect`, then validate the NEXT phase transition\n\n---\n\n## 2. Phase Gate Definitions\n\n### Gate: Concept → Systems Design\n\n**Required Artifacts:**\n- [ ] `design\u002Fgdd\u002Fgame-concept.md` exists and has content\n- [ ] Game pillars defined (in concept doc or `design\u002Fgdd\u002Fgame-pillars.md`)\n\n**Quality Checks:**\n- [ ] Game concept has been reviewed (`\u002Fdesign-review` verdict not MAJOR REVISION NEEDED)\n- [ ] Core loop is described and understood\n- [ ] Target audience is identified\n\n---\n\n### Gate: Systems Design → Technical Setup\n\n**Required Artifacts:**\n- [ ] Systems index exists at `design\u002Fgdd\u002Fsystems-index.md` with at least MVP systems enumerated\n- [ ] At least 1 GDD in `design\u002Fgdd\u002F` (beyond game-concept.md and systems-index.md)\n\n**Quality Checks:**\n- [ ] GDD(s) pass design review (8 required sections present)\n- [ ] System dependencies are mapped in the systems index\n- [ ] MVP priority tier is defined\n\n---\n\n### Gate: Technical Setup → Pre-Production\n\n**Required Artifacts:**\n- [ ] Engine chosen (CLAUDE.md Technology Stack is not `[CHOOSE]`)\n- [ ] Technical preferences configured (`.claude\u002Fdocs\u002Ftechnical-preferences.md` populated)\n- [ ] At least 1 Architecture Decision Record in `docs\u002Farchitecture\u002F`\n- [ ] Engine reference docs exist in `docs\u002Fengine-reference\u002F`\n\n**Quality Checks:**\n- [ ] Architecture decisions cover core systems (rendering, input, state management)\n- [ ] Technical preferences have naming conventions and performance budgets set\n\n---\n\n### Gate: Pre-Production → Production\n\n**Required Artifacts:**\n- [ ] At least 1 prototype in `prototypes\u002F` with a README\n- [ ] First sprint plan exists in `production\u002Fsprints\u002F`\n- [ ] All MVP-tier GDDs from systems index are complete\n\n**Quality Checks:**\n- [ ] Prototype validates the core loop hypothesis\n- [ ] Sprint plan references real work items from GDDs\n- [ ] Vertical slice scope is defined\n\n---\n\n### Gate: Production → Polish\n\n**Required Artifacts:**\n- [ ] `src\u002F` has active code organized into subsystems\n- [ ] All core mechanics from GDD are implemented (cross-reference `design\u002Fgdd\u002F` with `src\u002F`)\n- [ ] Main gameplay path is playable end-to-end\n- [ ] Test files exist in `tests\u002F`\n- [ ] At least 1 playtest report (or `\u002Fplaytest-report` has been run)\n\n**Quality Checks:**\n- [ ] Tests are passing (run test suite via Bash)\n- [ ] No critical\u002Fblocker bugs in any bug tracker or known issues\n- [ ] Core loop plays as designed (compare to GDD acceptance criteria)\n- [ ] Performance is within budget (check technical-preferences.md targets)\n\n---\n\n### Gate: Polish → Release\n\n**Required Artifacts:**\n- [ ] All features from milestone plan are implemented\n- [ ] Content is complete (all levels, assets, dialogue referenced in design docs exist)\n- [ ] Localization strings are externalized (no hardcoded player-facing text in `src\u002F`)\n- [ ] QA test plan exists\n- [ ] Balance data has been reviewed (`\u002Fbalance-check` run)\n- [ ] Release checklist completed (`\u002Frelease-checklist` or `\u002Flaunch-checklist` run)\n- [ ] Store metadata prepared (if applicable)\n- [ ] Changelog \u002F patch notes drafted\n\n**Quality Checks:**\n- [ ] Full QA pass signed off by `qa-lead`\n- [ ] All tests passing\n- [ ] Performance targets met across all target platforms\n- [ ] No known critical, high, or medium-severity bugs\n- [ ] Accessibility basics covered (remapping, text scaling if applicable)\n- [ ] Localization verified for all target languages\n- [ ] Legal requirements met (EULA, privacy policy, age ratings if applicable)\n- [ ] Build compiles and packages cleanly\n\n---\n\n## 3. Run the Gate Check\n\nFor each item in the target gate:\n\n### Artifact Checks\n- Use `Glob` and `Read` to verify files exist and have meaningful content\n- Don't just check existence — verify the file has real content (not just a template header)\n- For code checks, verify directory structure and file counts\n\n### Quality Checks\n- For test checks: Run the test suite via `Bash` if a test runner is configured\n- For design review checks: `Read` the GDD and check for the 8 required sections\n- For performance checks: `Read` technical-preferences.md and compare against any\n  profiling data in `tests\u002Fperformance\u002F` or recent `\u002Fperf-profile` output\n- For localization checks: `Grep` for hardcoded strings in `src\u002F`\n\n### Cross-Reference Checks\n- Compare `design\u002Fgdd\u002F` documents against `src\u002F` implementations\n- Check that every system referenced in architecture docs has corresponding code\n- Verify sprint plans reference real work items\n\n---\n\n## 4. Collaborative Assessment\n\nFor items that can't be automatically verified, **ask the user**:\n\n- \"I can't automatically verify that the core loop plays well. Has it been playtested?\"\n- \"No playtest report found. Has informal testing been done?\"\n- \"Performance profiling data isn't available. Would you like to run `\u002Fperf-profile`?\"\n\n**Never assume PASS for unverifiable items.** Mark them as MANUAL CHECK NEEDED.\n\n---\n\n## 5. Output the Verdict\n\n```\n## Gate Check: [Current Phase] → [Target Phase]\n\n**Date**: [date]\n**Checked by**: gate-check skill\n\n### Required Artifacts: [X\u002FY present]\n- [x] design\u002Fgdd\u002Fgame-concept.md — exists, 2.4KB\n- [ ] docs\u002Farchitecture\u002F — MISSING (no ADRs found)\n- [x] production\u002Fsprints\u002F — exists, 1 sprint plan\n\n### Quality Checks: [X\u002FY passing]\n- [x] GDD has 8\u002F8 required sections\n- [ ] Tests — FAILED (3 failures in tests\u002Funit\u002F)\n- [?] Core loop playtested — MANUAL CHECK NEEDED\n\n### Blockers\n1. **No Architecture Decision Records** — Run `\u002Farchitecture-decision` to create one\n   covering core system architecture before entering production.\n2. **3 test failures** — Fix failing tests in tests\u002Funit\u002F before advancing.\n\n### Recommendations\n- [Priority actions to resolve blockers]\n- [Optional improvements that aren't blocking]\n\n### Verdict: [PASS \u002F CONCERNS \u002F FAIL]\n- **PASS**: All required artifacts present, all quality checks passing\n- **CONCERNS**: Minor gaps exist but can be addressed during the next phase\n- **FAIL**: Critical blockers must be resolved before advancing\n```\n\n---\n\n## 6. Update Stage on PASS\n\nWhen the verdict is **PASS** and the user confirms they want to advance:\n\n1. Write the new stage name to `production\u002Fstage.txt` (single line, no trailing newline)\n2. This immediately updates the status line for all future sessions\n\nExample: if passing the \"Pre-Production → Production\" gate:\n```bash\necho -n \"Production\" > production\u002Fstage.txt\n```\n\n**Always ask before writing**: \"Gate passed. May I update `production\u002Fstage.txt` to 'Production'?\"\n\n---\n\n## 7. Follow-Up Actions\n\nBased on the verdict, suggest specific next steps:\n\n- **No game concept?** → `\u002Fbrainstorm` to create one\n- **No systems index?** → `\u002Fmap-systems` to decompose the concept into systems\n- **Missing design docs?** → `\u002Freverse-document` or delegate to `game-designer`\n- **Missing ADRs?** → `\u002Farchitecture-decision`\n- **Tests failing?** → delegate to `lead-programmer` or `qa-tester`\n- **No playtest data?** → `\u002Fplaytest-report`\n- **Performance unknown?** → `\u002Fperf-profile`\n- **Not localized?** → `\u002Flocalize`\n- **Ready for release?** → `\u002Flaunch-checklist`\n\n---\n\n## Collaborative Protocol\n\nThis skill follows the collaborative design principle:\n\n1. **Scan first**: Check all artifacts and quality gates\n2. **Ask about unknowns**: Don't assume PASS for things you can't verify\n3. **Present findings**: Show the full checklist with status\n4. **User decides**: The verdict is a recommendation — the user makes the final call\n5. **Get approval**: \"May I write this gate check report to production\u002Fgate-checks\u002F?\"\n\n**Never** block a user from advancing — the verdict is advisory. Document the risks\nand let the user decide whether to proceed despite concerns.\n",{"name":5,"description":7,"allowed-tools":49,"argument-hint":50,"user-invocable":51},"Read, Glob, Grep, Bash, Write","[target-phase: systems-design | technical-setup | pre-production | production | polish | release]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fgate-check",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":60,"prompt":70,"zipAvailable":51},[61,64,67],{"tool":62,"command":63},"npx","npx skills add welflau\u002Fai-dev-system --skill gate-check",{"tool":65,"command":66},"bunx","bunx skills add welflau\u002Fai-dev-system --skill gate-check",{"tool":68,"command":69},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill gate-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Fgate-check\u002FSKILL.md",[],[73,105,134,159,186,210],{"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":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":87,"publishedAt":104},"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",[81,84],{"categoryNo":82,"categoryName":83,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,29,103],"testing","webapp testing","webapp","frontend","screenshots","playwright","web","debugging","toolkit","browser","ui","logs","applications","behavior","local","for","2026-11-11 15:11:14",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":115,"publishedAt":104},"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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通",[116,117,118,119,120,33,121,122,123,124,125,126,127,128,129,130,131,132,133],"internal comms","comms","status","help","SET","use","reports","me","incident","leadership","project","resources","communications","internal communications","formats","sort","my","updates",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":44},"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",[141],{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},[143,94,40,144,145,91,146,147,148,149,150,151,152,153,121,154,155,156,157,103,158],"web artifacts builder","artifacts builder","builder","css","components","react","routing","state management","state","file","Tailwind","single-file","simple","ui components","multi","single",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":173,"publishedAt":44},"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",[166,167,168],{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":169,"categoryName":170,"taxonomyType":171,"taxonomyTypeDesc":172},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[91,27,174,146,94,147,148,175,176,177,40,178,100,179,121,180,181,182,183,29,184,185],"frontend design","react components","create","code","examples","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":194,"publishedAt":44},"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",[193],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[195,196,197,176,177,198,199,200,201,121,202,203,32,204,29,205,206,207,208,209,185],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","users","Existing","request","generative","copyright","fields",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":214,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":44},"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",[217],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[219,220,221,222,96,223,40,120,224,225,179,226,227,181,228,29,229,230,231,103,232,233],"theme factory","factory","theme","docs","generate","fly","slides","styling","artifact","themes","you","fonts","can","apply","new"]