Your Custom Slash Commands π
These are your personal shortcuts for common product management tasks. Just type /command and Claude handles the complexity.
π¬ Getting Started Commands
/start [feature-name]
Begin a new feature with proper setup
You: /start user-profiles
Claude:
πΏ Creating feature/user-profiles branch
π Breaking down the feature
β
Ready to code!
When to use: Starting any new feature or significant change
/idea
Brainstorm and plan before building
You: /idea
I want users to customize their dashboard
Claude:
π‘ Here are 3 approaches:
1. Drag-and-drop widgets (Complex, 3-5 days)
2. Template selection (Simple, 1 day)
3. Toggle panels (Medium, 2 days)
Which direction interests you?
When to use: Exploring possibilities before committing to a solution
π¨ Building Commands
/test
Test features with visual browser verification
You: /test
Check if login form works on mobile
Claude:
π± Opening browser in mobile view...
β
Form displays correctly
β
Touch interactions work
β Password toggle too small
π§ Fixing issue now...
When to use: Verify anything works (no need to test manually!)
/fix
Debug and fix issues systematically
You: /fix
Button doesn't work on iPhone
Claude:
π Investigating...
π― Found it: Touch event not registered
π§ Fixing...
β
Tested on mobile - works now!
When to use: Something's broken and you need it fixed
/preview
Review changes before committing
You: /preview
Claude:
π 3 files changed:
π¨ LoginForm.tsx - Added validation
βοΈ auth.ts - New API call
β
tests/ - Added 5 tests
Quality Checks: β
All passing
Ready to commit? Yes!
When to use: Before committing to see exactly what changed
π Information Commands
/status
Get current project state
You: /status
Claude:
πΏ Branch: feature/dark-mode
π¦ Changes: 12 files
β
Tests: All passing
π Deploy ready: Yes
π‘ Dark mode complete. Ready for PR.
When to use: Check where you are in a feature
/explain [file-or-concept]
Understand code in plain English
You: /explain useAuth
Claude:
π― What it does:
Checks if a user is logged in
π‘ Think of it like:
A bouncer at a club checking IDs.
No valid ID? Can't get in.
π Why it matters:
Protects user data and keeps features secure
When to use: Need to understand what something does
/compare
See what changed between versions
You: /compare
Current branch vs main
Claude:
π 10 files changed:
π¨ UI: 6 files (login flow redesign)
βοΈ Logic: 3 files (auth improvements)
β
Tests: 1 file (new test coverage)
π‘ This adds social login while
keeping email login working
When to use: Understand scope of changes
π Shipping Commands
/ship
Complete feature and create PR
You: /ship
Claude:
β
All tests passing
β
Build succeeds
π¦ Committing changes
π Creating PR
π PR #42 ready for review!
π https://github.com/...
When to use: Feature is done, ready to ship
/docs
Generate plain-English documentation
You: /docs
Document the new comment system
Claude:
π Creating documentation...
# Comment System
π― Lets users discuss posts
π‘ Encourages community engagement
π How to use: Click comment icon...
When to use: Need docs for what was built
π οΈ Maintenance Commands
/cleanup
Tidy up the project
You: /cleanup
Claude:
ποΈ Found cleanup opportunities:
π΄ Critical: 2 security issues
π‘ Recommended: 12 unused files
π’ Nice-to-have: 8 style fixes
Proceed with cleanup? [Yes/No]
When to use: Project feels messy or before major releases
/rollback
Undo recent changes safely
You: /rollback
Claude:
π Recent commits:
1. "Add payment integration" (5 min ago)
2. "Fix login bug" (1 hour ago)
3. "Update dashboard" (2 hours ago)
Which to undo?
When to use: Need to undo a change that broke something
π― How to Use These
Basic Usage
/command
With Arguments
/start user-authentication
/explain LoginForm.tsx
Chaining (do multiple tasks)
/test
/fix (if issues found)
/preview
/ship
π‘ Pro Tips
1. Combine Commands
Build flow:
/start feature-name
[build features]
/test
/preview
/ship
2. Use /test Often
Don't manually check browsers. Just /test and Claude uses Playwright to verify everything.
3. Stuck? Use /status
Forgot where you are? /status gives the full picture.
4. Before Shipping
Always run /preview to catch any issues before creating the PR.
5. Brainstorming
Use /idea before jumping into code. Save time by planning first.
π¨ Customization
Add Your Own Commands
- Create a new
.mdfile in~/.claude/commands/ - Name it:
yourcommand.md - Write the prompt inside
- Use it:
/yourcommand
Example Custom Command
File: ~/.claude/commands/review.md
# /review - Code Review
You are reviewing code for:
- Best practices
- Performance issues
- Security concerns
- Accessibility
Provide actionable feedback in simple terms.
Now use: /review
π§ Troubleshooting
Command not found?
# Check if command file exists
ls ~/.claude/commands/
# Make sure it ends with .md
Command not working right?
# Read the command file to see what it does
cat ~/.claude/commands/commandname.md
# Edit it to adjust behavior
Want to disable a command?
# Rename to .disabled
mv ~/.claude/commands/ship.md ~/.claude/commands/ship.md.disabled
π Command Categories Quick Reference
π¬ Starting: /start, /idea
π¨ Building: /test, /fix, /preview
π Information: /status, /explain, /compare
π Shipping: /ship, /docs
π οΈ Maintenance: /cleanup, /rollback
π Real Workflow Example
Day 1: Feature Start
You: /start social-sharing
You: Build share buttons for posts
You: /test
Day 2: Refinement
You: /status
You: Add Twitter and LinkedIn
You: /test
You: /preview
Day 3: Ship It
You: /docs
You: /ship
β
Feature shipped!
π Learning More
Each command is just a markdown file. Open them to see exactly what they do:
# Read any command
cat ~/.claude/commands/ship.md
# Edit to customize
nano ~/.claude/commands/ship.md
The commands are prompts that tell Claude how to help you. Adjust them to match your workflow!
π Next Level
Want more commands? Here are ideas:
/demo- Create demo data/performance- Check app speed/security- Run security audit/mobile- Test mobile experience/analytics- Check metrics
Just ask: "Can you create a /demo command?"
Pro Tip: These commands work WITH your hooks. Hooks run automatically, commands you trigger manually. Together they're a powerful workflow automation system! π―