[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DRN09QR2Q3F1WJ5FJAG8JS":3,"skill-same:01M6DRN09QR2Q3F1WJ5FJAG8JS":86},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6DRN09QR2Q3F1WJ5FJAG8JS","design-foundation",null,"Generate a project's .claude\u002Frules\u002Fdesign.md design declaration — ground in the product's subject, derive a compact token system, self-check every choice against the generic default, then write the declaration the review and implementation sides both read.","Koroqe\u002Fclaude-code-sdlc","Koroqe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F24411116?v=4","01M6DRMM7GVYYXKEW474YPDVNG","Aleksei Korobeinikov","01M6DRMMBZ82MW04MVQ3Q9M5N5",53,"MIT","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-foundation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"design foundation","foundation","design","write","token","project","focus","self","compact","default","implementation","read","check","grep","Rules","choice","system","product","generate","review","2026-11-10 10:12:30",false,"---\ndescription: Generate a project's .claude\u002Frules\u002Fdesign.md design declaration — ground in the product's subject, derive a compact token system, self-check every choice against the generic default, then write the declaration the review and implementation sides both read.\nargument-hint: \"[focus]\"\narguments: [focus]\nallowed-tools: Read, Glob, Grep, Write, AskUserQuestion\n---\n\n# Command: Design Foundation\n\nGenerate `.claude\u002Frules\u002Fdesign.md` — the project's design declaration. The harness ships the frame; this skill derives the project's own taste from its subject and writes it down, so every later UI slice extends one declared system instead of improvising a new one.\n\n## Arguments\n\n`$focus` (also available as `$ARGUMENTS`) optionally names a surface, route, or area to prioritize during grounding. When absent, ground the whole product.\n\n## Invocation Context (determine FIRST)\n\nTwo paths reach this skill, and they differ in exactly one behavior:\n\n- **Standalone \u002F interactive** — the developer invoked `\u002Fdesign-foundation` directly. `AskUserQuestion` is available for grounding gaps.\n- **Unattended — triggered from `\u002Fbootstrap-feature`** — the pipeline reached this skill mid-run with nobody watching. **Never call `AskUserQuestion` here, and never stall waiting for an answer.** Degrade to best-effort inference from the repository, and for anything that cannot be inferred write an explicitly labeled placeholder into the generated file — e.g. `TODO(design-foundation): confirm the primary audience`. An unattended run always completes.\n\nIf the invocation path cannot be positively determined, treat the run as unattended — ambiguity resolves to the path that cannot stall.\n\n## Process\n\n### 1. Subject Grounding\n\nRead the repository before asking anyone anything:\n\n- the package\u002Fapp manifest and README — what the product is and claims to do\n- routes, page\u002Fscreen files, navigation — the key surfaces\n- user-facing copy — who the audience is and what register the product speaks in\n\nFrom these, state: the concrete product, its audience, and, for each key surface, the single job that surface does. The subject's own world — its materials, instruments, vernacular — is where distinctive design choices come from; a generic template is where they go to die.\n\nAsk via `AskUserQuestion` ONLY what cannot be inferred from the repository, and ONLY on the standalone path (see Invocation Context). Never ask a question the repository already answers.\n\n### 2. Token Derivation\n\nDerive a compact system, every token named and justified by the grounding:\n\n- **Colors:** 4-6 named colors. A dominant color plus one sharp accent beats a timid, evenly-spread palette.\n- **Typography:** at least 2 font roles (e.g. heading\u002Fbody, or sans\u002Fmono), each with a real fallback stack ending in a generic family — never a bare single font name.\n- **Motion:** duration and easing tokens — a small named scale, not ad hoc per-animation values.\n- **Spacing:** one spacing basis (a base unit or scale) that layouts multiply.\n- **Signature:** one signature element — the single recognizable move that belongs to this product and no other.\n\n**Existing tokens are the source of truth.** When the project already declares tokens — a `globals.css`, a Tailwind theme\u002Fconfig, a design-tokens file — document THOSE as the system and extend only where a genuine gap exists; inventing a parallel system beside them is a defect, not a contribution. Where existing UI is generic, record that as a finding in the report; do not touch application code — the only file this skill writes is `.claude\u002Frules\u002Fdesign.md`.\n\n### 3. Self-Check Pass\n\nFor every derived choice, ask: **would this choice fit any similar product equally well?** If yes, it is a default, not a decision — revise it until it could only belong to this subject, and state in the report what this pass changed and why. This is a judgment test, not a ban-list: no specific color or font is forbidden; interchangeability is the defect.\n\n### 4. Write the Declaration\n\nWrite `.claude\u002Frules\u002Fdesign.md` respecting the template's section shape (mirrored from the harness's `templates\u002Frules\u002Fdesign.md`): Design System Source of Truth, Component Library, Typography, Motion Tokens, Aesthetic Direction, the optional project-authored Ban-List, Preview, and the optional AI Interface Patterns section (pattern vocabulary only, never code). Fill what grounding and derivation produced; leave what only the project can supply — the `## Preview` launch command above all — as a labeled `TODO` scaffold rather than a guess.\n\n**Re-run on an existing `design.md`:** read the existing file first, then write the complete revised file — carrying forward every retained section — and report the delta: what was added, what changed, what was kept. Never silently overwrite an existing declaration.\n\nClose with a short report: the grounding (product, audience, surface jobs), the derived tokens with one-line justifications, what the self-check changed, and any findings (generic existing UI, gaps left as `TODO`).\n\n## Rules\n\n- Every example in the generated file is generic or invented — never name a real product, brand, or company as a reference.\n- Everything derives from the repository and, on the interactive path, the developer's answers; fetch nothing from any external service.\n- The single write target is `.claude\u002Frules\u002Fdesign.md`. Application code, docs, and configs are read, never modified.\n","# Command: Design Foundation\n\nGenerate `.claude\u002Frules\u002Fdesign.md` — the project's design declaration. The harness ships the frame; this skill derives the project's own taste from its subject and writes it down, so every later UI slice extends one declared system instead of improvising a new one.\n\n## Arguments\n\n`$focus` (also available as `$ARGUMENTS`) optionally names a surface, route, or area to prioritize during grounding. When absent, ground the whole product.\n\n## Invocation Context (determine FIRST)\n\nTwo paths reach this skill, and they differ in exactly one behavior:\n\n- **Standalone \u002F interactive** — the developer invoked `\u002Fdesign-foundation` directly. `AskUserQuestion` is available for grounding gaps.\n- **Unattended — triggered from `\u002Fbootstrap-feature`** — the pipeline reached this skill mid-run with nobody watching. **Never call `AskUserQuestion` here, and never stall waiting for an answer.** Degrade to best-effort inference from the repository, and for anything that cannot be inferred write an explicitly labeled placeholder into the generated file — e.g. `TODO(design-foundation): confirm the primary audience`. An unattended run always completes.\n\nIf the invocation path cannot be positively determined, treat the run as unattended — ambiguity resolves to the path that cannot stall.\n\n## Process\n\n### 1. Subject Grounding\n\nRead the repository before asking anyone anything:\n\n- the package\u002Fapp manifest and README — what the product is and claims to do\n- routes, page\u002Fscreen files, navigation — the key surfaces\n- user-facing copy — who the audience is and what register the product speaks in\n\nFrom these, state: the concrete product, its audience, and, for each key surface, the single job that surface does. The subject's own world — its materials, instruments, vernacular — is where distinctive design choices come from; a generic template is where they go to die.\n\nAsk via `AskUserQuestion` ONLY what cannot be inferred from the repository, and ONLY on the standalone path (see Invocation Context). Never ask a question the repository already answers.\n\n### 2. Token Derivation\n\nDerive a compact system, every token named and justified by the grounding:\n\n- **Colors:** 4-6 named colors. A dominant color plus one sharp accent beats a timid, evenly-spread palette.\n- **Typography:** at least 2 font roles (e.g. heading\u002Fbody, or sans\u002Fmono), each with a real fallback stack ending in a generic family — never a bare single font name.\n- **Motion:** duration and easing tokens — a small named scale, not ad hoc per-animation values.\n- **Spacing:** one spacing basis (a base unit or scale) that layouts multiply.\n- **Signature:** one signature element — the single recognizable move that belongs to this product and no other.\n\n**Existing tokens are the source of truth.** When the project already declares tokens — a `globals.css`, a Tailwind theme\u002Fconfig, a design-tokens file — document THOSE as the system and extend only where a genuine gap exists; inventing a parallel system beside them is a defect, not a contribution. Where existing UI is generic, record that as a finding in the report; do not touch application code — the only file this skill writes is `.claude\u002Frules\u002Fdesign.md`.\n\n### 3. Self-Check Pass\n\nFor every derived choice, ask: **would this choice fit any similar product equally well?** If yes, it is a default, not a decision — revise it until it could only belong to this subject, and state in the report what this pass changed and why. This is a judgment test, not a ban-list: no specific color or font is forbidden; interchangeability is the defect.\n\n### 4. Write the Declaration\n\nWrite `.claude\u002Frules\u002Fdesign.md` respecting the template's section shape (mirrored from the harness's `templates\u002Frules\u002Fdesign.md`): Design System Source of Truth, Component Library, Typography, Motion Tokens, Aesthetic Direction, the optional project-authored Ban-List, Preview, and the optional AI Interface Patterns section (pattern vocabulary only, never code). Fill what grounding and derivation produced; leave what only the project can supply — the `## Preview` launch command above all — as a labeled `TODO` scaffold rather than a guess.\n\n**Re-run on an existing `design.md`:** read the existing file first, then write the complete revised file — carrying forward every retained section — and report the delta: what was added, what changed, what was kept. Never silently overwrite an existing declaration.\n\nClose with a short report: the grounding (product, audience, surface jobs), the derived tokens with one-line justifications, what the self-check changed, and any findings (generic existing UI, gaps left as `TODO`).\n\n## Rules\n\n- Every example in the generated file is generic or invented — never name a real product, brand, or company as a reference.\n- Everything derives from the repository and, on the interactive path, the developer's answers; fetch nothing from any external service.\n- The single write target is `.claude\u002Frules\u002Fdesign.md`. Application code, docs, and configs are read, never modified.\n",{"arguments":54,"description":7,"allowed-tools":55,"argument-hint":56},[35],"Read, Glob, Grep, Write, AskUserQuestion","[focus]","main","262994376445c2281eca0784698159bb6e1bf1a3","skills\u002Fdesign-foundation",3,"https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc","https:\u002F\u002Fgithub.com\u002FKoroqe","https:\u002F\u002Fcone.red\u002Fteam\u002Faleksei-korobeinikov","Co-founder of GetDeal.ai and CONE RED. Author of claude-code-sdlc and OPOS.","2026-10-23 20:51:28",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add Koroqe\u002Fclaude-code-sdlc --skill design-foundation",{"tool":72,"command":73},"bunx","bunx skills add Koroqe\u002Fclaude-code-sdlc --skill design-foundation",{"tool":75,"command":76},"pnpm","pnpm dlx skills add Koroqe\u002Fclaude-code-sdlc --skill design-foundation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-foundation\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"index.json","REFERENCE","参考文档",568,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Flinux-forensic-disk-analysis-slack-recover\u002Findex.json",[87,121,138,154,175,184],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":103,"publishedAt":49},"01M6DRTXKTXP8HYDW2G274KAKK","merge-ready","Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI\u002FUX — then write the changelog entry.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fmerge-ready\u002FSKILL.md",[93,96,99,102],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":100,"categoryName":101,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[104,105,106,107,48,108,109,110,111,112,113,114,115,116,117,118,40,32,119,120],"merge","ready","merge ready","code review","documentation","run","code","git","verification","changelog","ux","audit","doc","security audit","Bash","edit","goal",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":49},"01M6DRTT500DJJ8XNQX16037VM","implement-slice","Implement the next smallest slice from the current plan using TDD — tests first, then code, then verification, then an atomic commit. Reads the plan from the scratchpad.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fimplement-slice\u002FSKILL.md",[127],{"categoryNo":100,"categoryName":101,"taxonomyType":26,"taxonomyTypeDesc":27},[129,130,131,132,110,112,113,133,118,134,42,40,32,119,135,136,137],"implement","implement slice","tdd","commit","first","plan","next","atomic commit","tests",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":49},"01M6DRTPT1Y4NPEQM56VA4PP0Q","develop-feature","Autonomously implement a complete feature from request to merge-ready — documentation phase, wave-based TDD implementation, then all quality gates, without stopping for human input.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fdevelop-feature\u002FSKILL.md",[],[145,146,147,129,131,104,108,148,118,149,42,40,32,119,105,39,150,151,152,153],"develop","feature","develop feature","quality gates","quality","human","gates","input","complete",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":164,"publishedAt":49},"01M6DRTHJG9KBEG33WNJBRBAFH","bootstrap-feature","Run the documentation phase of the SDLC pipeline for a feature — PRD, use cases, architecture review, QA test cases, implementation plan, feature branch and scratchpad. Produces no code.","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-verdicts\u002Fskills\u002Fbootstrap-feature\u002FSKILL.md",[160,161],{"categoryNo":100,"categoryName":101,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":162,"categoryName":163,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[165,166,146,48,167,108,168,109,110,169,170,171,118,134,172,40,32,119,173,174],"bootstrap","bootstrap feature","architecture","architecture review","qa","pipeline","qa test","branch","use","no code",{"skillNo":176,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":49},"01M6DRTDYFS4S3T8MQE4PZHZ7X","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fmerge-ready\u002FSKILL.md",[179,180,181,182],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":100,"categoryName":101,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[104,105,106,107,48,108,109,110,111,112,113,114,115,116,117,118,40,32,119,120],{"skillNo":185,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":49},"01M6DRTAW68GF6JGNDEWTF6B4V","https:\u002F\u002Fgithub.com\u002FKoroqe\u002Fclaude-code-sdlc\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fci\u002Fverification-upgrade\u002Fbad-verifier-tools\u002Fskills\u002Fimplement-slice\u002FSKILL.md",[188],{"categoryNo":100,"categoryName":101,"taxonomyType":26,"taxonomyTypeDesc":27},[129,130,131,132,110,112,113,133,118,134,42,40,32,119,135,136,137]]