| name | writing-editor |
| description | Improve or write prose: tighten, clarify, fix grammar, and adjust tone/length while preserving the author's voice and meaning. Use when users ask to edit, proofread, rewrite, polish, shorten, or change the tone of text, or to draft something from notes. Triggers on mentions of edit, proofread, rewrite, polish, tighten, make it shorter/clearer/more formal, fix grammar, 润色, 改写, 校对, 修改, 精简, 改语气, 帮我写. |
| license | Proprietary. LICENSE.txt has complete terms |
| compatibility | No external dependencies. Works on macOS, Linux, and Windows. |
Writing & Editing
Make the text clearer and tighter without making it sound like a different person.
Editing principles
- Cut what doesn't earn its place — filler, hedging, throat-clearing, redundancy.
- Lead with the point. Put the main idea first; don't bury it under setup.
- Prefer plain, concrete words over jargon and abstraction. Short sentences for key points.
- Active voice and strong verbs ("we shipped X", not "X was shipped").
- Keep the author's voice. Edit for clarity, not to impose your own style.
- Match the register the user wants: casual, professional, formal, playful.
Workflow
- Confirm the goal: just proofread? tighten? change tone? hit a length?
- Return the improved version.
- If the user wants, add a short note on the 2–3 most impactful changes (don't list every comma).
Quick controls
- "Make it shorter" → cut ~30–50%, keep all the substance, drop the padding.
- "More formal" → remove contractions/slang, measured tone; "more casual" → contractions, lighter.
- "Punchier" → shorter sentences, stronger verbs, lead with the hook.
Guidance
- Don't change meaning or invent facts while editing. If a claim seems off, flag it, don't silently fix.
- Preserve formatting the user relies on (lists, code, links) unless asked to restructure.
- For long pieces, fix structure first (order, headings), then sentence-level polish.
