codebase-design
Skill9 starsChanged 29 days agoNo licenceView on GitHub
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
255 other projects use a version of this, 100 of them edited; 22 of 96 edited versions we compared changed its rules; 23 new projects in the last 4 weeks, against 17 the 4 before.
How people change it
22 of 96 edited versions changed its rules, and some changes recur.
Of the 96 edited versions we compared: 74 keep every rule, 22 made changes of their own.
Rules people drop
- Use these terms exactly: don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.dropped by 10 of 22
- When designing an interface, ask:dropped by 7 of 22
Rules people add
- Don't introduce a seam unless something actually varies across it.added by 2 of 22
- Use these terms consistently where their distinctions matter.added by 2 of 22
- Prefer returning results to side effects when that keeps the interface simpler.added by 2 of 22
- Keep the surface small: fewer methods and parameters mean fewer, simpler tests.added by 2 of 22
- Agents copy existing patterns, including bad ones. Write golden principles as opinionated, mechanical rules in the repository. Correct drift against them continuously with small, targeted refactors. …added by 2 of 22
- Do not prompt harder.added by 2 of 22
- Give one command family one default mode. Do not let some commands write by default while others only check. State the default mode, the paths written, and the side effects in help text.added by 2 of 22
- When applying this vocabulary to a design or review, report the recommended module, interface, and seam. In that design or review, explain how the result improves depth, leverage, locality, or testability. …added by 2 of 22
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: 23 new projects took it in the last 4 weeks, 1.4× the 4 weeks before.
Most recently taken up by
- bamlab/flashlightword for word, first seen Nov 16, 2026
- tunnckoCore/skillsedited, first seen Nov 16, 2026
- atiq-r/skillsedited, first seen Nov 16, 2026
- devdeepjs/kobayashi-maruedited, first seen Nov 16, 2026
- qelphybox/tg-mcpword for word, first seen Nov 16, 2026
- lhotwll217/owner-operatoredited, first seen Nov 16, 2026
Used with
Projects with it also use decision-mapping.
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.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
Other versions255 projects use a version of this.
Word for word · 132
- mattpocock/skills★ 325k100% same
- The-Vibe-Company/quivr★ 40k100% same
- QuivrHQ/quivr★ 40k100% same
- MODSetter/SurfSense★ 17k100% same
- formbricks/formbricks★ 13k100% same
- ArcReel/ArcReel★ 6.6k100% same
- withcoral/coral★ 5k100% same
- bamlab/flashlight★ 1.6k100% same
- epam/ketcher★ 939100% same
- moeru-ai/xsai★ 669100% same
122 more not listed
Edited · 100
- danny-avila/LibreChat★ 47k100% same
- LibreChat-AI/LibreChat★ 47k100% same
- windmill-labs/windmill★ 19k96% same
- GreyDGL/PentestGPT★ 16k100% same
- humanlayer/humanlayer★ 13k100% same
- openstatusHQ/openstatus★ 9.3k100% same
- vinvcn/mattpocock-skills-zh-CN★ 5.8k16% same
- bestofjs/bestofjs★ 3.1k100% same
- mdiri-ai/SoduWork★ 93094% same
- nodetool-ai/nodetool★ 63797% same
90 more not listed
Wrote their own version · 23
- stevesolun/ctx★ 583same name
- devcxl/mattpocock-skills-zh★ 543same name
- OyadotAI/oya-browser★ 349same name
- ahonn/dotfiles★ 62same name
- sgaabdu4/building-flutter-apps★ 25same name
- kriscard/Skills★ 15same name
- eralmansouri/skills★ 9same name
- imMamdouhaboammar/matts-skills-into-chatgpt★ 8same name
- Boom-Vitt/skills-thai★ 5same name
- KroxiDev/engineering-skills★ 4same name
13 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 repository60 other files it gives its agents.
- ask-mattSkill
- chief-of-staffSkill
- claude-handoffSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- giclaw-evolveSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- loop-meSkill
- migrate-to-shoehornSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill
- Battle Pass Rewards ClaimSkill
- Claim Achievement RewardsSkill
- Claim Event RewardsSkill
- Claim Mail RewardsSkill
- Collect ExpeditionsSkill
- Genshin Automation PitfallsSkill
- Genshin Impact BasicsSkill
- Genshin CharactersSkill
- Cloud Gaming ChromeSkill
- Genshin CombatSkill
- Genshin EventsSkill
- Genshin Inventory and GearSkill
- Genshin Interaction SafetySkill
- Genshin Map and ExplorationSkill
- Genshin Navigation and InputSkill
- Genshin Progression and ResinSkill
- Genshin QuestsSkill
- Genshin Reward ClaimingSkill
- Genshin Shop and SpendingSkill
- Genshin SocialSkill
- Genshin UI ScreensSkill
- Welkin Moon Daily ClaimSkill
The file
We split this skill into the rules it gives an agent
2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.
2
Common
Most of the 110 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 110 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.

