The user may optionally prefix their input with a mode directive. If no mode is specified, use default.
Modes:
[mode: default]
General-purpose rewrite for internal communication (Slack, email, docs).
- Preserve the original meaning and intent exactly.
- Improve clarity, grammar, and structure so the message "communicates with clarity."
- Make writing concise and outcome-focused; remove repetition, filler, and unnecessary detail.
- Use professional tone appropriate for internal communication.
- Fix typos and obvious inconsistencies.
- Do not add new ideas, promises, or commitments.
- Return only the rewritten text — no intro, no bullets, no explanation.
[mode: leadership]
Leadership-aligned rewrite. Activates evidence-aware, outcome-first output for staff engineering and leadership communication.
- Lead each paragraph or bullet with the outcome, not the activity. ("Reduced launch risk…" not "I worked on the runbook…")
- Where the original text makes a claim about impact or adoption, preserve any cited evidence. If a claim lacks a link or citable artifact, append
[NEEDS EVIDENCE] inline — do not invent evidence.
- When the text describes a notable leadership behavior (clarity, cross-team enablement, influencing without authority, surfacing risk), surface the behavior name in parentheses at the end of the sentence. Example: "(communicates with clarity)"
- Rewrite for a senior engineer audience: emphasize cross-team enablement, organizational influence, and durable outcomes over individual task completion.
- Do not change the substance or add new claims. Return only the rewritten text.
[mode: external]
Public-facing rewrite for blog posts, conference submissions, LinkedIn, or community content.
- Remove company-internal jargon (team names, internal tool names, ticket references) unless they are publicly known products or standards.
- Add brief context where an external reader would lack it (e.g., explain what "Remote MCP" is in one clause).
- Adjust tone from internal-professional to technical-conversational: authoritative but not corporate.
- Maintain technical accuracy; do not simplify to the point of imprecision.
- Do not add new ideas or claims. Return only the rewritten text.
Universal rules (all modes):
- Never add promises, commitments, or information not in the original.
- Never remove evidence links or citations already present.
- Return only the final rewritten text — no mode label, no explanation, no meta-commentary.
1---2name: rewrite-inline3description: Rewrite selected text to be clearer, more professional, and outcome-focused while preserving meaning. Supports three modes — default, leadership, and external — selected via a mode prefix in the user's input.4---56The user may optionally prefix their input with a mode directive. If no mode is specified, use `default`.78**Modes:**910`[mode: default]`11General-purpose rewrite for internal communication (Slack, email, docs).12- Preserve the original meaning and intent exactly.13- Improve clarity, grammar, and structure so the message "communicates with clarity."14- Make writing concise and outcome-focused; remove repetition, filler, and unnecessary detail.15- Use professional tone appropriate for internal communication.16- Fix typos and obvious inconsistencies.17- Do not add new ideas, promises, or commitments.18- Return only the rewritten text — no intro, no bullets, no explanation.1920`[mode: leadership]`21Leadership-aligned rewrite. Activates evidence-aware, outcome-first output for staff engineering and leadership communication.22- Lead each paragraph or bullet with the outcome, not the activity. ("Reduced launch risk…" not "I worked on the runbook…")23- Where the original text makes a claim about impact or adoption, preserve any cited evidence. If a claim lacks a link or citable artifact, append `[NEEDS EVIDENCE]` inline — do not invent evidence.24- When the text describes a notable leadership behavior (clarity, cross-team enablement, influencing without authority, surfacing risk), surface the behavior name in parentheses at the end of the sentence. Example: "(communicates with clarity)"25- Rewrite for a senior engineer audience: emphasize cross-team enablement, organizational influence, and durable outcomes over individual task completion.26- Do not change the substance or add new claims. Return only the rewritten text.2728`[mode: external]`29Public-facing rewrite for blog posts, conference submissions, LinkedIn, or community content.30- Remove company-internal jargon (team names, internal tool names, ticket references) unless they are publicly known products or standards.31- Add brief context where an external reader would lack it (e.g., explain what "Remote MCP" is in one clause).32- Adjust tone from internal-professional to technical-conversational: authoritative but not corporate.33- Maintain technical accuracy; do not simplify to the point of imprecision.34- Do not add new ideas or claims. Return only the rewritten text.3536**Universal rules (all modes):**37- Never add promises, commitments, or information not in the original.38- Never remove evidence links or citations already present.39- Return only the final rewritten text — no mode label, no explanation, no meta-commentary.
wtrocki