Command Finder
A comprehensive decision tree for ClaudeKit newcomers. If you're ever unsure, just type /ck-help for interactive assistance!
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 |
|---|---|---|
/bootstrap | Full project initialization with research, tech stack, planning, design, implementation | Starting a brand new project from scratch |
/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 |
|---|---|---|
/brainstorm | Collaborative ideation with expert advice | Exploring ideas, validating approaches, getting pros/cons |
Important: /brainstorm DOES NOT implement - it only advises. After brainstorming, use /plan or /cook to implement.
Know What You Want
| Command | Description | When to Use |
|---|---|---|
/cook | β‘β‘β‘ All-in-one: research β plan β implement β test β review | FAST mode - Quick iterations, simpler features |
/plan | Create detailed implementation plan without coding | SAFE mode - Complex features, need approval first |
/code @plan.md | Execute an existing plan step by step | After /plan is approved |
Key Difference:
β’ /cook = Speed-focused, plans internally, goes straight to implementation
β’ /plan β /code = Safety-focused, creates reviewable plan first
Fixing Issues
Diagnostic First
| Command | Description | When to Use |
|---|---|---|
/debug | Analyze and find root cause | Don't know what's wrong |
/fix | Intelligent router to specialized fix commands | Know the issue, want quick fix |
Specialized Fix Commands
| Command | Description | When to Use |
|---|---|---|
/fix:types | Fix TypeScript/type errors | tsc errors, type mismatches |
/fix:ui | Fix UI/UX issues | Layout, styling, component bugs |
/fix:ci | Fix CI/CD pipeline issues | GitHub Actions, deployment failures |
/fix:test | Fix failing tests | Jest, Vitest test failures |
/fix:logs | Analyze error logs | Stack traces, runtime errors |
/fix:fast | Quick fix for simple issues | Single file, straightforward bugs |
/fix:hard | Complex multi-component fixes | Architecture, refactoring issues |
/fix:parallel | Fix multiple independent issues | 2+ unrelated bugs at once |
Smart Routing: Just use /fix <describe issue> and it will automatically route to the right specialized command!
Git Operations
| Command | Description | When to Use |
|---|---|---|
/git:cm | Stage all + commit (no push) | Save work locally |
/git:cp | Stage + commit + push | Ready to share changes |
/git:merge | Merge branches | Combine feature branch to main |
/git:pr | Create pull request | Request code review |
Documentation
| Command | Description | When to Use |
|---|---|---|
/docs:init | Create initial project documentation | New/undocumented project |
/docs:summarize | Summarize codebase changes | After major changes |
/docs:update | Update existing documentation | Keep docs in sync |
Exploration & Research
| Command | Description | When to Use |
|---|---|---|
/scout | Fast parallel codebase search | Find relevant files for a task |
/scout:ext | Extended search with Gemini 2M context | Deep codebase exploration |
/watzup | Review recent changes in current branch | Wrap up work, understand recent commits |
Questions & Learning
| Command | Description | When to Use |
|---|---|---|
/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 |
|---|---|---|
/kanban | Visual dashboard for plans | View plan progress, timeline visualization |
/preview | Universal markdown/directory viewer | View plans, docs in readable format |
/test | Run tests and analyze results | Verify code changes work |
Design Commands
| Command | Description | When to Use |
|---|---|---|
/design:describe | Describe design from image | Understand existing UI designs |
/design:screenshot | Take screenshot of UI | Capture current state |
/design:video | Record video of UI flow | Document interactions |
/design:3d | Generate 3D assets | Create 3D visuals |
/design:fast | Quick design iteration | Fast UI prototyping |
/design:good | High-quality design | Premium UI work |
Code Review
| Command | Description | When to Use |
|---|---|---|
/review:codebase | Comprehensive codebase review | Quality assessment, find issues |
Planning Variations
| Command | Description | When to Use |
|---|---|---|
/plan | Auto-detect complexity | General planning |
/plan:fast | Quick planning for simple tasks | Small features, quick fixes |
/plan:hard | Deep planning with extensive research | Complex, multi-phase features |
/plan:parallel | Plan multiple independent tasks | Several unrelated features |
/plan:validate | Validate and review existing plan | Before execution |
/plan:archive | Archive completed plan | Clean up finished work |
Common Workflows
Workflow 1: Building a New Feature (Safe)
1. /brainstorm β Explore options
2. /plan β Review plan
3. /clear or /compact
4. /code @plan.md β Implementation
5. /git:cp β Push
6. /git:pr β PR
Workflow 2: Building a Feature (Fast)
1. /cook β Research β Plan β Implement β Test β Review
2. /git:cp β Commit and push when approved
Workflow 3: Debugging & Fixing
1. /debug β Find root cause
2. /fix β Smart routing
3. /git:cm β Commit fix locally
Workflow 4: New Project Setup
1. /bootstrap β Full setup
2. Follow onboarding instructions
Workflow 5: Joining Existing Project
1. /docs:init β Analyze codebase, create docs
2. /scout β Explore codebase structure
Pro Tips
Speed vs Safety Trade-off:
β’ Use /cook when you're confident and want speed
β’ Use /plan β /code when precision and review matter
Never mix these workflows:
β’ β /plan β /cook (cook has its own planning)
β’ β
/plan β /code (correct flow)
β’ β
/cook standalone (has internal planning)
Git safety:
β’ /git:cm = commit only (safe for experimentation)
β’ /git:cp = commits AND pushes (can't undo easily)
Command Complexity Ratings
| Rating | Meaning | Example Commands |
|---|---|---|
| β‘ | Simple, quick | /debug, /test |
| β‘β‘ | Moderate | /brainstorm, /fix, /scout |
| β‘β‘β‘ | Complex, thorough | /cook, /code, /plan |
| β‘β‘β‘β‘ | Extended workflow | /docs:init |
| β‘β‘β‘β‘β‘ | Full project scope | /bootstrap |
Summary Cheat Sheet
| Scenario | Command |
|---|---|
| "I need to build something new from scratch" | /bootstrap |
| "I have an idea but not sure how to approach it" | /brainstorm |
| "I know exactly what I want, do it fast" | /cook |
| "I want to plan carefully before coding" | /plan β /code |
| "Something's broken, I don't know why" | /debug β /fix |
| "Something's broken, I know what it is" | /fix |
| "I need to save my work" | /git:cm or /git:cp |
| "I need to understand this codebase" | /docs:init |
| "I need architectural advice" | /ask |
| "What changed recently?" | /watzup |
| "View my plans visually" | /kanban or /preview |
| "I'm new, slow down explanations" | /coding-level 1 |
| "I need help with ClaudeKit" | /ck-help |
/ck-help β Full documentation/ck-help fix β Category guide for fix commands/ck-help plan:hard β Details on specific command/ck-help how to debug β Task-based recommendations