# Delegate planning to GLM (saves Sonnet tokens)
/ccs glm /plan "add user authentication"

# Delegate coding to GLM
/ccs glm /code "implement auth endpoints"

# Quick questions with Haiku
/ccs haiku /ask "explain this error"

# Continue last delegation with follow-up
/ccs:continue "add error handling to that feature"

# Works with any previous delegation context
/ccs:continue "also add unit tests"

# Direct prompt execution
ccs -p "your prompt"
ccs --prompt "your prompt"

# With specific profile
ccs glm -p "implement feature"
ccs codex --prompt "analyze this code"

# Step 1: Architecture & Planning (needs Claude's intelligence)
ccs
/plan "Design payment integration with Stripe"
# → Claude Sonnet 4.5 thinks deeply about edge cases

# Step 2: Implementation (straightforward, use GLM)
ccs glm
/code "implement the payment webhook handler"
# → GLM 4.6 writes code efficiently, saves usage

# Step 3: Code Review (needs deep analysis)
ccs
/review "check payment handler for security"
# → Claude Sonnet catches subtle vulnerabilities

# Step 4: Bug Fixes (simple)
ccs glm
/fix "update error message formatting"
# → GLM handles routine fixes

# Step 5: Continue with follow-up
/ccs:continue "also add logging to the webhook"
# → Continues from previous context

# Working on complex refactoring with Claude
ccs
/plan "refactor authentication system"

# Claude hits rate limit mid-task
# → Error: Rate limit exceeded

# Switch to GLM instantly
ccs glm
# Continue working without interruption

# Rate limit resets? Switch back
ccs

# Force GLM for simple tasks
/ccs --glm "task description"

# Force Kimi for long context
/ccs --kimi "analyze this large codebase"

# Force Codex for quick iterations
/ccs --codex "quick prototype"

# Force Kimi for Coding API reasoning
/ccs --km "reason through this failing test"