technical-writing
Skill74 starsChanged 3 days agoLicence not identifiedView on GitHub
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
155 other projects use a version of this, 69 of them edited; 51 of 69 edited versions we compared changed its rules; 5 new projects in the last 4 weeks, against 3 the 4 before.
How people change it
51 of 69 edited versions changed its rules, and some changes recur.
Of the 69 edited versions we compared: 18 keep every rule, 51 made changes of their own.
Rules people drop
- Keep the small words that show structure, such as "that" in "Ensure that the switch is off". Never trade clarity for word count.dropped by 44 of 51
- Write so a tired engineer understands on the first read. Apply all four layers.dropped by 43 of 51
- Avoid "-ing" words where you can.dropped by 43 of 51
- Use the compass on a whole document or on one sentence.dropped by 23 of 51
- Put the condition before the instruction: "To delete the document, click Delete."dropped by 6 of 51
- Put the warning or condition before the step it guards: "If hot oil touches your skin, injuries can occur."dropped by 6 of 51
- Write procedures as direct commands, never as narration and never in the passive: "Install the component", not "the component must be installed".dropped by 6 of 51
- Call each thing by one name, everywhere. A doc that says "the gate", "the ratchet", and "the budget check" for one thing teaches three things. Don't churn what didn't change.dropped by 6 of 51
Rules people add
- Avoid "-ing" words where you can. They take too many grammatical jobs and breed misreadings.added by 39 of 51
- Keep the small words that show structure. "Ensure that the switch is off" keeps "that" because it makes the sentence parse one way. Never trade clarity for word count.added by 39 of 51
- Use the compass on a whole document or on one sentence. Reach for it whenever you feel unsure what you are writing. Gut feel is often wrong here.added by 19 of 51
- Read the awkward sentence aloud. If it stays awkward, rewrite it.added by 19 of 51
- Keep "only" and "not" next to the word they change.added by 2 of 51
- Write real paths. Make every count true at the commit that lands it.added by 2 of 51
- A rule we can't quote: its licence doesn't allow itadded by 2 of 51
- Follow the repository's formatting for code snippets. Write real paths. Make every count or tree claim true at the commit that lands it, and include the command that regenerates it.added by 2 of 51
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Rising: 5 new projects took it in the last 4 weeks, 1.7× the 4 weeks before.thin data
Most recently taken up by
- Scrapybara/agent-skillstheir own version, first seen Nov 16, 2026
- endalk200/skillsedited, first seen Nov 16, 2026
- 6cwb7sddvz-ai/Claude-Skillstheir own version, first seen Nov 16, 2026
- gfunc/skillsword for word, first seen Nov 16, 2026
- shiwenbin1617/pstackword for word, first seen Nov 16, 2026
- backnotprop/pstackword for word, first seen Nov 15, 2026
Used with
Projects with it also use poteto-help.
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.
shiwenbin1617Skillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 17 projects that use this
Other versions155 projects use a version of this.
Word for word · 11
- backnotprop/pstack★ 4.2k100% same
- moeru-ai/xsai★ 669100% same
- vtno/skills★ 35100% same
- adjohn/pstack★ 9100% same
- shiwenbin1617/pstack★ 4100% same
- conscientiousness/herdr-pstack-orchestrator★ 2100% same
- kwaa/skills★ 2100% same
- gfunc/skills★ 1100% same
- Tashila-109/tstack-skills★ 1100% same
- upamune/skills★ 1100% same
1 more not listed
Edited · 69
- jtaroreh/agystack★ 12870% same
- uzairansaruzi/p3-stack★ 12687% same
- dsebban/skills★ 7199% same
- korallis/agent-stack★ 4213% same
- painhardcore/pstack★ 22100% same
- creedants/pstack-t3★ 18100% same
- korallis/skills-collection★ 1470% same
- mariusflorescu/pstack-t3★ 1396% same
- Scino/fstack★ 1399% same
- caidanw/skills★ 1193% same
59 more not listed
Wrote their own version · 75
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- vercel/eve★ 5.9ksame name
- cashew-labs/libretto★ 911same name
- saffron-health/libretto★ 911same name
- proffesor-for-testing/agentic-qe★ 524same name
- NPC-Worldwide/npcsh★ 505same name
- openclaw/openclaw-enterprise★ 472same name
- Mindrally/skills★ 275same name
- luoling8192/technical-writing★ 211same name
65 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.
In this repository73 other files it gives its agents.
- algorithms/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-reachSkill
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- bklite-ops-product-designSkill
- blast-radiusSkill
- broSkill
- codebase-designSkill
- code-reviewSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- figure-it-outSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- howSkill
- implementSkill
- improve-codebase-architectureSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- no-commentsSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- recallSkill
- reflectSkill
- setup-matt-pocock-skillsSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 18 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 137 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 137 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.
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.

