3 min read
Prompts Library
Copy-paste prompts for common tasks.
How to Use These
- Start Claude Code in your project folder:
claude - Copy a prompt from below
- Modify the bracketed parts
[like this]for your situation - Paste and press Enter
These are starting points. Modify them as needed.
Quick Reference
| Category | When to Use |
|---|---|
| Setup | Starting projects, initializing structure |
| Features | Adding functionality |
| Styling | Visual polish and UI adjustments |
| Polish | Refining from prototype to finished product |
| Debugging | When things break |
| Deployment | Deploying to Vercel, App Store, TestFlight |
| Data & Persistence | Saving, loading, and managing data |
| Images & Assets | Working with images, icons, and visual assets |
| Platform-Specific | macOS, iOS, and web-specific features |
| Testing | Testing your app before shipping |
| Git | Saving progress, undoing mistakes, versioning |
| Performance | Making your app faster |
| Understanding | Learning what code does |
| Refactoring | Improving existing code |
Most Used Prompts
Start a new project
I want to build [description]. It should [main functionality].
The target platform is [macOS/iOS/web].Add a feature
Add [feature]. When the user [action], it should [result].Fix something broken
[Describe what you did]. Expected [what should happen],
but instead [what actually happened].
Here's the error: [paste error]Make it look better
The [element] doesn't look right. [Describe the problem].
I want it to [describe desired appearance].Explain code
Explain what [file/function] does in simple terms.Tips
- Be specific — “Make it better” is vague; “Add more padding and make the text darker” is actionable
- One thing at a time — Small prompts beat big prompts
- Include context — Reference what you just did or what you’re trying to achieve
- Describe outcomes — “When the user clicks X, they should see Y”
- Reference examples — “Like Notion’s sidebar” conveys a lot
Reviewing Claude’s Work
Don’t just accept what Claude builds. These prompts help you evaluate the work critically before moving on.
Understand what changed
Walk me through what you just changed and why.Check edge cases
Are there any edge cases this doesn't handle? What happens if [scenario]?Push for simplicity
Is this the simplest way to do this? Could it be simpler?Check accessibility
Check this for accessibility issues.Verify against specs
Does this match the design specs in CLAUDE.md?See individual category pages for more specific prompts.