Copy-Paste Prompt Collection
Prompts that run as-is when pasted into Claude Code. When you're not sure what to type, start here. Click a card to copy the entire prompt instantly.
Only replace the [bracketed] parts to match your project. Even if you leave the brackets out entirely, Claude will analyze things on its own. Click the Background → link on each card to jump to the chapter that explains the underlying principle.
In Depth — Background and Variations
Below are the full prompts with background explanations. Once you understand the principles, you can adapt them to your own situations.
Setup & Environment
Auto-Generate CLAUDE.md
Background: Writing CLAUDE.md
Analyzes your project structure and creates a CLAUDE.md. It automatically figures out the tech stack, code style, and even the do-not rules.
Analyze this project and create a CLAUDE.md.
Include:
- A one-line description
- Tech stack (language, framework, package manager)
- Key directory structure
- Build/test commands
- Code style (infer patterns from existing code)
- Prohibited actions (e.g., don't modify config files, don't delete existing tests)
Reference config files like package.json, tsconfig, and .eslintrc so it matches the actual project.
Auto-Configure Hooks
Background: The Hooks System
Sets up automatic formatting on file save, blocking dangerous commands, and more.
Set up Claude Code hooks that fit this project.
Check:
- Whether a formatting tool exists (Prettier, ESLint, Black, etc.)
- Whether a test framework exists
Configure:
1. Auto-format after file edits (PostToolUse hook)
2. Block dangerous commands like rm -rf (PreToolUse hook)
Save to .claude/settings.json.
Recommend + Install MCP Servers
Background: Connecting MCP Servers
Finds and installs MCP servers useful for your project.
Check the currently installed MCP servers, then recommend MCP servers that would be useful for this project.
Project characteristics:
- [Services in use: GitHub, Notion, Slack, DB, etc.]
- [Main work: code review, docs management, data queries, etc.]
For each recommendation, explain what the server is for and give the install command.
Coding
Code Review + Commit
Background: Git Integration
Reviews your changes and generates a commit message.
Review my current changes:
1. Check the changes with git diff
2. Check for security problems, performance issues, and edge cases
3. If everything looks good, write a commit message in Conventional Commits format
4. Show me the message and get my confirmation before committing
Multi-File Refactoring
Background: Multi-File Work
Plans and executes changes spanning multiple files, safely.
Implement [the change].
Process:
1. First show me the list of affected files and the change plan
2. Execute once I approve
3. Change one file at a time, verifying the build after each step
Do not touch: [config files, external API call sites, etc.]
Auto-Generate Tests
Background: Test Automation
Finds untested code and adds tests for it.
Find the key functions/modules in this project that have no tests.
When you find them:
1. Prioritize by importance
2. Write tests for the top 3
3. Include happy-path + edge cases + error cases
4. Match the style of existing test files
Test framework: [Jest/Vitest/Pytest, etc. — delete this line if unsure]
Automation & Productivity
Memory Cleanup
Background: The Memory System
Wraps up your work and saves it to memory before the session ends, so the next session doesn't lose context.
Summarize what we did in this session:
1. List of completed work
2. Work in progress (and how far it got)
3. What to pick up next
4. Issues discovered and decisions made
Save it to MEMORY.md, and update CLAUDE.md too if anything belongs there.
Turn a Repeated Task into a Skill
Background: The Skills System
Automates a task you do often into a slash command.
There's a task I repeat often:
[Task description — e.g., "After writing a post, update the frontmatter, add it to the index file, and record the date"]
Turn this into a Skill I can run as /[skill-name].
Save it to .claude/commands/[skill-name].md.
Improve My Prompt
Background: Prompting Strategy
Analyzes a prompt you've been using and suggests a better version.
This is how I usually write my prompt:
"[your usual prompt]"
Analyze this prompt and improve it:
- What parts are unclear
- What constraints are missing
- What to add for better results
Show me the improved prompt.
Usage Tips
- New to this? → Start with Setup & Environment. One good CLAUDE.md raises the quality of every prompt after it.
- You can delete the brackets → Claude analyzes the project on its own. The brackets are just hints.
- Happy with a result? Share it → A screenshot of the output makes the best content.
Click each prompt's "Background" link to understand the principle behind it. Once you know the structure, you can reshape it for any situation.