Skip to content
Shell
6.6 KB
Raw Blame

Which Command Should I Use? πŸ€”

Quick decision tree to pick the right command


Start Here πŸ‘‡

                    What's your goal?
                           β”‚
        β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
        β”‚                  β”‚                  β”‚
   Build Feature      Fix Something     Understand Something
        β”‚                  β”‚                  β”‚
        β–Ό                  β–Ό                  β–Ό
   [Keep reading]     Use /fix          Use /explain

Building a Feature? Ask Yourself...

Question 1: Do you want to learn?

YES - Want to understand HOW and WHY

β†’ Use /feature-dev

Perfect for:
βœ… Learning new concepts
βœ… First time with tech
βœ… Understanding patterns
βœ… Educational experience

Example:
"I want to learn React hooks while building a form"

NO - Just want it done fast

β†’ Use /start

Perfect for:
βœ… You know what to do
βœ… Time pressure
βœ… Simple features
βœ… Repeat patterns

Example:
"Add another button like the existing ones"

Question 2: Do you know what to build?

NO - Still exploring ideas

β†’ Use /idea first
β†’ Then /feature-dev or /start

Perfect for:
βœ… Brainstorming
βœ… Comparing approaches
βœ… Figuring out scope

Example:
"I want better notifications but not sure how"

YES - Clear requirements

β†’ Skip to /feature-dev or /start

Example:
"Add a dark mode toggle in the header"

Complete Decision Matrix

Situation Command Why
"I want to learn" /feature-dev Educational + builds
"I know how, just build it" /start Fast execution
"Not sure what to build" /idea Exploration phase
"Something's broken" /fix Debug + repair
"What does this do?" /explain Understanding
"Did it work?" /test Verification
"Ready to ship?" /preview Pre-ship review
"Where are we?" /status Status check
"What changed?" /compare Diff analysis
"Ship it!" /ship Create PR
"Document this" /docs Documentation
"Clean up code" /cleanup Maintenance
"Undo that" /rollback Revert changes

By Experience Level

🌱 New to Development

Use /feature-dev for everything at first

  • Learn professional practices
  • Understand the "why"
  • Build confidence
  • After 3-5 features, transition to faster commands

🌿 Some Experience

Mix commands based on situation:

  • New concepts β†’ /feature-dev
  • Familiar patterns β†’ /start
  • Quick fixes β†’ /fix
  • Exploration β†’ /idea

🌳 Experienced

Use fast commands, /feature-dev for learning:

  • Standard work β†’ /start, /fix, /ship
  • New tech β†’ /feature-dev
  • Teaching others β†’ /feature-dev (show them)
  • Complex features β†’ /feature-dev (stay thorough)

By Feature Complexity

Simple (< 2 hours)

Quick: /start β†’ /test β†’ /ship
Learning: /feature-dev

Examples:

  • Add a button
  • Create a form field
  • Style tweak

Medium (2-6 hours)

Quick: /start β†’ /test β†’ /preview β†’ /ship
Learning: /feature-dev (recommended)

Examples:

  • User profiles
  • Comment system
  • Favorites feature

Complex (1+ days)

Recommended: /feature-dev
(Thoroughness prevents costly mistakes)

Alternative: /idea β†’ /start β†’ /test β†’ /preview β†’ /ship

Examples:

  • Dashboard with multiple widgets
  • Authentication system
  • Complex integrations

By Time Available

⏰ Time Pressure (Urgent)

/start β†’ /test β†’ /ship
(Skip learning, just deliver)

πŸ• Normal Timeline

/feature-dev
(Learn while building, better quality)

πŸŽ“ Learning Focus (No deadline)

/feature-dev + ask lots of questions
(Deep dive into concepts)

Real Scenarios

Scenario 1: "Add social login"

New to OAuth?
  β†’ /feature-dev (learn authentication flows)

Did it before?
  β†’ /start (faster implementation)

Scenario 2: "Button not working"

Always use: /fix
(Diagnostic workflow)

Scenario 3: "Users want notifications"

Not sure how?
  β†’ /idea (explore options)
  β†’ /feature-dev (implement & learn)

Clear requirements?
  β†’ /feature-dev if complex
  β†’ /start if simple

Scenario 4: "What does useEffect do?"

Always use: /explain useEffect
(Quick understanding)

Scenario 5: "Is this code ready?"

Use: /preview
(Pre-ship checklist)

Command Combos

Full Learning Journey

/idea                  (explore)
/feature-dev           (build & learn)
[automatically tests & ships]

Fast Delivery

/start feature-name    (quick start)
/test                  (verify)
/ship                  (deploy)

Deep Understanding

/status                (see current state)
/explain component.tsx (understand pieces)
/compare               (see changes)
/feature-dev           (build with learning)

Quality Focused

/feature-dev           (thorough build)
/test                  (verify visually)
/preview               (final review)
/ship                  (confident deploy)

Special Cases

"I don't understand the codebase"

1. /status (overview)
2. /explain key files
3. /feature-dev (learn by building)

"Need to ship today"

1. /start (fast)
2. /test (quick check)
3. /ship (deploy)

"Teaching someone else"

1. /feature-dev
2. Let them read the chat
3. Point out teaching moments

"Complex business logic"

Always /feature-dev
(Need to understand deeply)

"Repeating similar feature"

1st time: /feature-dev (learn pattern)
2nd time: /start (faster)
3rd+ time: /start (muscle memory)

Quick Reference

I want to LEARN

β†’ /feature-dev

I want it DONE

β†’ /start

I want to EXPLORE

β†’ /idea

I want to FIX

β†’ /fix

I want to UNDERSTAND

β†’ /explain

I want to CHECK

β†’ /test or /preview

I want to SHIP

β†’ /ship


The Golden Rule

When in doubt, use /feature-dev

Why?

  • βœ… You learn
  • βœ… Builds correctly
  • βœ… Tests thoroughly
  • βœ… Ships professionally
  • βœ… Slows you down just enough to avoid mistakes

You can always speed up later once you know what you're doing!


Still Unsure?

Ask Claude:

"Should I use /feature-dev or /start for [your situation]?"

Claude will recommend based on:

  • Your experience level
  • Feature complexity
  • Learning goals
  • Time constraints

Pro Tip: Your first 3-5 features? Use /feature-dev for ALL of them. The investment in learning pays off forever. πŸŽ“