Best Claude Code Tips & Tricks (2026)

Review my CLAUDE.md file and suggest improvements. Focus on:
1. Missing context that would help you understand my codebase faster
2. Ambiguous instructions that could be interpreted multiple ways
3. Redundant or contradictory rules
4. Missing build/test/lint commands
5. Directory structure gaps

My tech stack is {{tech_stack}} and the project is a {{project_description}}.

Output a revised CLAUDE.md that follows best practices: structured sections, specific over vague, commands copy-pasteable, and under 800 words.

I need to {{describe_change}} across my codebase.

Affected areas:
- {{file_or_module_1}}
- {{file_or_module_2}}
- {{file_or_module_3}}

Requirements:
- Keep all existing tests passing
- Follow the naming conventions in CLAUDE.md
- Update any imports that change
- Do NOT modify files outside the listed areas

Make the changes file by file. After each file, briefly explain what changed and why.

I'm starting a new task in a long session. Before we proceed:

1. Summarize the key changes we've made so far in this session
2. List any files that are currently modified but uncommitted
3. Note any decisions or constraints we established

Then use /compact to trim context. After compacting, I'll describe the next task.

The new task is: {{next_task}}

I'm seeing this error:

{{error_message}}

It happens when I {{trigger_action}}.

Debug this step by step:
1. Read the relevant source files around the error
2. Check if there are related tests that cover this path
3. Identify the root cause (not just the symptom)
4. Propose a fix with minimal changes
5. Verify the fix doesn't break related functionality

Do NOT guess — read the actual code before suggesting anything.

Generate tests for {{file_path}}.

Testing requirements:
- Framework: {{test_framework}}
- Cover happy path, edge cases, and error handling
- Mock external dependencies (DB, API calls, file system)
- Follow the test patterns already used in this project (check existing test files first)
- Each test should have a descriptive name explaining the scenario

Do NOT test private implementation details — only test the public API/exports of the module.

Set up a new {{framework}} project with the following requirements:

Stack: {{tech_stack}}
Features: {{feature_list}}

Steps:
1. Initialize the project with standard tooling
2. Set up the directory structure following {{framework}} best practices
3. Configure TypeScript, linting, and formatting
4. Create a CLAUDE.md with the full project context
5. Add a .claude/skills/ directory with a deploy skill
6. Create a basic README with setup instructions
7. Make an initial git commit

Use the latest stable versions of all dependencies. Do not add anything I didn't ask for.

Review the uncommitted changes in this repo. For each modified file:

1. Summarize what changed
2. Flag any bugs, type errors, or logic issues
3. Check for missing error handling
4. Note any style violations against our CLAUDE.md conventions
5. Suggest improvements (but keep them optional)

Then give me a one-paragraph summary of whether this diff is ready to commit or needs changes. Suggest a conventional commit message if it's ready.

My MCP server {{server_name}} isn't working in Claude Code.

Symptoms: {{symptoms}}

Help me debug:
1. Check if the server is registered in ~/.claude.json under this project
2. Verify the command and args are correct
3. Check if environment variables are set (list which ones are needed)
4. Test if the server binary/script exists at the configured path
5. Look for common issues: wrong Node version, missing build step, port conflicts

Show me the exact commands to run for each diagnostic step.