[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C58X5ZTDWVG4RK8AQJ53P":3,"skill-same:01M71C58X5ZTDWVG4RK8AQJ53P":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M71C58X5ZTDWVG4RK8AQJ53P","output-guard",null,"Anti-incomplete-output protocol. Prevents AI from leaving work unfinished, generating placeholder content, or stopping mid-implementation. Use when quality-critical output is required.","yqecea\u002Fgem-swarm","yqecea","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196189405?v=4","01M71C12KWH5QPTE12J69335KF","Yusuf","01M71C12MFS3BRGNE5SSHB4DY9",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Foutput-guard\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"guard","output","output guard","use","critical","when","placeholder","work","quality","protocol","implementation","content","2026-11-10 10:12:30",false,"---\nname: output-guard\ndescription: Anti-incomplete-output protocol. Prevents AI from leaving work unfinished, generating placeholder content, or stopping mid-implementation. Use when quality-critical output is required.\n---\n\n# Output Guard Skill\n\nPrevents the most common AI failure mode: **stopping before the work is done.**\n\n## Problem Statement\n\nAI models frequently:\n- Generate the first 60% of a file and stop with `\u002F\u002F ... rest of implementation`\n- Create component stubs without actual logic\n- Leave `TODO` comments as if someone else will finish\n- Produce a hero section and skip the rest of the page\n- Generate CSS for desktop and skip mobile entirely\n- Build the happy path and ignore error\u002Floading\u002Fempty states\n\nThis skill enforces completion.\n\n## Completion Rules (MANDATORY)\n\n### Rule 1: No Placeholders\n```\nFORBIDDEN tokens in any output:\n- \u002F\u002F TODO\n- \u002F\u002F ... rest of implementation\n- \u002F\u002F implement here\n- \u002F\u002F add more as needed\n- {\u002F* placeholder *\u002F}\n- Lorem ipsum (unless explicitly a design placeholder)\n- \"Coming soon\" sections\n- Empty function bodies\n- Commented-out code blocks as \"examples\"\n```\n\nIf you cannot complete a section, state WHY and what is needed — do not leave a stub.\n\n### Rule 2: Every File is Complete\nA file is complete when:\n- [ ] All imports resolve to real modules\n- [ ] All functions have real implementations (not stubs)\n- [ ] All types\u002Finterfaces are fully defined\n- [ ] All error handling is implemented (not just `catch (e) {}`)\n- [ ] All component states are handled (loading, error, empty, success)\n- [ ] The file would pass `tsc --noEmit` and linting\n\n### Rule 3: Every Page is Complete\nA page is complete when:\n- [ ] ALL sections are implemented (not just hero + one section)\n- [ ] Responsive layout works at 375px, 768px, 1024px, 1440px\n- [ ] All interactive elements have hover\u002Ffocus\u002Factive states\n- [ ] Navigation actually navigates (no dead links)\n- [ ] Forms actually submit (or have clear disabled states)\n- [ ] Images have actual `src` attributes (not empty or broken)\n\n### Rule 4: Every Component is Complete\nA component is complete when:\n- [ ] All props are typed and documented\n- [ ] Default\u002Fhover\u002Ffocus\u002Factive\u002Fdisabled states exist\n- [ ] Keyboard navigation works (Tab, Enter, Escape)\n- [ ] Screen readers can announce it properly (ARIA)\n- [ ] It renders correctly in light and dark modes (if applicable)\n\n### Rule 5: Self-Audit Before Reporting Done\nBefore saying \"task complete\", verify:\n\n```\nCOMPLETION CHECKLIST (answer honestly):\n1. Did I implement EVERY section mentioned in the brief? (not just the interesting ones)\n2. Did I handle ALL breakpoints? (not just desktop)\n3. Did I add ALL interactive states? (not just default)\n4. Did I leave ANY TODO\u002Fplaceholder\u002Fstub? (search the output)\n5. Would this ship to production AS-IS? (not \"with minor tweaks\")\n```\n\nIf ANY answer is \"no\" → finish the work before reporting done.\n\n## Enforcement Mechanism\n\nWhen this skill is active, the orchestrator or reviewing agent should check for:\n\n1. **Grep scan**: Search all created\u002Fmodified files for forbidden tokens\n2. **Section count**: Compare brief requirements to actual implemented sections\n3. **Breakpoint check**: Verify responsive rules exist (not just desktop CSS)\n4. **State coverage**: Check that components handle more than just the happy path\n\n## Integration with Review Pipeline\n\nThe Automatic Quality Review Pipeline (from implementation-planning) should include output completeness as part of its Design Compliance review dimension. Incomplete output is a **Critical** severity finding.\n","# Output Guard Skill\n\nPrevents the most common AI failure mode: **stopping before the work is done.**\n\n## Problem Statement\n\nAI models frequently:\n- Generate the first 60% of a file and stop with `\u002F\u002F ... rest of implementation`\n- Create component stubs without actual logic\n- Leave `TODO` comments as if someone else will finish\n- Produce a hero section and skip the rest of the page\n- Generate CSS for desktop and skip mobile entirely\n- Build the happy path and ignore error\u002Floading\u002Fempty states\n\nThis skill enforces completion.\n\n## Completion Rules (MANDATORY)\n\n### Rule 1: No Placeholders\n```\nFORBIDDEN tokens in any output:\n- \u002F\u002F TODO\n- \u002F\u002F ... rest of implementation\n- \u002F\u002F implement here\n- \u002F\u002F add more as needed\n- {\u002F* placeholder *\u002F}\n- Lorem ipsum (unless explicitly a design placeholder)\n- \"Coming soon\" sections\n- Empty function bodies\n- Commented-out code blocks as \"examples\"\n```\n\nIf you cannot complete a section, state WHY and what is needed — do not leave a stub.\n\n### Rule 2: Every File is Complete\nA file is complete when:\n- [ ] All imports resolve to real modules\n- [ ] All functions have real implementations (not stubs)\n- [ ] All types\u002Finterfaces are fully defined\n- [ ] All error handling is implemented (not just `catch (e) {}`)\n- [ ] All component states are handled (loading, error, empty, success)\n- [ ] The file would pass `tsc --noEmit` and linting\n\n### Rule 3: Every Page is Complete\nA page is complete when:\n- [ ] ALL sections are implemented (not just hero + one section)\n- [ ] Responsive layout works at 375px, 768px, 1024px, 1440px\n- [ ] All interactive elements have hover\u002Ffocus\u002Factive states\n- [ ] Navigation actually navigates (no dead links)\n- [ ] Forms actually submit (or have clear disabled states)\n- [ ] Images have actual `src` attributes (not empty or broken)\n\n### Rule 4: Every Component is Complete\nA component is complete when:\n- [ ] All props are typed and documented\n- [ ] Default\u002Fhover\u002Ffocus\u002Factive\u002Fdisabled states exist\n- [ ] Keyboard navigation works (Tab, Enter, Escape)\n- [ ] Screen readers can announce it properly (ARIA)\n- [ ] It renders correctly in light and dark modes (if applicable)\n\n### Rule 5: Self-Audit Before Reporting Done\nBefore saying \"task complete\", verify:\n\n```\nCOMPLETION CHECKLIST (answer honestly):\n1. Did I implement EVERY section mentioned in the brief? (not just the interesting ones)\n2. Did I handle ALL breakpoints? (not just desktop)\n3. Did I add ALL interactive states? (not just default)\n4. Did I leave ANY TODO\u002Fplaceholder\u002Fstub? (search the output)\n5. Would this ship to production AS-IS? (not \"with minor tweaks\")\n```\n\nIf ANY answer is \"no\" → finish the work before reporting done.\n\n## Enforcement Mechanism\n\nWhen this skill is active, the orchestrator or reviewing agent should check for:\n\n1. **Grep scan**: Search all created\u002Fmodified files for forbidden tokens\n2. **Section count**: Compare brief requirements to actual implemented sections\n3. **Breakpoint check**: Verify responsive rules exist (not just desktop CSS)\n4. **State coverage**: Check that components handle more than just the happy path\n\n## Integration with Review Pipeline\n\nThe Automatic Quality Review Pipeline (from implementation-planning) should include output completeness as part of its Design Compliance review dimension. Incomplete output is a **Critical** severity finding.\n",{"name":5,"description":7},"main","923c514d4d5e15bbfd65ec7eaf949a997679aa3e","src\u002Fskills\u002Fdomain\u002Foutput-guard","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm","https:\u002F\u002Fgithub.com\u002Fyqecea","15 y.o Data Science,Student","2026-04-26 20:00:27",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add yqecea\u002Fgem-swarm --skill output-guard",{"tool":49,"command":50},"bunx","bunx skills add yqecea\u002Fgem-swarm --skill output-guard",{"tool":52,"command":53},"pnpm","pnpm dlx skills add yqecea\u002Fgem-swarm --skill output-guard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fdomain\u002Foutput-guard\u002FSKILL.md",true,[],[58,72,86,96,108,133],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":31},"01M71C74XVPP23ST10E8MYJZA0","validation","Cross-cutting validation methodology for verifying phase outputs and project integrity","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fvalidation\u002FSKILL.md",[],[60,65,66,67,68,69,70,71],"validation methodology","for","project","outputs","phase","methodology","integrity",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":31},"01M71C72PTKRV481M975R3QDDE","session-management","Manages orchestration session state, tracking, and resumption","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fsession-management\u002FSKILL.md",[],[79,80,81,82,83,84,85],"session management","session","management","session state","orchestration","state","tracking",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":31},"01M71C6ZY1EGM4SGVYT4B2HHD7","implementation-planning","Generates detailed implementation plans from finalized designs","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fimplementation-planning\u002FSKILL.md",[],[93,29,94,95],"planning","implementation planning","plans",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":31},"01M71C6XQVGMDFJ50BP5SBDS76","execution","Phase execution methodology for orchestration workflows with error handling and completion protocols","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fexecution\u002FSKILL.md",[],[98,66,70,103,104,83,69,105,106,107],"error","workflows","protocols","error handling","with",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":124,"publishedAt":31},"01M71C6VY8APWMNK1XEJ3WP7A2","design-dialogue","Guides structured design conversations for complex engineering tasks","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdesign-dialogue\u002FSKILL.md",[114,119],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[125,126,127,128,129,66,130,131,132],"dialogue","design","design dialogue","guides","conversations","tasks","engineering","structured",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":145,"publishedAt":31},"01M71C6R4RJWG3S2R26778TPD8","delegation","Agent delegation best practices for constructing effective subagent prompts with proper scoping","https:\u002F\u002Fgithub.com\u002Fyqecea\u002Fgem-swarm\u002Fblob\u002Fmain\u002Fsrc\u002Fskills\u002Fshared\u002Fdelegation\u002FSKILL.md",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":143,"categoryName":144,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000023","Skill与智能体开发",[135,146,147,66,148,107,149],"subagent","scoping","best practices","prompts"]