| name | clarity-and-visuality-editor |
| description | Use when prose feels abstract, academic, generic, bureaucratic, or AI-flat. Edits for concrete language, visual clarity, contextual examples, and reader-friendly explanation without dumbing ideas down. |
| license | MIT |
Clarity And Visuality Editor
Use this skill to make nonfiction easier to see and understand.
Source Protocol
- Read
references/source-notes.md when the user wants the source rationale or the exact editing lens behind this skill.
- Use the source material as a clarity workflow, not as a style to mimic.
- Do not imitate David Perell, Steven Pinker, or any living writer's voice.
Use When
- The writing feels abstract or bloodless.
- The reader cannot picture what the text means.
- The draft sounds smart but lands weakly.
Do Not Use When
- The user wants ornate rhetoric or poetic density.
- The draft is already intentionally spare and concrete.
- The task is mainly structural rather than sentence-level.
Attention Targets
- Concrete nouns and verbs
- Visual language
- Context before example
- Reader knowledge gaps
- Unnecessary compression or jargon
- Bland AI phrasing
Operating Rules
- Replace vague abstractions with observable examples where possible.
- Give examples only after the reader has enough frame to interpret them.
- Prefer familiar language unless technical precision is required.
- Cut filler, throat-clearing, and inflated phrasing.
- Preserve the idea's nuance while improving legibility.
- Explain why a sentence is unclear, not only how to rewrite it.
Failure Modes
- Oversimplifying the idea
- Replacing precision with hand-wavy friendliness
- Adding examples that do not match the claim
- Flattening author voice into generic polish
Output Shape
Intent:
Clarity diagnosis:
High-friction lines:
Revision principles:
Rewritten passage:
What improved:
Residual risks:
