Skip to Content
UseUsing Commands

Using Commands

Dotpack commands are workflows, not prompts. Treat them like small specs: give constraints, references, and what “done” means.

Syntax by tool

ToolSyntax
Gemini CLI/command
Cursor@command
Claude Code/command

High-leverage request template

Copy/paste this and fill it in:

/<command> <goal>

Context:
- relevant files/paths:
- constraints (stack, libraries, patterns):
- references (existing code to follow):

Acceptance criteria:
- must:
- must not:

Testing:
- add/update tests:
- edge cases:

Core workflows

/build — feature workflow

Use when you want a working feature across files.

/build add a settings page with validation and loading/error states

/fix — root-cause workflow

Use when something is broken and you want the root cause + a verified fix.

/fix the checkout button is disabled on mobile

/plan — strategy workflow

Use when you want a step-by-step plan before writing code.

/plan migrate from Pages Router to App Router

What “battle-tested” means in practice

These workflows should push toward:

  • a clear plan before large changes
  • validation and error handling (where relevant)
  • tests added/updated when applicable
  • a quick review/verification step

Next

Last updated on
LearnAdapters