[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AEJ5BFV600PFDWWRHY4T8G":3,"skill-same:01M6AEJ5BFV600PFDWWRHY4T8G":98},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6AEJ5BFV600PFDWWRHY4T8G","feature-design-assistant",null,"Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ffeature-design-assistant\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],"design","assistant","feature design assistant","feature","feature design","architecture","planning","use","dialogue","ideas","designing architecture","changes","codebase","features","when","new","2026-11-10 10:12:30",false,"---\nname: feature-design-assistant\ndescription: \"Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.\"\n---\n\n# Feature Design Assistant\n\nHelp turn ideas into fully formed designs and specs through structured information gathering and collaborative validation.\n\n**Announce at start:** \"I'm using the feature-design-assistant skill to design this feature.\"\n\n## Phase 1: Context Discovery\n\nFirst, explore the codebase to understand:\n- Project structure and tech stack\n- Existing patterns and conventions\n- Related features or modules\n- Recent changes in relevant areas\n\n## Phase 2: Structured Information Gathering\n\nUse **AskUserQuestion** to batch collect information efficiently. Each call can ask up to 4 questions.\n\n### Round 1: Core Requirements (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What is the primary goal of this feature?\",\n      \"header\": \"Goal\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"New Functionality\", \"description\": \"Add entirely new capability to the system\" },\n        { \"label\": \"Enhancement\", \"description\": \"Improve or extend existing feature\" },\n        { \"label\": \"Bug Fix\", \"description\": \"Fix incorrect behavior or issue\" },\n        { \"label\": \"Refactoring\", \"description\": \"Improve code quality without changing behavior\" }\n      ]\n    },\n    {\n      \"question\": \"Who are the primary users of this feature?\",\n      \"header\": \"Users\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"End Users\", \"description\": \"External customers using the product\" },\n        { \"label\": \"Admins\", \"description\": \"Internal administrators or operators\" },\n        { \"label\": \"Developers\", \"description\": \"Other developers using APIs or SDKs\" },\n        { \"label\": \"System\", \"description\": \"Automated processes or background jobs\" }\n      ]\n    },\n    {\n      \"question\": \"What is the expected scope of this feature?\",\n      \"header\": \"Scope\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Small (1-2 days)\", \"description\": \"Single component, limited changes\" },\n        { \"label\": \"Medium (3-5 days)\", \"description\": \"Multiple components, moderate complexity\" },\n        { \"label\": \"Large (1-2 weeks)\", \"description\": \"Cross-cutting concerns, significant changes\" },\n        { \"label\": \"Unsure\", \"description\": \"Need to explore further to estimate\" }\n      ]\n    },\n    {\n      \"question\": \"Are there any hard deadlines or constraints?\",\n      \"header\": \"Timeline\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Urgent\", \"description\": \"Need this ASAP, within days\" },\n        { \"label\": \"This Sprint\", \"description\": \"Should be done within current sprint\" },\n        { \"label\": \"Flexible\", \"description\": \"No hard deadline, quality over speed\" },\n        { \"label\": \"Planning Only\", \"description\": \"Just designing now, implementing later\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 2: Technical Requirements (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Which layers of the system will this feature touch?\",\n      \"header\": \"Layers\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Data Model\", \"description\": \"Database schema, models, migrations\" },\n        { \"label\": \"Business Logic\", \"description\": \"Services, domain logic, rules\" },\n        { \"label\": \"API\", \"description\": \"REST\u002FGraphQL endpoints, contracts\" },\n        { \"label\": \"UI\", \"description\": \"Frontend components, user interface\" }\n      ]\n    },\n    {\n      \"question\": \"What are the key quality requirements?\",\n      \"header\": \"Quality\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"High Performance\", \"description\": \"Must handle high load or be very fast\" },\n        { \"label\": \"Strong Security\", \"description\": \"Sensitive data, auth, access control\" },\n        { \"label\": \"High Reliability\", \"description\": \"Cannot fail, needs redundancy\" },\n        { \"label\": \"Easy Maintenance\", \"description\": \"Needs to be easily understood and modified\" }\n      ]\n    },\n    {\n      \"question\": \"How should errors be handled?\",\n      \"header\": \"Errors\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Fail Fast\", \"description\": \"Stop immediately on any error\" },\n        { \"label\": \"Graceful Degrade\", \"description\": \"Continue with reduced functionality\" },\n        { \"label\": \"Retry & Recover\", \"description\": \"Automatic retry with recovery logic\" },\n        { \"label\": \"Context Dependent\", \"description\": \"Different strategies for different cases\" }\n      ]\n    },\n    {\n      \"question\": \"What testing approach is preferred?\",\n      \"header\": \"Testing\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"TDD (Recommended)\", \"description\": \"Write tests first, then implementation\" },\n        { \"label\": \"Test After\", \"description\": \"Implement first, add tests after\" },\n        { \"label\": \"Minimal Tests\", \"description\": \"Only critical path testing\" },\n        { \"label\": \"No Tests\", \"description\": \"Skip testing for this feature\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 3: Integration & Dependencies (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Does this feature need external integrations?\",\n      \"header\": \"Integrations\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Database\", \"description\": \"New tables, queries, or migrations\" },\n        { \"label\": \"External APIs\", \"description\": \"Third-party service calls\" },\n        { \"label\": \"Message Queue\", \"description\": \"Async processing, events\" },\n        { \"label\": \"None\", \"description\": \"No external integrations needed\" }\n      ]\n    },\n    {\n      \"question\": \"Are there dependencies on other features or teams?\",\n      \"header\": \"Dependencies\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Auth System\", \"description\": \"User authentication or authorization\" },\n        { \"label\": \"Other Features\", \"description\": \"Depends on features being developed\" },\n        { \"label\": \"External Team\", \"description\": \"Needs input from another team\" },\n        { \"label\": \"None\", \"description\": \"Fully independent feature\" }\n      ]\n    },\n    {\n      \"question\": \"How should we handle backwards compatibility?\",\n      \"header\": \"Compat\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Must Maintain\", \"description\": \"Cannot break existing clients\" },\n        { \"label\": \"Version API\", \"description\": \"Create new version, deprecate old\" },\n        { \"label\": \"Breaking OK\", \"description\": \"Can make breaking changes\" },\n        { \"label\": \"Not Applicable\", \"description\": \"New feature, no existing users\" }\n      ]\n    },\n    {\n      \"question\": \"What documentation is needed?\",\n      \"header\": \"Docs\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"API Docs\", \"description\": \"Endpoint documentation\" },\n        { \"label\": \"User Guide\", \"description\": \"How-to for end users\" },\n        { \"label\": \"Dev Guide\", \"description\": \"Technical implementation details\" },\n        { \"label\": \"None\", \"description\": \"No documentation needed\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 4: Clarifying Questions (Context-Dependent)\n\nBased on previous answers, ask follow-up questions. Examples:\n\n**If UI layer selected:**\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What UI framework\u002Fapproach should we use?\",\n      \"header\": \"UI Tech\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"React\", \"description\": \"React components with hooks\" },\n        { \"label\": \"Vue\", \"description\": \"Vue.js components\" },\n        { \"label\": \"Server-Side\", \"description\": \"Server-rendered HTML templates\" },\n        { \"label\": \"Existing Pattern\", \"description\": \"Follow current project conventions\" }\n      ]\n    }\n  ]\n}\n```\n\n**If High Security selected:**\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What security measures are required?\",\n      \"header\": \"Security\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Input Validation\", \"description\": \"Strict input sanitization\" },\n        { \"label\": \"Rate Limiting\", \"description\": \"Prevent abuse and DoS\" },\n        { \"label\": \"Audit Logging\", \"description\": \"Track all sensitive actions\" },\n        { \"label\": \"Encryption\", \"description\": \"Encrypt data at rest\u002Ftransit\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 3: Approach Exploration\n\nAfter gathering requirements, propose 2-3 approaches:\n\n```markdown\n## Approach Options\n\n### Option A: [Name] (Recommended)\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n\n### Option B: [Name]\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n\n### Option C: [Name]\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n```\n\nUse AskUserQuestion to confirm approach:\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Which approach would you like to proceed with?\",\n      \"header\": \"Approach\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Option A (Recommended)\", \"description\": \"Brief summary of approach A\" },\n        { \"label\": \"Option B\", \"description\": \"Brief summary of approach B\" },\n        { \"label\": \"Option C\", \"description\": \"Brief summary of approach C\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 4: Design Presentation\n\nPresent design in sections (300-500 words each), validate after each:\n\n1. **Architecture Overview** - High-level structure\n2. **Data Model** - Entities, relationships, schema\n3. **API Design** - Endpoints, request\u002Fresponse\n4. **Component Design** - Internal modules, interfaces\n5. **Error Handling** - Error cases, recovery strategies\n6. **Testing Strategy** - What and how to test\n\nAfter each section, use AskUserQuestion:\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Does this section look correct?\",\n      \"header\": \"Review\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Looks Good\", \"description\": \"Continue to next section\" },\n        { \"label\": \"Minor Changes\", \"description\": \"Small adjustments needed\" },\n        { \"label\": \"Major Revision\", \"description\": \"Significant changes required\" },\n        { \"label\": \"Questions\", \"description\": \"Need clarification before proceeding\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 5: Documentation & Tasks\n\n### Save Design Document\n\nWrite to `docs\u002Fdesigns\u002FYYYY-MM-DD-\u003Ctopic>-design.md`:\n\n```markdown\n# Feature: [Name]\n\n## Summary\n[Brief description]\n\n## Requirements\n[From Phase 2 answers]\n\n## Architecture\n[From Phase 4]\n\n## Implementation Tasks\n[Task checklist]\n```\n\n### Generate Implementation Tasks\n\n```markdown\n## Implementation Tasks\n\n- [ ] **Task Title** `priority:1` `phase:model` `time:15min`\n  - files: src\u002Ffile1.py, tests\u002Ftest_file1.py\n  - [ ] Write failing test for X\n  - [ ] Run test, verify it fails\n  - [ ] Implement minimal code\n  - [ ] Run test, verify it passes\n  - [ ] Commit\n\n- [ ] **Another Task** `priority:2` `phase:api` `deps:Task Title` `time:10min`\n  - files: src\u002Fapi.py\n  - [ ] Write failing test\n  - [ ] Implement and verify\n  - [ ] Commit\n```\n\n## Phase 6: Execution Handoff\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"How would you like to proceed with implementation?\",\n      \"header\": \"Next Step\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Execute Now\", \"description\": \"Run \u002Ffeature-pipeline in this session\" },\n        { \"label\": \"New Session\", \"description\": \"Start fresh session for implementation\" },\n        { \"label\": \"Later\", \"description\": \"Save design, implement manually later\" },\n        { \"label\": \"Revise Design\", \"description\": \"Go back and modify the design\" }\n      ]\n    }\n  ]\n}\n```\n\n## Key Principles\n\n- **Batch questions efficiently** - Use all 4 question slots when appropriate\n- **Use multiSelect for non-exclusive options** - Layers, features, requirements\n- **Use single-select for decisions** - Approach, timeline, strategy\n- **Mark recommendations** - Add \"(Recommended)\" to preferred options\n- **Progressive refinement** - General → Specific questions\n- **Validate incrementally** - Check understanding at each phase\n- **YAGNI ruthlessly** - Remove unnecessary features from designs\n","# Feature Design Assistant\n\nHelp turn ideas into fully formed designs and specs through structured information gathering and collaborative validation.\n\n**Announce at start:** \"I'm using the feature-design-assistant skill to design this feature.\"\n\n## Phase 1: Context Discovery\n\nFirst, explore the codebase to understand:\n- Project structure and tech stack\n- Existing patterns and conventions\n- Related features or modules\n- Recent changes in relevant areas\n\n## Phase 2: Structured Information Gathering\n\nUse **AskUserQuestion** to batch collect information efficiently. Each call can ask up to 4 questions.\n\n### Round 1: Core Requirements (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What is the primary goal of this feature?\",\n      \"header\": \"Goal\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"New Functionality\", \"description\": \"Add entirely new capability to the system\" },\n        { \"label\": \"Enhancement\", \"description\": \"Improve or extend existing feature\" },\n        { \"label\": \"Bug Fix\", \"description\": \"Fix incorrect behavior or issue\" },\n        { \"label\": \"Refactoring\", \"description\": \"Improve code quality without changing behavior\" }\n      ]\n    },\n    {\n      \"question\": \"Who are the primary users of this feature?\",\n      \"header\": \"Users\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"End Users\", \"description\": \"External customers using the product\" },\n        { \"label\": \"Admins\", \"description\": \"Internal administrators or operators\" },\n        { \"label\": \"Developers\", \"description\": \"Other developers using APIs or SDKs\" },\n        { \"label\": \"System\", \"description\": \"Automated processes or background jobs\" }\n      ]\n    },\n    {\n      \"question\": \"What is the expected scope of this feature?\",\n      \"header\": \"Scope\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Small (1-2 days)\", \"description\": \"Single component, limited changes\" },\n        { \"label\": \"Medium (3-5 days)\", \"description\": \"Multiple components, moderate complexity\" },\n        { \"label\": \"Large (1-2 weeks)\", \"description\": \"Cross-cutting concerns, significant changes\" },\n        { \"label\": \"Unsure\", \"description\": \"Need to explore further to estimate\" }\n      ]\n    },\n    {\n      \"question\": \"Are there any hard deadlines or constraints?\",\n      \"header\": \"Timeline\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Urgent\", \"description\": \"Need this ASAP, within days\" },\n        { \"label\": \"This Sprint\", \"description\": \"Should be done within current sprint\" },\n        { \"label\": \"Flexible\", \"description\": \"No hard deadline, quality over speed\" },\n        { \"label\": \"Planning Only\", \"description\": \"Just designing now, implementing later\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 2: Technical Requirements (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Which layers of the system will this feature touch?\",\n      \"header\": \"Layers\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Data Model\", \"description\": \"Database schema, models, migrations\" },\n        { \"label\": \"Business Logic\", \"description\": \"Services, domain logic, rules\" },\n        { \"label\": \"API\", \"description\": \"REST\u002FGraphQL endpoints, contracts\" },\n        { \"label\": \"UI\", \"description\": \"Frontend components, user interface\" }\n      ]\n    },\n    {\n      \"question\": \"What are the key quality requirements?\",\n      \"header\": \"Quality\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"High Performance\", \"description\": \"Must handle high load or be very fast\" },\n        { \"label\": \"Strong Security\", \"description\": \"Sensitive data, auth, access control\" },\n        { \"label\": \"High Reliability\", \"description\": \"Cannot fail, needs redundancy\" },\n        { \"label\": \"Easy Maintenance\", \"description\": \"Needs to be easily understood and modified\" }\n      ]\n    },\n    {\n      \"question\": \"How should errors be handled?\",\n      \"header\": \"Errors\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Fail Fast\", \"description\": \"Stop immediately on any error\" },\n        { \"label\": \"Graceful Degrade\", \"description\": \"Continue with reduced functionality\" },\n        { \"label\": \"Retry & Recover\", \"description\": \"Automatic retry with recovery logic\" },\n        { \"label\": \"Context Dependent\", \"description\": \"Different strategies for different cases\" }\n      ]\n    },\n    {\n      \"question\": \"What testing approach is preferred?\",\n      \"header\": \"Testing\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"TDD (Recommended)\", \"description\": \"Write tests first, then implementation\" },\n        { \"label\": \"Test After\", \"description\": \"Implement first, add tests after\" },\n        { \"label\": \"Minimal Tests\", \"description\": \"Only critical path testing\" },\n        { \"label\": \"No Tests\", \"description\": \"Skip testing for this feature\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 3: Integration & Dependencies (4 questions)\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Does this feature need external integrations?\",\n      \"header\": \"Integrations\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Database\", \"description\": \"New tables, queries, or migrations\" },\n        { \"label\": \"External APIs\", \"description\": \"Third-party service calls\" },\n        { \"label\": \"Message Queue\", \"description\": \"Async processing, events\" },\n        { \"label\": \"None\", \"description\": \"No external integrations needed\" }\n      ]\n    },\n    {\n      \"question\": \"Are there dependencies on other features or teams?\",\n      \"header\": \"Dependencies\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Auth System\", \"description\": \"User authentication or authorization\" },\n        { \"label\": \"Other Features\", \"description\": \"Depends on features being developed\" },\n        { \"label\": \"External Team\", \"description\": \"Needs input from another team\" },\n        { \"label\": \"None\", \"description\": \"Fully independent feature\" }\n      ]\n    },\n    {\n      \"question\": \"How should we handle backwards compatibility?\",\n      \"header\": \"Compat\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Must Maintain\", \"description\": \"Cannot break existing clients\" },\n        { \"label\": \"Version API\", \"description\": \"Create new version, deprecate old\" },\n        { \"label\": \"Breaking OK\", \"description\": \"Can make breaking changes\" },\n        { \"label\": \"Not Applicable\", \"description\": \"New feature, no existing users\" }\n      ]\n    },\n    {\n      \"question\": \"What documentation is needed?\",\n      \"header\": \"Docs\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"API Docs\", \"description\": \"Endpoint documentation\" },\n        { \"label\": \"User Guide\", \"description\": \"How-to for end users\" },\n        { \"label\": \"Dev Guide\", \"description\": \"Technical implementation details\" },\n        { \"label\": \"None\", \"description\": \"No documentation needed\" }\n      ]\n    }\n  ]\n}\n```\n\n### Round 4: Clarifying Questions (Context-Dependent)\n\nBased on previous answers, ask follow-up questions. Examples:\n\n**If UI layer selected:**\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What UI framework\u002Fapproach should we use?\",\n      \"header\": \"UI Tech\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"React\", \"description\": \"React components with hooks\" },\n        { \"label\": \"Vue\", \"description\": \"Vue.js components\" },\n        { \"label\": \"Server-Side\", \"description\": \"Server-rendered HTML templates\" },\n        { \"label\": \"Existing Pattern\", \"description\": \"Follow current project conventions\" }\n      ]\n    }\n  ]\n}\n```\n\n**If High Security selected:**\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"What security measures are required?\",\n      \"header\": \"Security\",\n      \"multiSelect\": true,\n      \"options\": [\n        { \"label\": \"Input Validation\", \"description\": \"Strict input sanitization\" },\n        { \"label\": \"Rate Limiting\", \"description\": \"Prevent abuse and DoS\" },\n        { \"label\": \"Audit Logging\", \"description\": \"Track all sensitive actions\" },\n        { \"label\": \"Encryption\", \"description\": \"Encrypt data at rest\u002Ftransit\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 3: Approach Exploration\n\nAfter gathering requirements, propose 2-3 approaches:\n\n```markdown\n## Approach Options\n\n### Option A: [Name] (Recommended)\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n\n### Option B: [Name]\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n\n### Option C: [Name]\n**Pros:** ...\n**Cons:** ...\n**Best for:** ...\n```\n\nUse AskUserQuestion to confirm approach:\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Which approach would you like to proceed with?\",\n      \"header\": \"Approach\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Option A (Recommended)\", \"description\": \"Brief summary of approach A\" },\n        { \"label\": \"Option B\", \"description\": \"Brief summary of approach B\" },\n        { \"label\": \"Option C\", \"description\": \"Brief summary of approach C\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 4: Design Presentation\n\nPresent design in sections (300-500 words each), validate after each:\n\n1. **Architecture Overview** - High-level structure\n2. **Data Model** - Entities, relationships, schema\n3. **API Design** - Endpoints, request\u002Fresponse\n4. **Component Design** - Internal modules, interfaces\n5. **Error Handling** - Error cases, recovery strategies\n6. **Testing Strategy** - What and how to test\n\nAfter each section, use AskUserQuestion:\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"Does this section look correct?\",\n      \"header\": \"Review\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Looks Good\", \"description\": \"Continue to next section\" },\n        { \"label\": \"Minor Changes\", \"description\": \"Small adjustments needed\" },\n        { \"label\": \"Major Revision\", \"description\": \"Significant changes required\" },\n        { \"label\": \"Questions\", \"description\": \"Need clarification before proceeding\" }\n      ]\n    }\n  ]\n}\n```\n\n## Phase 5: Documentation & Tasks\n\n### Save Design Document\n\nWrite to `docs\u002Fdesigns\u002FYYYY-MM-DD-\u003Ctopic>-design.md`:\n\n```markdown\n# Feature: [Name]\n\n## Summary\n[Brief description]\n\n## Requirements\n[From Phase 2 answers]\n\n## Architecture\n[From Phase 4]\n\n## Implementation Tasks\n[Task checklist]\n```\n\n### Generate Implementation Tasks\n\n```markdown\n## Implementation Tasks\n\n- [ ] **Task Title** `priority:1` `phase:model` `time:15min`\n  - files: src\u002Ffile1.py, tests\u002Ftest_file1.py\n  - [ ] Write failing test for X\n  - [ ] Run test, verify it fails\n  - [ ] Implement minimal code\n  - [ ] Run test, verify it passes\n  - [ ] Commit\n\n- [ ] **Another Task** `priority:2` `phase:api` `deps:Task Title` `time:10min`\n  - files: src\u002Fapi.py\n  - [ ] Write failing test\n  - [ ] Implement and verify\n  - [ ] Commit\n```\n\n## Phase 6: Execution Handoff\n\n```json\n{\n  \"questions\": [\n    {\n      \"question\": \"How would you like to proceed with implementation?\",\n      \"header\": \"Next Step\",\n      \"multiSelect\": false,\n      \"options\": [\n        { \"label\": \"Execute Now\", \"description\": \"Run \u002Ffeature-pipeline in this session\" },\n        { \"label\": \"New Session\", \"description\": \"Start fresh session for implementation\" },\n        { \"label\": \"Later\", \"description\": \"Save design, implement manually later\" },\n        { \"label\": \"Revise Design\", \"description\": \"Go back and modify the design\" }\n      ]\n    }\n  ]\n}\n```\n\n## Key Principles\n\n- **Batch questions efficiently** - Use all 4 question slots when appropriate\n- **Use multiSelect for non-exclusive options** - Layers, features, requirements\n- **Use single-select for decisions** - Approach, timeline, strategy\n- **Mark recommendations** - Add \"(Recommended)\" to preferred options\n- **Progressive refinement** - General → Specific questions\n- **Validate incrementally** - Check understanding at each phase\n- **YAGNI ruthlessly** - Remove unnecessary features from designs\n",{"name":5,"description":7},"main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ffeature-design-assistant",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill feature-design-assistant",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill feature-design-assistant",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill feature-design-assistant","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ffeature-design-assistant\u002FSKILL.md",true,[74,80,84,90,94],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fapi_reference.md","REFERENCE","参考文档",9121,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fgene-database\u002Freferences\u002Fapi_reference.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fcommon_workflows.md",10395,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fgene-database\u002Freferences\u002Fcommon_workflows.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fbatch_gene_lookup.py","SCRIPT","脚本",9109,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fgene-database\u002Fscripts\u002Fbatch_gene_lookup.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Ffetch_gene_data.py",8602,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fgene-database\u002Fscripts\u002Ffetch_gene_data.py",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fquery_gene.py",7409,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fgene-database\u002Fscripts\u002Fquery_gene.py",[99,127,154,185,220,244],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":45},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,110,111,112,113,114,115,116,36,43,117,118,119,120,121,122,123,124,125,126],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":45},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[133],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[135,136,137,138,139,140,141,142,143,144,145,43,146,147,148,149,150,151,152,153],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"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":167,"publishedAt":45},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[160,163,164],{"categoryNo":161,"categoryName":162,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":165,"categoryName":166,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[168,169,170,171,172,173,174,114,175,176,177,178,179,180,181,36,182,183,43,184],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":190,"sourceHtmlUrl":191,"categories":192,"keywords":196,"publishedAt":45},"01M6AFY6F7CC2BBZP1QD6VTNVC","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[193],{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,114,219],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":231,"publishedAt":45},"01M6AFWF33SFV9Z3SF4PEEE4BF","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.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[227,230],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":194,"categoryName":195,"taxonomyType":21,"taxonomyTypeDesc":22},[232,233,234,235,236,198,237,207,208,238,239,240,241,114,242,118,243],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":189,"licenseFileUrl":248,"sourceHtmlUrl":249,"categories":250,"keywords":258,"publishedAt":45},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[251,254,255],{"categoryNo":252,"categoryName":253,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":256,"categoryName":257,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[259,260,261,262,263,264,265,266,200,267,210,146,268,269,270,271,272,180,273,43,274,275,276,277,278,124,279],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]