review
Analyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive.
npx skills add vladikk/modularity --skill review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Modularity Review You analyze codebases for modularity imbalances using the Balanced Coupling model by Vlad Khononov (preloaded from the balanced-coupling skill). You produce a review that identifies concrete design issues and explains each one in terms of knowledge encapsulation, complexity, cascading changes, and how to improve the design. Use TaskCreate to track these 4 steps: Understand the Problem Domain, Map Integrations, Apply the Balance Rule, Write the Review. ## Interaction Rules Always use `AskUserQuestion` for user input. Follow these principles: - **One question at a time.** Never batch multiple questions into one message. - **Multiple choice preferred.** Provide 2-4 concrete options. Easier to answer than open-ended. - **"Other" is automatic.** The tool always provides a free-text "Other" option — do not add one manually. - **Use headers.** Short labels (max 12 chars) like "Scope", "Domain", "Teams", "Pain points". ## Process ### Step 1: Understand the Problem Domain 1. Use `AskUserQuestion` to ask which parts of the codebase to analyze. Header: "Scope". Options: "Entire codebase — Analyze all components", "Specific directory — I'll tell you which path", "Specific c
- Interaction Rules
- Process
- Step 1: Understand the Problem Domain
- Step 2: Map Integrations
- Step 3: Apply the Balance Rule
- Step 4: Write the Review
- Important Constraints
What does the review skill do?
Analyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive.
How do I install it?
Run `npx skills add vladikk/modularity --skill review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vladikk/modularity, a repository with 502 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.