title: Edit for Clarity and Concision

description: Tighten prose without losing meaning or voice.

content:
Edit the following to be clearer and more concise, preserving my meaning and voice:

{{text}}

Cut filler, redundancy, and hedging. Prefer plain words and active voice. Don't change the substance or make it sound like generic AI prose. Return the edited version, then a short list of the most impactful changes you made.

text

description: The text to edit


title: Adjust Tone

description: Rewrite text to hit a specific tone and audience.

content:
Rewrite the following to be {{tone}} for an audience of {{audience}}:

{{text}}

Keep the core message intact. Match the tone consistently throughout — don't drift back to the original register. Avoid clichés and over-formality. Return the rewrite and note any place where the tone shift forced a change in substance.

tone

description: Desired tone (e.g. friendly, formal, direct)

audience

description: Who will read it

description: The text to rewrite


title: Write a Commit Message

description: Craft a clear, conventional commit message from a change.

content:
Write a commit message for this change:

{{change}}

Format: a concise imperative subject line under ~70 chars, a blank line, then a body that explains WHY the change was made and any consequence a future reader needs. Use a conventional prefix (feat/fix/refactor/docs/test/chore) if the project uses them. Don't just restate the diff — explain the motivation.

change

description: The change (diff or description)


title: Draft a Technical Email

description: Write a clear, actionable email about a technical matter.

content:
Draft an email about: {{topic}}

To: {{recipient}}

Lead with the ask or the key point in the first sentence. Keep it skimmable — short paragraphs, and a clear action with any deadline. Match a professional but human tone. Anticipate the one question the recipient will have and answer it preemptively. End with the specific next step.

topic

description: What the email is about

recipient

description: Who you're writing to


title: Summarize a Document

description: Produce a faithful, useful summary at the right altitude.

content:
Summarize the following for someone who needs to {{purpose}}:

{{text}}

Give: a one-sentence TL;DR, then the key points as a short list, then anything that requires action or a decision. Stay faithful — don't add claims that aren't in the source, and flag where the source is vague or contradicts itself. Match the length to the purpose, not the input.

purpose

description: What the reader needs to do with it

text

description: The document to summarize


title: Write a Proposal

description: Make a persuasive, well-structured case for an idea.

content:
Help me write a proposal for: {{idea}}

Structure: the problem and why it matters now, the proposed solution, the expected benefit (quantified if possible), the cost and risks (stated honestly), and the alternatives considered. Lead with the reader's interest, not mine. Pre-empt the strongest objection. Keep it tight enough that a busy decision-maker reads the whole thing.

idea

description: What you're proposing


title: Give Constructive Feedback

description: Phrase critique so it's heard and actionable.

content:
Help me give feedback on: {{situation}}

Draft feedback that is specific, kind, and actionable. Anchor it to observable behavior and impact, not character. Lead with the most important point. Make the path forward concrete. Avoid the feedback sandwich and vague praise. Keep my respect for the person evident throughout. Show the message and explain the one phrasing choice that matters most.

situation

description: What the feedback is about


title: Rewrite to Remove Jargon

description: Make specialist text accessible without dumbing it down.

content:
Rewrite this to be understandable by {{audience}} without losing accuracy:

{{text}}

Replace jargon with plain language or define it on first use. Keep the technical claims correct — simplify the words, not the truth. Where a concept genuinely requires a term of art, introduce it gently. Return the rewrite and list any term you chose to keep and why.

audience

description: Who needs to understand it

text

description: The jargon-heavy text


title: Tighten Wordy Prose

description: Cut a passage down without losing meaning.

content:
Tighten this without losing meaning or nuance:

{{text}}

Cut filler, redundancy, hedging, and throat-clearing. Prefer strong verbs over noun phrases, and active over passive where it helps. Keep the author's voice. Show the tightened version, then list the 2-3 cuts that mattered most and why. Don't strip qualifications that are actually load-bearing.

description: The text to tighten


title: Adapt Tone for an Audience

description: Rewrite the same content for a different reader.

content:
Rewrite this for a {{audience}} audience:

{{text}}

Keep the facts identical; change the register, vocabulary, and level of detail to fit the reader and what they care about. Adjust the framing to their priorities. Flag any claim that's fine for the original audience but would mislead or under-serve the new one. Show the rewrite and a one-line note on what you shifted and why.

audience

description: The target audience

description: The text to adapt


title: Write a Strong Opening

description: Draft openings that earn the reader's attention.

content:
I'm writing {{piece}} about {{topic}}.

Draft 3 distinct openings that earn attention without clickbait or throat-clearing. Vary the move: one that opens on a concrete specific, one on tension or a question, one on a surprising claim. For each, one line on who it suits and the risk it carries. Then recommend one and say why it fits the piece and audience best.

piece

description: Type of piece (essay, post, email)

topic

description: What it's about


title: Structure a Long Document

description: Find the right outline for a sprawling piece.

content:
I need to structure a long piece covering: {{material}}

Propose an outline that gives the reader a clear path. Decide the organizing principle (chronological, by theme, problem-then-solution, general-to-specific) and justify it for this material. Show the section flow and what each section must accomplish. Flag where a reader would get lost or lose momentum, and what to cut or move. Lead with what the reader most needs first.

material

description: What the piece must cover


title: Write an Executive Summary

description: Compress a long document into what a decider needs.

content:
Write an executive summary of:

{{document}}

Lead with the conclusion and the decision or action it implies — a busy reader should get the point in the first two sentences. Include only what changes their thinking: the key findings, the recommendation, and the cost or risk. Cut the methodology and the narrative; link to the detail. Keep it to a few tight paragraphs. Make sure it stands alone for someone who will never read the full document.

document

description: The document to summarize


title: Outline a Presentation

description: Structure a talk so it lands with an audience.

content:
Help me outline a talk on {{topic}} for {{audience}} in about {{duration}}.

Start from the one thing they should remember and the action you want. Build a spine: a hook that earns attention, the few points that support the message (not everything you know), and a close that lands the takeaway. Budget time per section realistically. Note where a story, demo, or visual beats a bullet list. Cut anything that doesn't serve the single message.

topic

description: The talk topic

audience

description: Who is listening

duration

description: Time available


title: Write a FAQ

description: Answer the questions people actually keep asking.

content:
Write a FAQ for: {{subject}}

Use REAL questions people ask, phrased the way they ask them, ordered by how common they are — not questions invented to show off features. Answer each directly in the first sentence, then add detail. Include the awkward ones (limitations, gotchas, why it works this way) instead of dodging them. Keep each answer self-contained. Cut questions nobody asks, and link out rather than duplicating long explanations.

subject

description: What the FAQ covers


title: Convert Passive to Active

description: Make limp, passive prose direct and clear.

content:
Rewrite this to be more direct:

{{text}}

Turn passive constructions into active where it adds clarity and names the actor — but keep passive where the actor is unknown or irrelevant, or where the object is genuinely the point. Replace nominalizations (decisions were made) with verbs (we decided). Show the rewrite and point out the one or two changes that most sharpen it. Don't mechanically kill every passive; preserve meaning and tone.

text

description: The text to sharpen