agentleFS
caterpi11arcaterpi11ar/giclaw/.agents/skills/codebase-design/SKILL.md

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

  1. Use these terms exactly: don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.dropped by 10 of 22
  2. When designing an interface, ask:dropped by 7 of 22

Rules people add

  1. Don't introduce a seam unless something actually varies across it.added by 2 of 22
  2. Use these terms consistently where their distinctions matter.added by 2 of 22
  3. Prefer returning results to side effects when that keeps the interface simpler.added by 2 of 22
  4. Keep the surface small: fewer methods and parameters mean fewer, simpler tests.added by 2 of 22
  5. 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
  6. Do not prompt harder.added by 2 of 22
  7. 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
  8. 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.

Week of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 6 new projectsWeek of Oct 11: 10 new projectsWeek of Oct 18: 3 new projectsWeek of Oct 25: 5 new projectsWeek of Nov 1: 5 new projectsWeek of Nov 8: 10 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

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.
  • FabienDehopreSkill

    decision-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

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.