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 Reference patterns Best practices
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.Build to a verifiable check Build against a concrete, runnable check. Build Verify your work Best practices
Implement <function>. Example cases: <input → output>, <input → output>. After implementing, run the tests and show me they pass — show the output, don't just assert that it works.Component clone Spin up a new component that matches an existing one. Build Reference patterns Best practices
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 Give specific context Prompting
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.Go above and beyond Get an ambitious first version instead of a bare minimum. Build Go above & beyond Prompting
Build <thing>. Include as many relevant features and interactions as you can think of — go beyond the basics to create a fully-featured version, not a minimal one.Mockup to code Recreate a design and self-check it visually. Build Use images Common workflows
[paste screenshot] Build this component in <framework>. Then take a screenshot of your result, compare it against the mockup, and list the visual differences you still need to fix.Package a workflow as a Skill Turn a repeated workflow into a reusable Skill. Build Build Skills Agent Skills
We keep repeating <workflow>. Create a Claude Skill for it: a SKILL.md with YAML frontmatter (a name, and a description that says both what it does AND when to use it), plus any helper scripts. Keep the body concise.Plan-first scaffold Get an agreed plan before a single line is written. Build Plan first Best practices
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 Verify your work Best practices
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.Spec-first interview Turn a fuzzy feature idea into a written spec. Build Plan first Best practices
I want to build <feature>. Before writing any code, interview me one question at a time — cover the implementation approach, UX, edge cases, and tradeoffs. When we're done, write the agreed decisions to SPEC.md and stop.No prompts match your filters.