Skip to main content
This page collects short recipes for everyday development. For higher-level guidance on prompting and context management, see Best practices. This page covers:

​
Prompt recipes

These are prompt patterns for everyday tasks like exploring unfamiliar code, debugging, refactoring, writing tests, and creating PRs. Each works in any Claude Code surface; adapt the wording to your project.

​
Understand new codebases

For configuring Claude Code in a monorepo or large codebase, see Monorepos and large repos.

​
Get a quick codebase overview

Suppose you’ve just joined a new project and need to understand its structure quickly.
1

Navigate to the project root directory

2

Start Claude Code

3

Ask for a high-level overview

4

Dive deeper into specific components

Tips:
  • Start with broad questions, then narrow down to specific areas
  • Ask about coding conventions and patterns used in the project
  • Request a glossary of project-specific terms

​
Find relevant code

Suppose you need to locate code related to a specific feature or functionality.
1

Ask Claude to find relevant files

2

Get context on how components interact

3

Understand the execution flow

Tips:
  • Be specific about what you’re looking for
  • Use domain language from the project
  • Install a code intelligence plugin for your language to give Claude precise “go to definition” and “find references” navigation

​
Fix bugs efficiently

Suppose you’ve encountered an error message and need to find and fix its source.
1

Share the error with Claude

2

Ask for fix recommendations

3

Apply the fix

Tips:
  • Tell Claude the command to reproduce the issue and get a stack trace
  • Mention any steps to reproduce the error
  • Let Claude know if the error is intermittent or consistent

​
Refactor code

Suppose you need to update old code to use modern patterns and practices.
1

Identify legacy code for refactoring

2

Get refactoring recommendations

3

Apply the changes safely

4

Verify the refactoring

Tips:
  • Ask Claude to explain the benefits of the modern approach
  • Request that changes maintain backward compatibility when needed
  • Do refactoring in small, testable increments

​
Work with tests

Suppose you need to add tests for uncovered code.
1

Identify untested code

2

Generate test scaffolding

3

Add meaningful test cases

4

Run and verify tests

Claude can generate tests that follow your project’s existing patterns and conventions. When asking for tests, be specific about what behavior you want to verify. Claude examines your existing test files to match the style, frameworks, and assertion patterns already in use. For comprehensive coverage, ask Claude to identify edge cases you might have missed. Claude can analyze your code paths and suggest tests for error conditions, boundary values, and unexpected inputs that are easy to overlook.

​
Create pull requests

You can create pull requests by asking Claude directly (“create a pr for my changes”), or guide Claude through it step-by-step:
1

Summarize your changes

2

Generate a pull request

3

Review and refine

When you create a PR using gh pr create, the session is automatically linked to that PR. To return to it later, run claude --from-pr 123, replacing 123 with the PR number, or paste the PR URL into the /resume picker search.
Review Claude’s generated PR before submitting and ask Claude to highlight potential risks or considerations.

​
Handle documentation

Suppose you need to add or update documentation for your code.
1

Identify undocumented code

2

Generate documentation

3

Review and enhance

4

Verify documentation

Tips:
  • Specify the documentation style you want (JSDoc, docstrings, etc.)
  • Ask for examples in the documentation
  • Request documentation for public APIs, interfaces, and complex logic

​
Work in notes and non-code folders

Claude Code works in any directory. Run it inside a notes vault, a documentation folder, or any collection of markdown files to search, edit, and reorganize content the same way you would code. The .claude/ directory and CLAUDE.md sit alongside other tools’ config directories without conflict. Claude reads files fresh on each tool call, so it sees edits you make in another application the next time it reads that file.

​
Work with images

Suppose you need to work with images in your codebase, and you want Claude’s help analyzing image content.
1

Add an image to the conversation

You can use any of these methods:
  1. Drag and drop an image into the Claude Code window
  2. Copy an image and paste it into the CLI with Ctrl+V. On macOS, Cmd+V also works in iTerm2.
  3. Provide an image path to Claude. E.g., “Analyze this image: /path/to/your/image.png”
2

Ask Claude to analyze the image

3

Use images for context

4

Get code suggestions from visual content

Tips:
  • Use images when text descriptions would be unclear or cumbersome
  • Include screenshots of errors, UI designs, or diagrams for better context
  • You can work with multiple images in a conversation
  • Image analysis works with diagrams, screenshots, mockups, and more
  • When Claude references images (for example, [Image #1]), Cmd+Click (Mac) or Ctrl+Click (Windows/Linux) the link to open the image in your default viewer

​
Reference files and directories

Use @ to quickly include files or directories without waiting for Claude to read them.
1

Reference a single file

This includes the full content of the file in the conversation.
2

Reference a directory

This provides a directory listing with file information.
3

Reference MCP resources

This fetches data from connected MCP servers using the format @server:resource. See MCP resources for details.
Tips:
  • File paths can be relative or absolute
  • @ file references add CLAUDE.md in the file’s directory and parent directories to context
  • Directory references show file listings, not contents
  • You can reference multiple files in a single message (for example, “@file1.js and @file2.js”)

​
Run Claude on a schedule

Suppose you want Claude to handle a task automatically on a recurring basis, like reviewing open PRs every morning, auditing dependencies weekly, or checking for CI failures overnight. Pick a scheduling option based on where you want the task to run:
When writing prompts for scheduled tasks, be explicit about what success looks like and what to do with results. The task runs autonomously, so it can’t ask clarifying questions. For example: “Review open PRs labeled needs-review, leave inline comments on any issues, and post a summary in the #eng-reviews Slack channel.”

​
Ask Claude about its capabilities

Claude has built-in access to its documentation and can answer questions about its own features and limitations.

​
Example questions

Claude provides documentation-based answers to these questions. For hands-on demonstrations, run /powerup for interactive lessons with animated demos, or refer to the specific workflow sections above.
Tips:
  • Claude always has access to the latest Claude Code documentation, regardless of the version you’re using
  • Ask specific questions to get detailed answers
  • Claude can explain complex features like MCP integration, enterprise configurations, and advanced workflows

​
Resume previous conversations

When a task spans multiple sittings, pick up where you left off instead of re-explaining context. Claude Code saves every conversation locally.
This resumes the most recent session in the current directory; if there isn’t one yet, it prints No conversation found to continue and exits. Use claude --resume to choose from a list, or /resume from inside a running session. See Manage sessions for naming, branching, and the full picker reference.

​
Run parallel sessions with worktrees

Work on a feature in one terminal while Claude fixes a bug in another, without the edits colliding. Each worktree is a separate checkout on its own branch.
Run the same command with a different name in a second terminal to start an isolated parallel session. See Worktrees for cleanup, .worktreeinclude, and non-git VCS support. To monitor parallel sessions from one screen instead of separate terminals, see background agents.

​
Plan before editing

For changes you want to review before they touch disk, switch to plan mode. Claude reads files and proposes a plan but makes no edits until you approve.
You can also press Shift+Tab mid-session to toggle into plan mode. See Plan mode for the approval flow and editing the plan in your text editor.

​
Delegate research to subagents

Exploring a large codebase fills your context with file reads. Delegate the exploration so only the findings come back.
The subagent reads files in its own context window and reports a summary. See Subagents for defining custom agents with their own tools and prompts.

​
Pipe Claude into scripts

Run Claude non-interactively for CI, pre-commit hooks, or batch processing. Stdin and stdout work like any Unix tool.
See Non-interactive mode for output formats, permission flags, and fan-out patterns.

​
Next steps

Best practices

Patterns for getting the most out of Claude Code

Manage sessions

Resume, name, and branch conversations

Worktrees

Run isolated parallel sessions

Extend Claude Code

Add skills, hooks, MCP, subagents, and plugins