create-feature

Guide end-to-end CRUD feature creation across schema, repo, DTO, route, hook, component, and tests.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill create-feature-camilopiedra92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-feature
Source: https://github.com/camilopiedra92/YNAB-Clone/tree/main/.agent/skills/create-feature
Command: npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill create-feature-camilopiedra92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating the creation of a new domain feature across all architectural layers can be error-prone and time-consuming, leading to inconsistent implementations and broken pipelines.

Core Features & Use Cases

  • End-to-end scaffolding for DB schema, repository, DTO, API route, hook, component, and tests.
  • Consistency guarantees across stack boundaries, ensuring naming, validation, and data mapping align.
  • Use Case: When adding a new CRUD feature, follow this pipeline to ensure all layers are wired correctly from start to finish.

Quick Start

Follow the eight-step pipeline to add a new feature across all layers, from schema to tests.

Frequently Asked Questions about create-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new full-stack feature across all architectural layers?

To add a full-stack feature, follow an eight-step pipeline that scaffolds the schema, repository, DTO, API route, hook, component, and tests. This ensures consistent wiring, validation, and data mapping across the entire stack.

What is the best way to wire a CRUD feature from the database schema to the UI component?

Wiring a CRUD feature end-to-end requires systematically connecting the database schema through the repository and DTO to the API route, hook, and component. Applying an eight-layer pipeline pattern guarantees correct data mapping and validation boundaries.

Why does my end-to-end feature pipeline break between the API route and the frontend hook?

End-to-end feature pipelines break when stack boundaries like API routes and frontend hooks have mismatched naming, validation, or data mapping. Applying consistent scaffolding templates across architectural layers prevents these alignment errors.

Do I need to manually create tests when scaffolding a new domain feature end-to-end?

You do not need to manually create tests when scaffolding a domain feature end-to-end. The pipeline includes test generation as the final step, ensuring verification and consistency checks are applied across all newly created layers.

Can I use this pipeline for features that are not standard CRUD operations?

This scaffolding pipeline applies primarily to CRUD features, ensuring consistent wiring across architectural layers. While it focuses on standard create, read, update, and delete operations, the templates and validation patterns can guide broader domain feature development.