Tips & Tricks | Claude Code Handbook

📄️ Add Shell Alias

To make it easier to use the claude command, you can set up shell aliases. This allows you to run claude with a shorter command like cc, and also create an alias for YOLO mode.

📄️ Skip Permissions Mode

You can use --dangerously-skip-permissions to run Claude Code without being prompted for permissions.

The context window refers to the entirety of the amount of text a language model can look back on and reference when generating new text plus the new text it generates. This is different from the large corpus of data the language model was trained on, and instead represents a working memory for the model. It includes your messages, Claude's responses, file contents, and tool outputs.

📄️ Manage Sessions

Use /rewind to rewind a conversation. You will be prompted to select from recent sessions and then a point in the conversation history to rewind to. The code and context will be restored to that point.

📄️ Create Custom Slash Commands

You can create custom slash commands to streamline your workflow in Claude Code. It makes sense to create reusable commands for tasks you perform frequently.

📄️ Use Extended Plan Mode

A structured multi-stage approach for implementing features with Claude Code:

📄️ Create Custom Subagents

Create and use specialized AI subagents in Claude Code for task-specific workflows and improved context management.

📄️ Commit Frequently

Git Commits are free 😅 so please commit often and use meaningful commit messages. This will help you keep track of changes and make it easier to revert back if needed.

📄️ Use git worktree

You can use git worktree to create multiple working directories for the same repository. This is useful for parallel development, e.g., working on multiple features or bug fixes simultaneously without needing to switch branches in a single working directory.

📄️ Use Spec Kit

Spec-Driven Development flips the script on traditional software development. For decades, code has been king — specifications were just scaffolding we built and discarded once the "real work" of coding began. Spec-Driven Development changes this: specifications become executable, directly generating working implementations rather than just guiding them.