Modularity Skills
Skill
Architecture design, coupling review, and documentation skills grounded in Vlad Khononov's Balanced Coupling model.
By Vlad Khononov · Packaged for Pi by Vedang Manerikar · git:github.com/vedang/modularity · View source
What it does
Modularity Skills gives the agent a concrete analytical model for software boundaries instead of vague advice about 'low coupling.' It evaluates every dependency across three dimensions—integration strength (intrusive, functional, model, contract), distance, and domain volatility—using the formula BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY.
The package includes four skills: /skill:design for decomposing systems into modules with clean contracts, /skill:review for auditing existing codebases for coupling leaks and cascading changes, /skill:balanced-coupling as the core reference framework, and /skill:document for writing architecture docs and diagrams.
When to reach for it
Invocation: Run /skill:design, /skill:review, /skill:balanced-coupling, or /skill:document, or ask the agent to evaluate module boundaries.
- Designing a new service or component
- Use /skill:design to place boundaries around volatile business logic and keep cross-module contracts narrow.
- Auditing a painful module or PR
- Use /skill:review to pinpoint where high integration strength meets large distance across volatile code.
What it adds
- Four architecture skills: design, review, balanced-coupling, and document.
- Step-by-step diagnosis for coupling strength, connascence, boundary distance, and volatility.
Commands: /skill:design, /skill:review, /skill:balanced-coupling, /skill:document
How it fits
- Shaping Skills — After shaping a feature's requirements and breadboard, use Modularity to check that the component boundaries stay balanced.
- ADR — Document boundary choices and coupling tradeoffs in an ADR once the design settles.
Good to know
- Strong coupling is not always bad—co-locating closely related, high-volatility logic inside one module (low distance) is often healthier than splitting it across chatty services.
Source and setup
- Loaded via
git:github.com/vedang/modularity- Attribution
- By Vlad Khononov · Packaged for Pi by Vedang Manerikar