Writing prompts

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}}

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}}

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.

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.

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.

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.

Rewrite the following at {{percent}}% of its length. Keep every essential fact and the call to action. Remove repetition, hedging and throat-clearing.

{{text}}

Rewrite the following at {{percent}}% of its length. Keep every essential fact and the call to action. Remove repetition, hedging and throat-clearing. {{text}}

Write a documentation page for {{feature}} in {{product}}.

Audience: {{audience}}. Structure: what it is (1 paragraph), when to use it, prerequisites, step-by-step setup with code blocks, configuration options table, examples, troubleshooting, related pages. Use second person and present tense. Mark anything you're unsure about with TODO.

Write a documentation page for {{feature}} in {{product}}. Audience: {{audience}}. Structure: what it is (1 paragraph), when to use it, prerequisites, step-by-step setup with code blocks, configuration options table, examples, troubleshooting, related pages. Use second person and present tense. Mark anything you're unsure about with TODO.

Act as a tough but fair editor. Read my draft and give feedback on: is the main point clear in the first paragraph, structure, weakest argument, anything confusing, anything that should be cut, and the single change that would improve it most. Don't rewrite it; just give the feedback.

Draft:
{{draft}}

Act as a tough but fair editor. Read my draft and give feedback on: is the main point clear in the first paragraph, structure, weakest argument, anything confusing, anything that should be cut, and the single change that would improve it most. Don't rewrite it; just give the feedback. Draft: {{draft}}

Turn these commit messages/PR titles into user-facing release notes for version {{version}}:

{{commits}}

Group as New, Improved, Fixed. Write for users, not developers: describe the benefit, skip internal refactors, max one line each. Add a one-sentence headline for the release.

Turn these commit messages/PR titles into user-facing release notes for version {{version}}: {{commits}} Group as New, Improved, Fixed. Write for users, not developers: describe the benefit, skip internal refactors, max one line each. Add a one-sentence headline for the release.