← ClaudeAtlas

writing-stylelisted

Revise prose so it reads as though a person wrote it, without the tells that give an AI draft away. Use it whenever prose is about to leave your hands, not only when someone asks for it: PR descriptions and PR review comments, issue bodies, commit message bodies, README and documentation sections, design-doc prose, and the summary or explanation you are about to write back to the user. Also use it when someone asks to improve, humanize, clean up, tighten, or revise a draft, or says something sounds robotic or AI-written. Apply it proactively — the drafts that need it most are the ones nobody thought to ask about, and a repo can declare its own terms of art that generic advice would strip out. It is about how the prose reads, not what it says: it does not decide a document's content or supply what the document is missing.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh writing-style 2>&1 || true` When invoked directly with a draft: identify patterns below, revise, return the revised text. When producing prose: apply these patterns from the start rather than producing and then revising. ## The rules live in `rules.yaml` `skills/writing-style/rules.yaml` is the single authoritative source. Read it for the banned words, phrases, and frequency thresholds. It carries the terms and the reason for each, grouped by category. This file does not restate that list. It used to, and the copy drifted from the validator's copy, which is the divergence the rule source exists to end. `shirabe validate` reads the same file at enforcement time, so a rule added there reaches both you and the validator with no second edit. A repository can declare terms of art the rules must not fire on, through a `## Prose Vocabulary:` header in its CLAUDE.md. Honor a repository's declaration when you draft in it: shirabe declares `tier`, `journey`, and `underscore` because those are its own vocabulary, not tells. ## What the validator catches, and what it does not The mechanical rules are enforced before a reviewer sees the draft. Word matches, phrase matches, and em dash density are handled; you do not need to scan for them, and re-flagging them wastes the reader's attention. What no matcher reaches is the `judgment_only` section of the rule source, and it is where the value is: - **Low information density.** W