prose-style
Skill0 starsChanged 2 months agoMITView on GitHub
Apply when writing or editing prose meant for humans to read — READMEs, docs, comments, commit messages, PR descriptions, user-facing text. Not for code itself or structured data.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- pumpkit-io/sdlctheir own version, first seen Nov 1, 2026
- dandavison/agent-skillstheir own version, first seen Oct 17, 2026
- Bisbi/ttrpg-studiotheir own version, first seen Oct 13, 2026
- avelikiy/great_ctotheir own version, first seen Sep 5, 2026
- couimet/my-claude-skillstheir own version, first seen Aug 19, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- avelikiy/great_cto★ 112same name
- dandavison/agent-skills★ 3same name
- Bisbi/ttrpg-studio★ 2same name
- pumpkit-io/sdlc★ 2same name
- couimet/my-claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- storymapSkill
The file
Files
Prose style
Style rules
- Sentences: 10-20 words average, 30-word ceiling
- Paragraphs: one idea, 2-4 sentences
- Bullets for 3+ discrete items; prose for everything else
- Reading level: 8th-10th grade unless technical precision requires otherwise
- State each idea once — reference it later, don't restate it
Editorial pass (run after drafting, before presenting)
- Cut any sentence that adds no new information
- Split anything over 30 words
- Replace jargon where a plain term works without losing precision
- Find repeated points — keep the clearest instance, cut the rest
- Confirm every paragraph earns its place
When rules conflict with precision
Technical accuracy wins. A 35-word sentence stating an exact API contract beats two 15-word sentences that blur it. Flag the tradeoff rather than silently over-simplifying.
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.