prose-principles
Skill1 starsChanged 39 days agoMITView on GitHub
Sentence-level prose rules for words to replace, filler to cut, and weak constructions to fix. Use when writing or reviewing any prose.
In this repository38 other files it gives its agents.
- agent-conductSkill
- bugfixSkill
- code-smellsSkill
- deliverSkill
- final-responseSkill
- frontend-designSkill
- go-conventionsSkill
- go-implementorSkill
- go-reviewerSkill
- go-test-strengthSkill
- implementation-principlesSkill
- nextflow-conventionsSkill
- nextflow-implementorSkill
- nextflow-reviewerSkill
- nextjs-fastapi-conventionsSkill
- nextjs-fastapi-implementorSkill
- nextjs-fastapi-reviewerSkill
- orchestratorSkill
- phase-creatorSkill
- phase-reviewerSkill
- pr-resolverSkill
- pr-reviewerSkill
- python-conventionsSkill
- python-implementorSkill
- python-reviewerSkill
- spec-authorSkill
- spec-proofreaderSkill
- spec-reviewerSkill
- spec-writerSkill
- subagentsSkill
- swift-conventionsSkill
- swift-implementorSkill
- swift-reviewerSkill
- testing-principlesSkill
- tightenSkill
- unslopSkill
- verificationSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Write "is" or "has".
- Distinctive: line 56
Forced counts: Use the natural number of items, not three.
- Distinctive: line 60
Read the draft once more. For each sentence, ask whether it names something concrete, and whether the reader would act differently without …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prose Principles
Rules for the sentences themselves, whatever the container. unslop applies these to a Markdown file and adds document mechanics. final-response applies them to a chat turn and adds what a response owes its reader. writing-for-agents covers a different axis: the structure of a document an agent acts on.
Core Rule
Name the mechanism, the number, or the action. A sentence that would read the same in another project's document says nothing about this one: cut it, or replace it with the concrete fact.
Words To Replace
- AI vocabulary. additionally, comprehensive, crucial, delve, enhance, intricate, leverage, robust, seamless, showcase, underscore, utilize. Use the plain word: "use", not "utilize"; "help", not "facilitate"; "many", not "numerous".
- Fancy ways to say "is". "serves as", "stands as", "boasts", "features". Write "is" or "has".
- Filler. "in order to" is "to". "due to the fact that" is "because". "in the event that" is "if". "it is important to note that" is nothing.
- Hedge stacks. "could potentially possibly" is "may". Keep one calibrated qualifier.
- Abstract metaphor nouns. substrate, wedge, vector, nexus, bedrock, flywheel, north star, endgame, plus "ratchet", "scaffolding", and "surface" used as metaphors. Pick the concrete word: "base", "add", "way", "the last phase". A word used literally is fine, so the agent harness in this repo is a real thing rather than a metaphor.
- Puffery. "pivotal", "testament to", "evolving landscape", "setting the stage for", and "production-ready" or "best practice" with no evidence behind them. State what happened or what was measured.
Constructions To Avoid
- Superficial -ing clauses. "...highlighting the need for", "...ensuring reliability". Delete them, or name the mechanism that follows.
- Formulaic contrast. "not just X, but Y". "Despite challenges, X continues to thrive." State the point directly.
- Passive voice with a hidden actor. "queries are validated" becomes "the compiler validates queries". Passive is fine when the actor is unknown or beside the point.
- An adverb propping up a weak verb. "significantly improves" is the measured delta. "runs quickly" is the number.
- Dense sentences. One idea per sentence. If the reader has to backtrack to parse it, split it.
- Synonym cycling. Pick one name for a thing and repeat it. Three names teach three things.
- Forced counts. Use the natural number of items, not three.
Check
Read the draft once more. For each sentence, ask whether it names something concrete, and whether the reader would act differently without it. If neither holds, cut it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

