https://topaiskills.com/tags/codebase-design/Recent content in Codebase Design on Top AI SkillsHugoenSat, 22 Aug 2026 00:00:00 +0000https://topaiskills.com/skills/general/codebase-design/Sat, 22 Aug 2026 00:00:00 +0000https://topaiskills.com/skills/general/codebase-design/<p>Most &ldquo;design&rdquo; skills tell an agent to write cleaner code. Matt Pocock&rsquo;s Codebase Design skill instead hands it a fixed vocabulary — module, interface, depth, seam, adapter — and forbids substitutions. I pulled the SKILL.md from the <a href="https://github.com/mattpocock/skills" rel="nofollow" target="_blank">mattpocock/skills</a> repo (228K stars, same family as <a href="https://topaiskills.com/skills/general/code-review/">code-review</a> and <a href="https://topaiskills.com/skills/general/handoff/">handoff</a>) and the strict glossary is the whole trick: you can&rsquo;t design a boundary if &quot;boundary&quot; means three different things.</p> <h2 id="the-vocabulary-precision-is-the-feature">The Vocabulary: Precision Is the Feature</h2> <p>The skill defines <strong>module</strong> as anything with an interface and an implementation — deliberately scale-agnostic: a function, class, package, or tier-spanning slice qualifies. <strong>Interface</strong> means everything a caller must know to use it correctly: the type signature, plus invariants, ordering constraints, error modes, config, and performance characteristics. <strong>Depth</strong> is leverage at the interface: how much behavior a caller or test can exercise per unit of interface they must learn.</p>