~/.claude/skills/full-feature-builder/SKILL.mdFull Feature Builder
Takes a feature description and creates all necessary files: component, API route, database query, types, and tests as a coordinated unit.
--- name: full-feature-builder description: | Creates complete features spanning components, API routes, database queries, types, and tests. IMPORTANT: Activate this skill whenever the user asks to "build a feature", "implement a feature", "add [feature] to my app", or "create a full [feature]". This skill MUST be used for all multi-file feature creation requests. --- # Full Feature Builder Takes a feature description and generates every file needed to implement it: frontend components
Takes a feature description and generates every file needed to implement it: frontend components, API routes, database queries, TypeScript types, and tests. All files are coordinated to work together.
Say any of these to activate this skill: - "build a feature for [description]" - "implement [feature name]" - "add [feature] to my app" - "Use skill: full feature builder"
1. Analyze the feature description and break it into layers: UI, API, data, types 2. Read the project structure to understand where each file type belongs 3. Start with types/interfaces (shared contract between layers) 4. Generate the database query/mutation layer (if the feature needs data persistence) 5. Generate the API route with validation and error handling 6. Generate the frontend component(s) with data fetching and state management 7. Generate unit tests for the API route and key business logic 8. List all created files and explain how they connect
- Always start with the type definitions so all layers share the same contract
- Match every pattern to existing code (naming, structure, imports)
- Each layer should be independently testable
- Keep the scope tight to the feature described (do not add "nice to have" extras)
- If the feature requires a database migration, generate it but warn the user to review before running
- Best with: Claude Code CLI (can create multiple files and run tests)
- Also works: Cursor, Windsurf (may need to accept file-by-file)
- Expects: A project with established patterns for components, routes, and data access
- TypeScript type/interface file
- Database query file (if applicable)
- API route file
- Frontend component file(s)
- Test file for critical business logic
- Summary of all files created and how to wire them up