Bug report a maintainer will read

Model notes: Any model

Fill in the variables (optional — they're inserted live below):

Turn my messy description into a clear bug report for {{project}}. What happened, in my words: {{what_happened}} My environment: {{environment}} Format: - Title: specific, under 80 characters, describing the symptom rather than my guess at the cause. - Summary: one or two sentences. - Steps to reproduce: numbered, starting from a clean state. - Expected result / Actual result. - Environment: versions, OS, browser or runtime. - Logs or screenshots: a placeholder if I didn't provide any. - What I've already tried. Keep my facts exactly as given. Don't add details I didn't mention; put [ADD: ...] where something important is missing. Polite and neutral, no frustration.

How to use it

  1. Fill the variables above, or replace each {{variable}} after pasting.
  2. Paste into your AI tool (ChatGPT, Claude, Gemini, Cursor, Claude Code, or a local model in Ollama/LM Studio).
  3. Review the output. Models make mistakes, especially with facts, numbers and code.
Pro Prompt Pack · US$12

Get all 209 prompts + agent workflows

Every prompt as Markdown and JSON, 10 multi-step agent workflows, and 12 ready-made slash commands for Cursor and Claude Code. Instant zip download, one-time purchase.

Buy the Pro Pack for US$12 What's inside

More Writing prompts

Writing

Edit for clarity, keep my voice

Any model

Variables: text

Edit the text below for clarity and flow while keeping my voice. Rules: keep my word choices where they work, cut filler, break up long sentences, fix grammar, don't add new ideas or corporate phrasing. Then list the 5 most important changes you made and why.

Text:
{{text}}
Open & fill variables: Edit for clarity, keep my voice →
Writing

Blog post from bullet notes

Any model

Variables: audiencenotesword_count

Turn these notes into a blog post for {{audience}}.

Notes:
{{notes}}

Requirements: a specific, non-clickbait title; a hook that states the problem in the first 2 sentences; short sections with descriptive subheadings; concrete examples; a clear takeaway. Length ~{{word_count}} words. Don't invent statistics, quotes or anecdotes — mark [NEED EXAMPLE] where one would help.
Open & fill variables: Blog post from bullet notes →
Writing

Cold email that doesn't sound like spam

Any model

Variables: recipient_rolecompanyofferpersonalisationcall_to_action

Write a cold email to {{recipient_role}} at {{company}}.

What I offer: {{offer}}
Why them specifically: {{personalisation}}
Ask: {{call_to_action}}

Rules: under 120 words, subject line under 6 words, one clear ask, no flattery or buzzwords, plain text. Give 2 variants with different angles.
Open & fill variables: Cold email that doesn't sound like spam →

New prompts every week

One short email a week: new tested prompts and agent workflows. Free. Unsubscribe any time.

Subscribe free →