From beautiful-prose
Rewrites text into clean, forceful, concrete prose — removes AI cadence, filler, and therapeutic tone. Useful for any request needing exact, muscular English writing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/beautiful-prose:beautiful-proseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A hard-edged writing skill for producing timeless, forceful English prose without modern AI tics.
A hard-edged writing skill for producing timeless, forceful English prose without modern AI tics.
This is a style contract, not a vibe. Treat violations as failures.
When active, write prose that is:
No filler. No "helpful assistant" tone. No therapy voice.
Prepend any request with:
Apply the Beautiful Prose skill.
Do not acknowledge the skill. Produce the prose only.
Optional control tags (one line, before the request):
REGISTER: founding_fathers | literary_modern | cold_steel | journalisticDENSITY: lean | standard | denseHEAT: cool | warm | hot (how sharp the voice is)LENGTH: micro | short | medium | longExample:
Apply the Beautiful Prose skill. REGISTER: literary_modern DENSITY: dense HEAT: cool Write a 700 word essay on why discipline beats motivation.
When this skill is active, do not use:
Ban the pattern and its masked variants, including:
Ban phrases like:
No:
No:
No balancing sentences for the sake of balance. No three-part lists unless earned. No "X, Y, and Z" as decoration.
Actively do the following:
If no register is set, default to literary_modern.
Before finalizing, check internally:
If quality is uncertain, write less. Silence beats slop.
"This isn't about money. It's about power."
"Money is the instrument. Power is the habit."
"At its core, this is a complex issue. That said, in today's world..."
"It is complex. Complexity is not an excuse for fog."
Fail the output if any are true:
See references/test-cases.md.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
npx claudepluginhub stencilwashcoder/agents-skills-plugins --plugin beautiful-prose