菜单
Zinsser-first plain writing style for any writing or editing task. Invoke before creating, editing, critiquing, rewriting, outlining, prompting, or polishing prose, docs, posts, proposals, teardown notes, social posts, emails, prompts, or skill instructions.**
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | writing-style |
| description | Zinsser-first plain writing style for any writing or editing task. Invoke before creating, editing, critiquing, rewriting, outlining, prompting, or polishing prose, docs, posts, proposals, teardown notes, social posts, emails, prompts, or skill instructions.** |
Strip every sentence to its cleanest components. Every word must earn its place.
No throat-clearing. Start with the point, not a warm-up. Cut openings like "In this post, I'll show you..." or "It's worth noting that...". Just say the thing.
No nounism. Use verbs, not noun clusters. "We made a decision to implement" → "We decided to implement." "The establishment of a connection" → "Connecting."
No clutter. Eliminate:
Active voice. "The bug was fixed by the team" → "The team fixed the bug."
Concrete over abstract. Show specifics, not generalizations. "Performance improved significantly" → "Response time dropped from 2s to 200ms." Only if you have direct information in the source material.
Short sentences, short paragraphs. One idea per sentence. Dense paragraphs lose readers.
First person, direct. "I built...", "We discovered...", "The code does X."
No corrective constructions. Don't say "It's not X, it's Y". Just say Y.
No em dashes. They signal AI writing. Use periods, commas, or parentheses instead.
No dead constructions. "There are three reasons" → "Three reasons". "It is important to" → cut entirely or rephrase. These delay the subject.
No weasel words. "Some users reported" → "Users reported" or give the number. "Often" and "generally" hedge without adding. Commit or cut.
Strong verbs. Replace weak verbs (is, was, has, make, do, get) with specific ones. "The function does validation" → "The function validates." "We made improvements" → "We improved."
Unity. One tense, one voice, one mood. Don't drift between past and present, or between "I" and "we" and "you". Pick and stick.
Parallel structure. Lists and comparisons must match grammatically. "Fast, reliable, and it scales well" → "Fast, reliable, and scalable."
Rhythm matters, but sparingly. Vary sentence length for flow. Don't let it become sing-song.
No hype. Skip inflated claims, buzzwords, and empty superlatives.
No fake urgency. If it is not urgent, do not write like it is.
Stick to the source. Use specifics from the source material only. If the source does not say it, omit it.
Say what you know. If you are unsure, be plain about it or leave it out.
Plain words. Prefer simple, direct language over cleverness.
Clear structure. Use strong headers and short paragraphs. Break when a new idea starts.
Concrete detail. If you can make it specific, do. If you can't, leave it out.
Value density. Every paragraph earns its place. Cut sentences that add no information.
These phrases and patterns signal AI writing. Never use them:
Throat-clearing to cut:
❌ "A good user experience is often invisible. It removes friction and lets you move from A to B without thinking. Many of the latest updates are focused on just that. First, you'll find your remaining credits are always visible in the navigation bar."
✓ "Your remaining credits now show in the navigation bar."
Nounism to fix:
❌ "The implementation of the feature required modification of the configuration."
✓ "We had to modify the config to implement the feature."
Clutter to eliminate:
❌ "The main dashboard is now smarter. It gives you an at-a-glance view of which content formats have been generated. This makes it easy to spot what's done."
✓ "The dashboard shows which formats have been generated for each project."
Write like you talk to a friend. If you wouldn't say it across a table, don't write it. The reader wants a person, not a committee.
Your personality is your authority. The things you find funny, the observations that catch you off guard, the small details that stick with you. Put them in. They're what separate your writing from anyone else's. Zinsser: "Readers want the person who is talking to them to sound genuine."
Don't worry about the audience. Write for yourself. If you find it interesting, trust that. The moment you start writing for some imagined reader, you sand off everything that made it yours.
Small, casual words. "Use" not "utilize." "Buy" not "purchase." "Help" not "facilitate." The short word is almost always the honest one. Zinsser called big words "the language of the pretender."
Leave yourself in. If something surprised you, say so. If you thought something was funny, let that show. The humanity is the point. Writing scrubbed of personality is writing nobody wants to read.
Brevity carries voice too. You can write a whole book in short sentences and small words and still hold a reader. Tight writing is not cold writing. The constraint forces you to pick words that carry weight, and those words carry personality with them.
Write tight. Every sentence delivers information. No warm-ups, no wind-downs. But write warm. The reader should hear a person.
Use when navigating Wikipedia inside the split-pane extension—finding articles from a topic or phrase, teaching or routing the user toward articles, choosing what to explore next, Wikimedia REST or Action APIs with paging, or sending message_parent url_change (optional section `#fragment` on the same wiki). Use for Wikipedia search, summaries, links/backlinks, or updating the mirrored page URL.
Apply rich formatting to Notion pages - toggles, callouts, headers, and styled text. Use when creating or formatting Notion documents via the Notion MCP server.
Design and author Hermes Workflows with typed inputs/outputs, agent/bash/ask/parallel/pipeline/goal primitives, Review Queue gates, artifacts, and verification receipts. Use when creating or modifying workflow definitions.
Plan new software projects by decomposing the goal into MVP tasks, researching frameworks and libraries with subagents, and preferring opinionated prebuilt solutions over bespoke complexity. Use when starting a new project, scoping an idea, choosing a stack, or producing an implementation plan for a single-user MVP.
Draft or revise any kind of writing so it is clearer, better structured, and more effective for its audience. Use for essays, emails, memos, articles, narratives, speeches, social posts, marketing copy, personal writing, documentation, technical writing, reports, proposals, and mixed-format prose while preserving meaning and facts.
How to build high-quality Remotion animated videos for social media (square 1080×1080 and vertical 1080×1920). Use this skill whenever the user asks to create, build, fix, or improve a Remotion video, animated scene, social media animation, motion design, kinetic typography, talking-head integration, scene pacing, or any motion-design work in a Remotion project. Also trigger when the user mentions scene components, animation timing, frame extraction, ease curves, or motion primitives. If you're about to write a Scene*.tsx file, read this skill first — the difference between a good and bad scene is in the approach, not the code. For re-editing existing footage into TikTok / Shorts / Reels short-form vertical with running captions and jump cuts, see the `tiktok-shorts-edit` skill instead.
