Prompts that save devs and business owners hours. Our own prompts, each built on one technique from the official guides. Fill in the square brackets, then paste.
1. Review a pull request
You are a senior code reviewer. Review this diff for bugs, security and clarity; rank issues by severity.
Copy
Use it for: a second pair of eyes before you merge.
Technique: Give it a role, from Anthropic, Prompting best practices ("Give Claude a role").
2. Explain a stack trace
Explain the error in <trace></trace> in plain words, give the likely cause, then the smallest fix.
Copy
Use it for: a crash you can't read yet.
Technique: Use XML tags, from Anthropic, Prompting best practices ("Structure prompts with XML tags").
3. Write a README
Write a README for this repo with: What it does, Install, Usage, Config. Markdown, under 300 words.
Copy
Use it for: a project nobody documented.
Technique: Set the response format, from Google, Gemini prompt design strategies ("Response format").
4. Summarize customer feedback
Our product: [what it is, for whom]. Group this feedback into themes, most frequent first, one quote each.
Copy
Use it for: a pile of reviews or support tickets.
Technique: Include relevant context, from OpenAI, Prompt engineering ("Include relevant context information").
5. Draft a cold email
Write a cold email to [role] about [offer]: under 120 words, one ask. Match this example's tone: [paste]
Copy
Use it for: a first draft of outreach.
Technique: Show an example, from OpenAI, Prompt engineering ("Few-shot learning").
6. Write SQL from a question
Schema: [paste tables]. Write one SQL query that answers: [question]. If it can't, say what's missing.
Copy
Use it for: a question your data can answer.
Technique: Add context, from Google, Gemini prompt design strategies ("Add context").
Techniques: Anthropic, OpenAI, Google prompt guides, read 2026-10-10.