Command Finder
A comprehensive decision tree for ClaudeKit newcomers. If you're
ever unsure, just type
/ck-help
for interactive assistance!
Select Kit
Interactive Decision Tree
Click on any node or path to highlight the route to that command. Or click the command buttons above to see their corresponding paths.
Command Reference
Select to trace path
Click on any node or edge to highlight a path. Click commands above to see their paths.
New Project Setup
| Command | Description | When to Use |
|---|---|---|
/ck:bootstrap | Full project initialization with research, tech stack, planning, design, implementation | Starting a brand new project from scratch |
/ck:docs init | Analyze existing codebase and create documentation | Joining an existing project or setting up docs |
Tip: New Project Flow: /bootstrap → automatically handles everything including Git initialization, tech stack research, wireframes, and initial implementation.
Feature Building
Don't Know What You Want Yet
| Command | Description | When to Use |
|---|---|---|
/ck:brainstorm | Collaborative ideation with expert advice | Exploring ideas, validating approaches, getting pros/cons |
Important: /brainstorm DOES NOT implement - it only advises. After brainstorming, use /ck:plan or /ck:cook to implement.
Know What You Want
| Command | Description | When to Use |
|---|---|---|
/ck:cook | ⚡⚡⚡ All-in-one: research → plan → implement → test → review | FAST mode - Quick iterations, simpler features |
/ck:plan | Create detailed implementation plan without coding | SAFE mode - Complex features, need approval first |
/ck:cook @plan.md | Implement an existing plan step by step | After /ck:plan is approved |
Key Difference:
• /ck:cook =
Speed-focused, plans internally, goes straight to implementation
• /ck:plan →
/ck:cook = Safety-focused, creates reviewable plan first
Fixing Issues
Diagnostic First
| Command | Description | When to Use |
|---|---|---|
/ck:debug | Analyze and find root cause | Don't know what's wrong |
/ck:fix | Smart fix routing - auto routes by issue type | Know the issue, want quick fix |
Smart Routing: Just use /fix <describe issue> and it will automatically route to the right specialized command!
Git Operations
| Command | Description | Options |
|---|---|---|
/ck:git | Git operations with natural language | cm cp pr merge |
/ck:worktree | Create isolated worktree | Work on multiple features in parallel |
Tip: Use natural language instead of fixed commands. Just say "commit my changes" or "create a PR for this feature"!
Documentation
| Command | Description | When to Use |
|---|---|---|
/ck:docs init | Create initial project documentation | New/undocumented project |
/ck:docs summarize | Summarize codebase changes | After major changes |
/ck:docs update | Update existing documentation | Keep docs in sync |
Exploration & Research
| Command | Description | When to Use |
|---|---|---|
/ck:scout | Fast parallel codebase search | Find relevant files for a task |
/ck:scout ext | Extended search with Gemini 2M context | Deep codebase exploration |
/ck:watzup | Review recent changes in current branch | Wrap up work, understand recent commits |
Questions & Learning
| Command | Description | When to Use |
|---|---|---|
/ck:ask | Technical & architectural consultation | Need expert advice on architecture, trade-offs |
/coding-level [0-5] | Set explanation depth | Tailor Claude's responses to your experience |
Coding Levels:
• 0 = ELI5 (zero coding experience)
• 1 = Junior (0-2 years)
• 2 = Mid-Level (3-5 years)
• 3 = Senior (5-8 years)
• 4 = Tech Lead (8-10 years)
• 5 = God Mode (default, maximum efficiency)
Project Management
| Command | Description | When to Use |
|---|---|---|
/ck:kanban | Visual dashboard for plans | View plan progress, timeline visualization |
/ck:preview | Universal markdown/directory viewer | View plans, docs in readable format |
/ck:test | Run tests and analyze results | Verify code changes work |
Design Commands
| Command | Description | When to Use |
|---|---|---|
/ck:frontend-design | UI/UX design with screenshot analysis | Create/improve UI components |
/ck:remotion | Video design with React | Create video animations |
/ck:threejs | 3D graphics with Three.js | Create 3D visualizations |
/ck:ai-artist | AI image generation | Create artwork, assets |
Code Review
| Command | Description | When to Use |
|---|---|---|
/ck:review codebase | Comprehensive codebase review | Quality assessment, find issues |
/ck:review codebase parallel | Parallel review with multiple agents | Large codebase, need speed |
Planning Variations
| Command | Description | When to Use |
|---|---|---|
/ck:plan | Auto-detect complexity | General planning |
/ck:plan --fast | Quick planning for simple tasks | Small features, quick fixes |
/ck:plan --hard | Deep planning with extensive research | Complex, multi-phase features |
/ck:plan --parallel | Plan multiple independent tasks | Several unrelated features |
/ck:plan validate | Validate and review existing plan | Before execution |
/ck:plan archive | Archive completed plan | Clean up finished work |
Common Workflows
Workflow 1: Building a New Feature (Safe)
1. /ck:brainstorm → Explore options
2. /ck:plan → Review plan
3. /clear or /compact
4. /ck:cook @plan.md → Implementation
5. /ck:git cp →
Push
6. /ck:git pr →
PR
Workflow 2: Building a Feature (Fast)
1. /ck:cook →
Research → Plan → Implement → Test → Review
2. /ck:git cp →
Commit and push when approved
Workflow 3: Debugging & Fixing
1. /ck:debug →
Find root cause
2. /ck:fix → Smart routing
3. /ck:git cm →
Commit fix locally
Workflow 4: New Project Setup
1. /ck:bootstrap → Full setup
2. Follow onboarding instructions
Workflow 5: Joining Existing Project
1. /ck:docs init →
Analyze codebase, create docs
2. /ck:scout → Explore codebase structure
Workflow 6: Code Review
1. /ck:test →
Run tests
2. /ck:review codebase →
Comprehensive review
3. /ck:simplify →
Refine code
4. /ck:git pr →
Create PR
Workflow 7: Design Implementation
1. /ck:frontend-design →
Create design
2. /ck:cook →
Implement design
3. /ck:test →
Verify implementation
Workflow 8: Research
1. /ck:scout →
Find relevant files
2. /ck:research →
Deep dive into topic
3. /ck:ask →
Get expert advice
Pro Tips
Speed vs Safety Trade-off:
• Use /ck:cook when you're confident and want speed
• Use /ck:plan → /ck:cook @plan.md when precision and review matter
Best Practice:
• Use /ck:cook for most tasks - has internal planning
• Use /ck:plan before /ck:cook @plan.md for complex tasks needing review
Git safety:
• /ck:git cm = commit only (safe for experimentation)
• /ck:git cp = commits AND pushes (can't undo easily)
Summary Cheat Sheet
| Scenario | Command |
|---|---|
| "I need to build something new from scratch" | /ck:bootstrap |
| "I have an idea but not sure how to approach it" | /ck:brainstorm |
| "I know exactly what I want, do it fast" | /ck:cook |
| "I want to plan carefully before coding" | /ck:plan → /ck:cook |
| "Something's broken, I don't know why" | /ck:debug → /ck:fix |
| "Something's broken, I know what it is" | /ck:fix |
| "I need to save my work" | /ck:git cm or /ck:git cp |
| "I need to understand this codebase" | /ck:docs init |
| "I need architectural advice" | /ck:ask |
| "What changed recently?" | /ck:watzup |
| "View my plans visually" | /ck:kanban or /ck:preview |
| "I'm new, slow down explanations" | /coding-level 1 |
| "I need help with ClaudeKit" | /ck:ck-help |
/ck:ck-help → Full documentation/ck:ck-help fix → Category guide for fix commands/ck:ck-help plan --hard → Details on specific command/ck:ck-help how to debug → Task-based recommendations Marketing Kit - Coming Soon
The decision tree for Marketing Kit is under construction. In the meantime, check out the Commands Guide to explore all marketing commands.
View Commands Guide