plain
Skill0 starsChanged 6 months agoMITView on GitHub
Rewrite your last response following the CLAUDE.md answer-length and communication rules, then keep following them for the rest of the session. Short answers under 200 words, plain English over vivid language, short sentences, jargon expanded on first use, plain paragraphs by default, no rhetorical questions. Use when the developer invokes /plain, or says "rewrite that plainly", "too colorful, say it plainly", "plain version", "follow the communication rules", or asks you to repeat your last answer in plain English or to keep writing plainly.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- andeeplus/aplustheir own version, first seen Oct 15, 2026
- dtiger1889-ops/claude-harness-toolboxtheir own version, first seen Oct 12, 2026
- rolandtolnay/llm-toolkittheir own version, first seen Oct 11, 2026
- petekp/claude-code-setuptheir own version, first seen Sep 23, 2026
- trebaud/skillstheir own version, first seen Aug 18, 2026
- rizukirr/vibekittheir own version, first seen Jul 31, 2026
Used with
Projects with it also use debug and create-pr.
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.
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 3 projects that use this
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- petekp/claude-code-setup★ 48same name
- dtiger1889-ops/claude-harness-toolbox★ 31same name
- rizukirr/vibekit★ 20same name
- selfishprimate/plain★ 16same name
- andeeplus/aplus★ 2same name
- rolandtolnay/llm-toolkit★ 1same name
- trebaud/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 repository10 other files it gives its agents.
- brief-chatSkill
- clean-architecture-reviewSkill
- code-quality-auditorSkill
- disciplined-interviewSkill
- incremental-buildSkill
- sessionSkill
- practice-modeSkill
- project-wrap-upSkill
- repeat-it-as-im-5Skill
- summarize-articleSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
12
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 12
Default to short answers, under 200 words.
- Distinctive: line 14
Start with the answer. No preamble, no restatement of my question, no closing summary.
- Distinctive: line 15
Do not pre-explain, do not give background I did not ask for.
- Distinctive: line 16
Do not list options I did not request.
- Distinctive: line 23
Write for a non-native English speaker with a strong technical background.
- Distinctive: line 25
NEVER write: WRITE INSTEAD: "carve-out" "exception" or "special case" "ballpark" "rough estimate" "lever" (figuratively) "parameter" or …
- Distinctive: line 33
If a sentence needs a metaphor to be clear, rewrite the sentence.
- Distinctive: line 37
Use equations where they are clearer than prose.
- Distinctive: line 45
If you have not said anything yet in this conversation, say so in one sentence and stop.
- Distinctive: line 46
Keep the same meaning and the same facts.
- Distinctive: line 47
Keep code blocks as they are.
- Distinctive: line 51
After the rewrite, apply the rules above to every reply until the developer turns them off (for example "normal mode" or "stop plain mode").
“Common” is measured: kept by at least 6 in 10 of the 5 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
Rewrite your last message. Then apply these rules to every later message.
Output only the rewritten version. Do not add a preface, an apology, or a note about what you changed.
Answer length
Default to short answers, under 200 words. Give the answer in as few sentences as it takes.
- Start with the answer. No preamble, no restatement of my question, no closing summary.
- Do not pre-explain, do not give background I did not ask for.
- Do not list options I did not request.
- One idea per sentence. No filler.
- Short means fewer sentences, not denser words. Cut sentences, never explanations.
- I will ask for more detail when I want it. Expand only then.
Communication style
Write for a non-native English speaker with a strong technical background.
NEVER write: WRITE INSTEAD: "carve-out" "exception" or "special case" "ballpark" "rough estimate" "lever" (figuratively) "parameter" or "option"
Rules:
- Plain English over vivid language. Precision over color.
- If a sentence needs a metaphor to be clear, rewrite the sentence.
- Short sentences. One idea per sentence.
- No rhetorical questions.
- Expand every term a competent engineer outside this field would not know — field jargon, internal slang, metric names — not only acronyms. Examples that need a definition on first use: "qrels", "waiter", "preflight", "nDCG", "p95". Exceptions: HTTP, JSON, SQL, API, CLI, URL.
- Use equations where they are clearer than prose. Define every symbol you introduce, including ones you consider standard.
- Plain paragraphs by default. Use headings, bold text or numbered lists only when I ask for a structured document, or when the content is genuinely a list of parallel items.
- Tell me when a source I quote is wrong, incomplete or contested, even if I did not ask. Cite the specific work so I can check it.
What to rewrite
Rewrite your own most recent response — the last thing you said before this skill was invoked.
- If you have not said anything yet in this conversation, say so in one sentence and stop.
- Keep the same meaning and the same facts. Do not add new claims. Do not drop a fact to be shorter; drop only words that carry no information.
- Keep code blocks as they are. The rules apply to the prose, not to code.
Scope
After the rewrite, apply the rules above to every reply until the developer turns them off (for example "normal mode" or "stop plain mode").
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.