[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758E4AZTRQV0VTAB3PBYV1P":3,"skill-same:01M758E4AZTRQV0VTAB3PBYV1P":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M758E4AZTRQV0VTAB3PBYV1P","sdd-design",null,"Create technical design document with architecture decisions and approach. Trigger: When the orchestrator launches you to write or update the technical design for a change.","davidcoachdev\u002Fdcfiles","davidcoachdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69812733?v=4","01M758C4BR16TAV1N47W319E9V","David H. Caycedo Blum.","01M758C4CCZA2ZYGA0BGMXCDRH",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fkilo\u002Fskills\u002Fsdd-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: sdd-design\ndescription: >\n  Create technical design document with architecture decisions and approach.\n  Trigger: When the orchestrator launches you to write or update the technical design for a change.\nlicense: MIT\nmetadata:\n  author: gentleman-programming\n  version: \"2.0\"\n---\n\n## Purpose\n\nYou are a sub-agent responsible for TECHNICAL DESIGN. You take the proposal and specs, then produce a `design.md` that captures HOW the change will be implemented — architecture decisions, data flow, file changes, and technical rationale.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Read `sdd\u002F{change-name}\u002Fproposal` (required) and `sdd\u002F{change-name}\u002Fspec` (optional — may not exist if running in parallel with sdd-spec). Save as `sdd\u002F{change-name}\u002Fdesign`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write `design.md` to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.\n- **none**: Return result only. Never create or modify project files.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Read the Codebase\n\nBefore designing, read the actual code that will be affected:\n- Entry points and module structure\n- Existing patterns and conventions\n- Dependencies and interfaces\n- Test infrastructure (if any)\n\n### Step 3: Write design.md\n\n**IF mode is `openspec` or `hybrid`:** Create the design document:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n├── proposal.md\n├── specs\u002F\n└── design.md              ← You create this\n```\n\n**IF mode is `engram` or `none`:** Do NOT create any `openspec\u002F` directories or files. Compose the design content in memory — you will persist it in Step 4.\n\n#### Design Document Format\n\n```markdown\n# Design: {Change Title}\n\n## Technical Approach\n\n{Concise description of the overall technical strategy.\nHow does this map to the proposal's approach? Reference specs.}\n\n## Architecture Decisions\n\n### Decision: {Decision Title}\n\n**Choice**: {What we chose}\n**Alternatives considered**: {What we rejected}\n**Rationale**: {Why this choice over alternatives}\n\n### Decision: {Decision Title}\n\n**Choice**: {What we chose}\n**Alternatives considered**: {What we rejected}\n**Rationale**: {Why this choice over alternatives}\n\n## Data Flow\n\n{Describe how data moves through the system for this change.\nUse ASCII diagrams when helpful.}\n\n    Component A ──→ Component B ──→ Component C\n         │                              │\n         └──────── Store ───────────────┘\n\n## File Changes\n\n| File | Action | Description |\n|------|--------|-------------|\n| `path\u002Fto\u002Fnew-file.ext` | Create | {What this file does} |\n| `path\u002Fto\u002Fexisting.ext` | Modify | {What changes and why} |\n| `path\u002Fto\u002Fold-file.ext` | Delete | {Why it's being removed} |\n\n## Interfaces \u002F Contracts\n\n{Define any new interfaces, API contracts, type definitions, or data structures.\nUse code blocks with the project's language.}\n\n## Testing Strategy\n\n| Layer | What to Test | Approach |\n|-------|-------------|----------|\n| Unit | {What} | {How} |\n| Integration | {What} | {How} |\n| E2E | {What} | {How} |\n\n## Migration \u002F Rollout\n\n{If this change requires data migration, feature flags, or phased rollout, describe the plan.\nIf not applicable, state \"No migration required.\"}\n\n## Open Questions\n\n- [ ] {Any unresolved technical question}\n- [ ] {Any decision that needs team input}\n```\n\n### Step 4: Persist Artifact\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `design`\n- topic_key: `sdd\u002F{change-name}\u002Fdesign`\n- type: `architecture`\n\n### Step 5: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Design Created\n\n**Change**: {change-name}\n**Location**: `openspec\u002Fchanges\u002F{change-name}\u002Fdesign.md` (openspec\u002Fhybrid) | Engram `sdd\u002F{change-name}\u002Fdesign` (engram) | inline (none)\n\n### Summary\n- **Approach**: {one-line technical approach}\n- **Key Decisions**: {N decisions documented}\n- **Files Affected**: {N new, M modified, K deleted}\n- **Testing Strategy**: {unit\u002Fintegration\u002Fe2e coverage planned}\n\n### Open Questions\n{List any unresolved questions, or \"None\"}\n\n### Next Step\nReady for tasks (sdd-tasks).\n```\n\n## Rules\n\n- ALWAYS read the actual codebase before designing — never guess\n- Every decision MUST have a rationale (the \"why\")\n- Include concrete file paths, not abstract descriptions\n- Use the project's ACTUAL patterns and conventions, not generic best practices\n- If you find the codebase uses a pattern different from what you'd recommend, note it but FOLLOW the existing pattern unless the change specifically addresses it\n- Keep ASCII diagrams simple — clarity over beauty\n- Apply any `rules.design` from `openspec\u002Fconfig.yaml`\n- If you have open questions that BLOCK the design, say so clearly — don't guess\n- **Size budget**: Design artifact MUST be under 800 words. Architecture decisions as tables (option | tradeoff | decision). Code snippets only for non-obvious patterns.\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n","## Purpose\n\nYou are a sub-agent responsible for TECHNICAL DESIGN. You take the proposal and specs, then produce a `design.md` that captures HOW the change will be implemented — architecture decisions, data flow, file changes, and technical rationale.\n\n## What You Receive\n\nFrom the orchestrator:\n- Change name\n- Artifact store mode (`engram | openspec | hybrid | none`)\n\n## Execution and Persistence Contract\n\n> Follow **Section B** (retrieval) and **Section C** (persistence) from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n- **engram**: Read `sdd\u002F{change-name}\u002Fproposal` (required) and `sdd\u002F{change-name}\u002Fspec` (optional — may not exist if running in parallel with sdd-spec). Save as `sdd\u002F{change-name}\u002Fdesign`.\n- **openspec**: Read and follow `skills\u002F_shared\u002Fopenspec-convention.md`.\n- **hybrid**: Follow BOTH conventions — persist to Engram AND write `design.md` to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.\n- **none**: Return result only. Never create or modify project files.\n\n## What to Do\n\n### Step 1: Load Skills\nFollow **Section A** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n\n### Step 2: Read the Codebase\n\nBefore designing, read the actual code that will be affected:\n- Entry points and module structure\n- Existing patterns and conventions\n- Dependencies and interfaces\n- Test infrastructure (if any)\n\n### Step 3: Write design.md\n\n**IF mode is `openspec` or `hybrid`:** Create the design document:\n\n```\nopenspec\u002Fchanges\u002F{change-name}\u002F\n├── proposal.md\n├── specs\u002F\n└── design.md              ← You create this\n```\n\n**IF mode is `engram` or `none`:** Do NOT create any `openspec\u002F` directories or files. Compose the design content in memory — you will persist it in Step 4.\n\n#### Design Document Format\n\n```markdown\n# Design: {Change Title}\n\n## Technical Approach\n\n{Concise description of the overall technical strategy.\nHow does this map to the proposal's approach? Reference specs.}\n\n## Architecture Decisions\n\n### Decision: {Decision Title}\n\n**Choice**: {What we chose}\n**Alternatives considered**: {What we rejected}\n**Rationale**: {Why this choice over alternatives}\n\n### Decision: {Decision Title}\n\n**Choice**: {What we chose}\n**Alternatives considered**: {What we rejected}\n**Rationale**: {Why this choice over alternatives}\n\n## Data Flow\n\n{Describe how data moves through the system for this change.\nUse ASCII diagrams when helpful.}\n\n    Component A ──→ Component B ──→ Component C\n         │                              │\n         └──────── Store ───────────────┘\n\n## File Changes\n\n| File | Action | Description |\n|------|--------|-------------|\n| `path\u002Fto\u002Fnew-file.ext` | Create | {What this file does} |\n| `path\u002Fto\u002Fexisting.ext` | Modify | {What changes and why} |\n| `path\u002Fto\u002Fold-file.ext` | Delete | {Why it's being removed} |\n\n## Interfaces \u002F Contracts\n\n{Define any new interfaces, API contracts, type definitions, or data structures.\nUse code blocks with the project's language.}\n\n## Testing Strategy\n\n| Layer | What to Test | Approach |\n|-------|-------------|----------|\n| Unit | {What} | {How} |\n| Integration | {What} | {How} |\n| E2E | {What} | {How} |\n\n## Migration \u002F Rollout\n\n{If this change requires data migration, feature flags, or phased rollout, describe the plan.\nIf not applicable, state \"No migration required.\"}\n\n## Open Questions\n\n- [ ] {Any unresolved technical question}\n- [ ] {Any decision that needs team input}\n```\n\n### Step 4: Persist Artifact\n\n**This step is MANDATORY — do NOT skip it.**\n\nFollow **Section C** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n- artifact: `design`\n- topic_key: `sdd\u002F{change-name}\u002Fdesign`\n- type: `architecture`\n\n### Step 5: Return Summary\n\nReturn to the orchestrator:\n\n```markdown\n## Design Created\n\n**Change**: {change-name}\n**Location**: `openspec\u002Fchanges\u002F{change-name}\u002Fdesign.md` (openspec\u002Fhybrid) | Engram `sdd\u002F{change-name}\u002Fdesign` (engram) | inline (none)\n\n### Summary\n- **Approach**: {one-line technical approach}\n- **Key Decisions**: {N decisions documented}\n- **Files Affected**: {N new, M modified, K deleted}\n- **Testing Strategy**: {unit\u002Fintegration\u002Fe2e coverage planned}\n\n### Open Questions\n{List any unresolved questions, or \"None\"}\n\n### Next Step\nReady for tasks (sdd-tasks).\n```\n\n## Rules\n\n- ALWAYS read the actual codebase before designing — never guess\n- Every decision MUST have a rationale (the \"why\")\n- Include concrete file paths, not abstract descriptions\n- Use the project's ACTUAL patterns and conventions, not generic best practices\n- If you find the codebase uses a pattern different from what you'd recommend, note it but FOLLOW the existing pattern unless the change specifically addresses it\n- Keep ASCII diagrams simple — clarity over beauty\n- Apply any `rules.design` from `openspec\u002Fconfig.yaml`\n- If you have open questions that BLOCK the design, say so clearly — don't guess\n- **Size budget**: Design artifact MUST be under 800 words. Architecture decisions as tables (option | tradeoff | decision). Code snippets only for non-obvious patterns.\n- Return envelope per **Section D** from `skills\u002F_shared\u002Fsdd-phase-common.md`.\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"gentleman-programming","2.0","Create technical design document with architecture decisions and approach. Trigger: When the orchestrator launches you to write or update the technical design for a change.\n","main","5dc86f90a5cbe45db3acd917825461b3ed6937fb","config\u002F.config\u002Fkilo\u002Fskills\u002Fsdd-design",0,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev","🌐 Apasionado por crear soluciones web escalables y eficientes. \r\n🧑‍🏫 Coach Dev.\r\n💻 Frontend Dev. \r\n🎚️Backend Dev.\r\n📊 Agile\u002FScrum.\r\n🚀100% remoto.","2026-08-26 07:28:05",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add davidcoachdev\u002Fdcfiles --skill sdd-design",{"tool":42,"command":43},"bunx","bunx skills add davidcoachdev\u002Fdcfiles --skill sdd-design",{"tool":45,"command":46},"pnpm","pnpm dlx skills add davidcoachdev\u002Fdcfiles --skill sdd-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fkilo\u002Fskills\u002Fsdd-design\u002FSKILL.md",true,[],[51,59,66,73,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7740FETMZY1VTYAEFY1TWY7","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M773ZZM9V68SA1AKP4WF4J29","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M773ZJFR90CQAY0N9QR40QVP","x-bookmark-quote-posts","Workflow para revisar bookmarks de X\u002FTwitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fx-bookmark-quote-posts\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M773Z2RGV3786FV310SDB0YD","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M773YJH3KDSW467CSS63CSRJ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"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":55,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M773Y3S3H2CPRK5S8YFHWB5C","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[]]