borghei/Claude-Skills / engineering/deep-module-design
deep-module-design
VerifiedDesign deep modules with small interfaces and rank shallow, pass-through or leaky code for deepening. Use when designing a module interface, improving codebase architecture, or making code easier to test.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.3 KB |
| assets/architecture-review-template.md | markdown | 1.9 KB |
| assets/interface-design-brief-template.md | markdown | 1.5 KB |
| assets/sample_codebase.json | config | 6.4 KB |
| assets/sample_designs.json | config | 3.1 KB |
| references/architecture-review-playbook.md | markdown | 7.2 KB |
| references/depth-principles.md | markdown | 9.5 KB |
| scripts/interface_compare.pyexecutable | script | 8.2 KB |
| scripts/module_depth.pyexecutable | script | 13.3 KB |
assets/architecture-review-template.md
View on GitHub# Architecture Review — <area or codebase>
**Reviewer:** <name> **Date:** YYYY-MM-DD **Commit:** <sha>
**Scope:** <paths reviewed and why: requester's pain point, or change-frequency hotspots>
**Inputs read:** glossary <yes/no>, decision records <list>, `module_depth.py` output <attached>
## Summary
<Two or three sentences: the main friction found and the top recommendation.>
## Candidates
### 1. <Concept name from the glossary> — Strong | Worth exploring | Speculative
| Field | Detail |
|-------|--------|
| Modules involved | `path/a.py`, `path/b.py` |
| Friction | <what is hard today; evidence: churn count, bug ids, duplicated rule locations> |
| Tool signals | depth <n>, pass-through <n>%, leaks <list>, changes <n> |
| Proposed deepening | <what merges; what becomes hidden; no signatures yet> |
| Leverage gain | <what callers will no longer need to know> |
| Locality gain | <which rule or change will live in one place> |
| Test impact | <tests that move to the new interface; tests that get deleted> |
| Conflicts with decisions | <none, or "contradicts DR-0007; worth reopening because …"> |
| Ranking (1–3 each) | change <n>, pain <n>, locality <n>, tests <n>, risk <n> = <total>/15 |
**Before**
```
caller -> ServiceA.get -> RepoA.get -> db
caller -> validate_x(); validate_y(); ServiceA.save -> RepoA.save -> db
```
**After**
```
caller -> Intake.place(draft) [validation, pricing, persistence, events hidden]
```
### 2. <Concept> — <strength>
<Same table and sketch.>
## Top recommendation
<Which candidate to tackle first and why — tie the reason to change frequency
and pain evidence, not to elegance.>
## Rejected or deferred
| Candidate | Reason | Record as decision? |
|-----------|--------|---------------------|
| | | yes / no |
## Next step
Pick one candidate. The review continues with interrogation and at least two
interface designs compared before any code changes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |