Commands

Overview

Custom slash commands are markdown files in .claude/commands/ that define reusable prompts triggered by /command-name. We use them for repetitive workflows — /dev starts the dev server, /build runs smart builds, /deploy ships to Vercel. Commands can accept arguments via $ARGUMENTS and compose multiple tools into a single action.

Current Progress

• 17+ slash commands configured and working
• Core workflow commands: /dev, /build, /deploy, /quick all tested
• Creation commands: /atom, /template, /block, /saas operational
• $ARGUMENTS placeholder used for parameterized commands

Areas of Improvement

• Some commands overlap with skills — need to clarify which is canonical
• No command for database seeding or migration rollback
• Missing /changelog and /release commands for version management

References

Setup

1. Create .claude/commands/ directory
2. Add markdown files — filename becomes the command name
3. Use $ARGUMENTS placeholder for command arguments
4. User commands go in ~/.claude/commands/ for cross-project access

Usage

• /dev — Kill port 3000, start pnpm dev, open Chrome
• /build — Run pnpm build with TypeScript check and auto-fix
• /deploy — Deploy to Vercel with environment selection
• /atom <name> — Create an atom component from 2+ primitives
• /test <file> — Generate and run tests for a file

Config Files