Stats
Links
Categories
40+ Claude Code Tips: From Basics to Advanced
Here are my tips for getting the most out of Claude Code, including a custom status line script, cutting the system prompt in half, using Gemini CLI as Claude Code's minion, and Claude Code running itself in a container. Also includes the dx plugin.
📺 Quick demo - See some of these tips in action with a multi-Claude workflow and voice input:
Table of Contents
- Tip 0: Customize your status line
- Tip 1: Learn a few essential slash commands
- Tip 2: Talk to Claude Code with your voice
- Tip 3: Break down large problems into smaller ones
- Tip 4: Using Git and GitHub CLI like a pro
- Tip 5: AI context is like milk; it's best served fresh and condensed!
- Tip 6: Getting output out of your terminal
- Tip 7: Set up terminal aliases for quick access
- Tip 8: Proactively compact your context
- Tip 9: Complete the write-test cycle for autonomous tasks
- Tip 10: Cmd+A and Ctrl+A are your friends
- Tip 11: Use Gemini CLI as a fallback for blocked sites
- Tip 12: Invest in your own workflow
- Tip 13: Search through your conversation history
- Tip 14: Multitasking with terminal tabs
- Tip 15: Slim down the system prompt
- Tip 16: Git worktrees for parallel branch work
- Tip 17: Manual exponential backoff for long-running jobs
- Tip 18: Claude Code as a writing assistant
- Tip 19: Markdown is the s**t
- Tip 20: Use Notion to preserve links when pasting
- Tip 21: Containers for long-running risky tasks
- Tip 22: The best way to get better at using Claude Code is by using it
- Tip 23: Clone/fork and half-clone conversations
- Tip 24: Use realpath to get absolute paths
- Tip 25: Understanding CLAUDE.md vs Skills vs Slash Commands vs Plugins
- Tip 26: Interactive PR reviews
- Tip 27: Claude Code as a research tool
- Tip 28: Mastering different ways of verifying its output
- Tip 29: Claude Code as a DevOps engineer
- Tip 30: Keep CLAUDE.md simple and concise
- Tip 31: Claude Code as the universal interface
- Tip 32: It's all about choosing the right level of abstraction
- Tip 33: Audit your approved commands
- Tip 34: Write lots of tests (and use TDD)
- Tip 35: Be braver in the unknown; iterative problem solving
- Tip 36: Running bash commands and agents in the background
- Tip 37: The era of personalized software is here
- Tip 38: Navigating and editing your input box
- Tip 39: Spend some time planning, but also prototype quickly
- Tip 40: Simplify overcomplicated code
- Tip 41: Automation of automation
- Tip 42: Share your knowledge and contribute where you can
- Tip 43: Keep learning!