# Codebase Design · JRichlen

> Before writing a new interface (module boundary, class API, function signature, or service contract) that at least two call sites will depend on, that crosses a module/service/team/persistence boundary, or that will be expensive to change later — produce 3+ radically different candidate designs and compare them on depth, locality, and seam placement before picking one. Use on "before committing to an interface", "design this API/module/class boundary", "how should this be structured", "compare i

## Facts
- Page: https://tashan.sh/capability/plugin-jrichlen-agent-plugins-codebase-design
- tashan id: plugin:jrichlen/agent-plugins/codebase-design
- Source: https://github.com/JRichlen/agent-plugins
- Type: plugin
- Category: other
- tashan score: 39.0 / 100
- Adoption: 7.0
- Upkeep: 79.0
- Freshness: 93.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: MIT
- Official: no

## Install

```sh
/plugin marketplace add JRichlen/agent-plugins
/plugin install codebase-design@jrichlen
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-09-13 by tashan (https://tashan.sh) from public evidence. Scorer s5.