Build
Scaffold features, endpoints, and components with a plan-first approach.
API endpoint from pattern Add a route that matches your backend conventions, with tests. Build api backend
Add a <METHOD> <route> endpoint following the pattern in @<router-file>. Validate the input, return typed responses, and add one happy-path test plus one error-case test.Component clone Spin up a new component that matches an existing one. Build components ui
Create a new component like @<existing> but for <use case>. Reuse its props style, file structure, and styling approach — don't invent new conventions.Feature from spec Implement one feature that fits the file's existing conventions. Build implementation patterns
Implement <feature> in @<file>. Match the existing patterns in this file. Add types, handle the error cases, and stop after the minimal working version — no extra abstractions.Plan-first scaffold Get an agreed plan before a single line is written. Build planning scaffolding
Before writing any code, outline a short plan for <feature>: the files you'll create or touch, the key functions, and the data flow between them. Wait for my OK, then implement.Scaffold with TDD Lock behavior with tests before writing the implementation. Build testing tdd
Write failing tests for <behavior> first and show them to me. Once I confirm, implement until they pass. Don't modify the tests without asking.No prompts match your filters.