Introduction
Claude Code has built-in commands. These commands help developers manage conversations, projects and models easily. They also help with usage. You can use these commands in the Claude Code terminal by using this way you do not have to write prompts for common actions. The commands make it simpler to get things done. You can manage conversations efficiently and you can also manage projects, models and usage efficiently with these commands. Claude Code commands are very helpful, for developers. which save time and make work easier.
1. claude -r
Purpose: Resume the most recent Claude Code session directly from the terminal.
Use Case: When you close Claude Code and want to continue working on the same project without starting a new conversation.
claude -r
2. /resume
Purpose: Reopen a previous conversation or working session.
Use Case: Continue a coding task from where you left off.
/resume
3. /rename
Purpose: Rename the current chat or session.
Use Case: Organize multiple projects and conversations more effectively.
/rename Authentication Refactor
4. /btw
Purpose: Displays useful tips, shortcuts, and productivity suggestions.
Use Case: Learn Claude Code features that you may not be using.
/btw
5. /export
Purpose: Export the current conversation.
Use Case: Save discussions, code reviews, architecture explanations, or project documentation.
/export filename.md
6. /logout
Purpose: Sign out of your Claude account.
Use Case: Switch accounts or secure your session.
/logout
7. /model
Purpose: View or change the active Claude model.
Use Case: Switch between Haiku, Sonnet, or Opus depending on the task.
/model
8. /usage
Purpose: Displays token consumption and usage information.
Use Case: Monitor API usage and control costs.
/usage
9. /stats
Purpose: Shows statistics about your current session.
Use Case: Understand how much work Claude has performed during the session.
/stats
10. /insights
Purpose: Provides insights about your workflow and project interactions.
Use Case: Review how Claude is assisting with development and identify productivity patterns.
/insights
11. /voice
Purpose: Enables voice-based interaction with Claude Code.
Use Case: Speak commands or questions instead of typing.
/voice
Claude Models Explained
Claude Code can use different Claude models depending on the complexity of the task. Each model is designed for a different speed, cost, and intelligence.
Claude Haiku
Fastest and most affordable Claude model.
Best For:
- Quick questions
- Simple coding tasks
- Small code changes
- Documentation generation
- Fast responses
tip: Use Haiku when speed matters more than deep reasoning.
Claude Sonnet
Balanced model offering strong reasoning and good speed.
Best For:
- Daily software development
- Debugging
- Code reviews
- Feature development
- Most programming tasks
Tip: Sonnet is the recommended model for most developers.
Claude Opus
Most powerful Claude model.
Best For:
- Complex debugging
- Large codebases
- Architecture design
- Multi-step reasoning
- Difficult engineering problems
Tip: Use Opus when accuracy and deep reasoning are more important than speed or cost.
Which Model Should You Use?
| Model | Speed | Cost | Reasoning | Best For |
|---|---|---|---|---|
| Haiku | Very Fast | Lowest | Basic | Quick tasks |
| Sonnet | Fast | Medium | Strong | Everyday coding |
| Opus | Slower | Highest | Excellent | Complex engineering |
Simple Rule
Haiku → Small tasks and quick responses.
Sonnet → Default choice for most coding work.
Opus → Deep analysis, architecture, and difficult debugging.
For most developers using Claude Code daily, Sonnet is usually the best balance of speed, intelligence, and cost.
