
Document
This produces the final output of a modularity analysis: a structured review document in both Markdown and HTML. It's not meant to be invoked directly. Instead, it's the last step after you've analyzed coupling in a codebase. The document includes an executive summary, a table of integrations scored by strength/distance/volatility, and detailed issue sections that explain knowledge leakage, complexity impact, and concrete improvement recommendations. Every coupling concept links back to coupling.dev for reference. The format is opinionated and follows Vlad Khononov's Balanced Coupling model strictly, right down to required footer attribution. If you're doing modularity reviews, this handles the writeup so you can focus on the analysis.
- GitHub stars
- 449
- last updated
- Apr 4, 2026
Install
$ npx -y skills add vladikk/modularity --skill document --agent claude-codeInstalls into .claude/skills of the current project.
Files
Document
You produce the final modularity review document in two formats: Markdown (.md) and HTML (.html). Both files contain identical content.
Document Structure
Header
# Modularity Review
**Scope**: [what was analyzed]
**Date**: [date]
Executive Summary
A short paragraph (3-5 sentences) covering:
- What the project does (its core functionality)
- The overall modularity status (healthy, needs attention, critical issues)
- The most important finding from the review
Coupling Overview Table
Summarize all key integrations. The table headers MUST link to coupling.dev:
Sponsors
Details
- Repository
- github.com/vladikk/modularity
- First seen
- Jun 11, 2026