writing

name	writing
description	Use when writing or rewriting prose such as documentation, landing-page copy, release notes, blog posts, emails, memos, proposals, prompts, or UI text. Produces direct, specific writing with clear structure. Avoids filler, hype, generic transitions, self-reference, and stock "AI" phrasing.

Writing

Write for the reader's job, not for the sentence.

When To Use This Skill

Use this skill when the task is primarily about prose:

• writing from scratch
• rewriting for clarity or tone
• tightening existing copy
• adapting a draft to a specific audience or format
• removing generic or "AI-sounding" language

Do not use this skill when the task is mainly factual research, code changes, or rote formatting.

Default Style

• Lead with the point. Do not warm up.
• Prefer concrete nouns and verbs over abstractions.
• Use short sentences when the idea is simple.
• Use longer sentences only when they carry real structure or contrast.
• Make one claim at a time.
• Cut anything that sounds like commentary about the writing itself.
• If a statement can be tested, write it so it can be checked.

Hard Rules

• Do not write filler openings such as "In today's fast-paced world," "It's important to note," or "Whether you're X or Y."
• Do not use hype words unless the user explicitly wants that tone.
• Do not describe prose as "engaging," "compelling," "impactful," "seamless," "robust," or "innovative" unless the subject itself is those things and you can show why.
• Do not use self-conscious meta language like "natural voice," "human-centered," or "AI writing tropes" inside the output.
• Do not pad with summary sentences that repeat the previous paragraph in softer words.
• Do not use symmetrical list flourishes unless the content is genuinely parallel.

Words And Patterns To Avoid By Default

Avoid these unless the domain truly requires them:

• delve
• leverage
• unlock
• robust
• seamless
• landscape
• powerful
• transformative
• cutting-edge
• thoughtfully crafted
• in order to
• it is worth noting
• in conclusion
• this means that
• not only X, but Y
• whether you are

Workflow

1. Identify the document type, audience, and required action.
2. Decide what the reader should know, feel, or do after reading.
3. Write the strongest opening sentence first.
4. Build only the structure the piece needs.
5. Replace abstractions with specifics.
6. Cut repeated ideas, hedges, and ornamental transitions.
7. Read once for rhythm and once for precision.

By Format

Documentation

• Prioritize correctness, sequence, and edge conditions.
• Prefer direct instructions over explanation-heavy framing.
• Use examples only when they remove ambiguity.
• State prerequisites and failure cases plainly.

Product Or Marketing Copy

• Focus on the user's problem, the product action, and the concrete payoff.
• Show what changes after using the product.
• Keep claims narrow enough to feel true.
• One sharp line beats three soft ones.

Release Notes

• Start with what changed.
• Separate added behavior, changed behavior, and fixes.
• Cut promotional language.
• Mention breaking changes early.

Memos, Proposals, And Internal Writing

• State the decision, recommendation, or problem in the first paragraph.
• Surface constraints and tradeoffs directly.
• Use headings only when they help scanning.
• End with the next action or open question.

UI Text

• Keep labels short.
• Make actions explicit.
• Error messages should say what failed and what to do next.
• Empty states should explain the missing state, not just decorate it.

Editing Pass

When revising, look for:

• an opening that starts too far from the point
• nouns that hide the actor or action
• repeated claims stated in slightly different words
• transitions that announce logic instead of carrying it
• adjectives doing the job of evidence
• paragraphs that should be bullets
• bullets that should be one sentence

Replacement Heuristics

• Replace "This platform enables teams to..." with the concrete action.
• Replace "robust support for" with the actual capability.
• Replace "seamless experience" with what friction was removed.
• Replace "powerful tools" with the tool names or outcomes.
• Replace "users can easily" with the action itself unless ease is being compared.

Final Check

Before finishing, ask:

• Is the point visible in the first lines?
• Can a skeptical reader tell what is actually being claimed?
• Did I remove every sentence that exists only to sound polished?
• Does the piece sound like someone who knows the subject and respects the reader's time?