Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Modularity Review Document Writer

A sub-skill that turns a Balanced Coupling modularity analysis into matching Markdown and HTML review documents.

Dev & CodingIntermediate★ 521⑂ 32AI score 6/10Last updated: Apr 4, 2026

What it does

  • Writes the final modularity review document once the analysis phase is done.
  • Enforces a fixed layout: header (scope/date) → 3–5 sentence executive summary → coupling overview table → per-issue sections → attribution footer.
  • Each issue is broken into Knowledge Leakage, Complexity Impact, Cascading Changes, and a Recommended Improvement (reduce strength / reduce distance / accept the imbalance) with explicit trade-offs.
  • Provides concrete Critical / Significant / Minor severity criteria.
  • Auto-links every coupling concept (integration strength, distance, volatility, DDD, connascence…) to coupling.dev in both output formats.
  • Emits .md and .html into docs/modularity-review/<date>/, generating HTML strictly from the bundled assets/template.html by replacing {{TITLE}} and {{CONTENT}}.

Who it's for

  • Architects and developers who need a written artifact from architecture reviews (monolith decomposition, service boundary redesign).
  • Teams applying Vlad Khononov's Balanced Coupling model to a real codebase.
  • Tech leads who want consistent report formatting and severity labeling.

Note: this is a sub-skill (user-invocable: false). The parent modularity analysis skill calls it as its final documentation step, so it isn't meant to be invoked alone.

Examples

  1. After analyzing coupling between the Payments and Orders services, it writes docs/modularity-review/2025-06-01/modularity-review.md with the overview table and issue sections.
  2. It also produces a styled HTML report (light/dark theme from the template) with identical content for stakeholder sharing.
  3. It classifies three imbalances as Critical/Significant/Minor and proposes an anti-corruption layer, co-location, or accepting the imbalance based on low volatility.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/vladikk/modularity/HEAD/skills/document/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/document folder from the GitHub repo vladikk/modularity into my ~/.claude/skills/document/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/vladikk/modularity.git && mkdir -p ~/.claude/skills && cp -r modularity/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository: git clone https://github.com/vladikk/modularity.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy everything over: cp -r modularity/skills/* ~/.claude/skills/
    • Copy the whole skills directory: this skill needs the parent analysis skill and the assets/template.html file.
  5. Restart Claude Code and open the project you want to review.
  6. Ask something like "run a modularity review on this repo" — this skill is invoked automatically at the write-up stage.
  7. Find the output under docs/modularity-review/<date>/ in your project.
View source on GitHub ↗License: NOASSERTION