prose
Skill3 starsChanged 5 days agoApache-2.0View on GitHub
Write prose a person reads short and plain, with precise names, by Orwell's six rules. Use for the text of every reply, commit messages, issue and PR bodies, docs and comments.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- VladButacu/agentkittheir own version, first seen Nov 15, 2026
- sanmidable/skillstheir own version, first seen Nov 8, 2026
- krkn-s/ai-workspacetheir own version, first seen Nov 1, 2026
- bym6dn6zv5-gif/skillstheir own version, first seen Nov 1, 2026
- raphaelsalaja/skillstheir own version, first seen Nov 1, 2026
- robmclarty/fascicletheir own version, first seen Oct 31, 2026
Used with
Projects with it also use design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- cloudflare/computer★ 9.9ksame name
- tokio-rs/topcoat★ 6.4ksame name
- tokio-rs/toasty★ 3.3ksame name
- static-web-server/static-web-server★ 2.4ksame name
- cohen-liel/hivemind★ 108same name
- simota/agent-skills★ 99same name
- raphaelsalaja/skills★ 67same name
- robmclarty/fascicle★ 4same name
- sanmidable/skills★ 2same name
- bym6dn6zv5-gif/skills★ 1same name
6 more not listed
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.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
11
Distinctive
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 13
Keep answers short and concise: the direct answer first, in a few sentences.
- Distinctive: line 15
If something important doesn't fit, offer to expand in one line instead of including it.
- Distinctive: line 16
Do not omit critical information, but prefer brevity.
- Distinctive: line 17
Use the real name for things: the code identifier, the user's own words, or a concise description or appositive.
- Distinctive: line 18
Avoid nonce terms, and avoid cataphors with unclear antecedents or referents.
- Distinctive: line 19
Don't say "it", "that", and similar words unless the referent is obvious.
- Distinctive: line 25
Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
- Distinctive: line 26
Never use a long word where a short one will do.
- Distinctive: line 27
If it is possible to cut a word out, always cut it out.
- Distinctive: line 28
Never use the passive where you can use the active.
- Distinctive: line 29
Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prose
Writing guidelines for prose a person will read: responses, docs, READMEs, PR descriptions, commit messages and comments. Short, plain answers with precise names, following Orwell's six rules.
Response Style
- Answer in plain language, like one person talking to another.
- Keep answers short and concise: the direct answer first, in a few sentences.
- Skip background, caveats, and long lists unless the user asks for more detail.
- If something important doesn't fit, offer to expand in one line instead of including it.
- Do not omit critical information, but prefer brevity.
- Use the real name for things: the code identifier, the user's own words, or a concise description or appositive. Don't make up labels like "the switch-back note".
- Avoid nonce terms, and avoid cataphors with unclear antecedents or referents.
- Don't say "it", "that", and similar words unless the referent is obvious. Prefer precision.
Orwell's Rules for Writing
From George Orwell, "Politics and the English Language" (1946):
- Never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
- Never use a long word where a short one will do.
- If it is possible to cut a word out, always cut it out.
- Never use the passive where you can use the active.
- Never use a foreign phrase, a scientific word, or a jargon word if you can think of an everyday English equivalent.
- Break any of these rules sooner than say anything outright barbarous.
<!-- Adapted from humanlayer/skills@701b6bcb, plugins/rpi/skills/rpi/references/prose.md. Copyright (c) 2026 HumanLayer, MIT License; see ../LICENSE-humanlayer. -->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.

