Document
Produces modularity review documents in both Markdown and HTML formats.
Install
npx skills add vladikk/modularity --skill document -g -a claude-code -y- Repository
- vladikk/modularity576
- Category
- Writing
- Updated
- 2mo ago
- License
- See repository
- Context cost
- Mediumabout 2,614 tokens
- Runs scripts
- No, instructions only
What it does
Produces modularity review documents in both Markdown and HTML formats. Use when writing the final review output from a modularity analysis.
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:
| Integration | [Strength](https://coupling.dev/posts/dimensions-of-coupling/integration-strength/) | [Distance](https://coupling.dev/posts/dimensions-of-coupling/distance/) | [Volatility](https://coupling.dev/posts/dimensions-of-coupling/volatility/) | [Balanced?](https://coupling.dev/posts/core-concepts/balance/) |
| ----------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------- |
| A -> B | ... | ... | ... | ... |
Issues
For each identified imbalance, write a section:
## Issue: [Short descriptive title]
**Integration**: [Component A] -> [Component B]
**Severity**: [Critical / Significant / Minor]
### Knowledge Leakage
