modularity
Code-level AI feedback misses where the costly mistakes hide: architecture.
Claude Code plugin for designing modular systems from functional requirements and reviewing existing codebases for modularity problems with actionable improvement recommendations. Based on the Balanced Coupling model.
- Analyze existing code for modularity problems and coupling issues
- Get actionable recommendations to improve system architecture
- Design modular systems from functional requirements upfront
Code-level AI feedback misses where the costly mistakes hide: architecture. This plugin reviews coupling imbalances at the component-boundary level (/modularity:review) and designs modular architectures from requirements (/modularity:design), tracing every recommendation to a concrete Balanced Coupling dimension — integration strength, distance, volatility — instead of gut feel.
Software architects and senior developers who want Claude to analyze and improve code modularity using formal coupling metrics.
https://github.com/vladikk/modularity
By vladikk
How to Get It
/plugin marketplace add vladikk/modularity /plugin install modularity@vladikk-modularity
After installing, paste this into Claude:
Help me analyze existing code for modularity problems and coupling issues
Trust Signals Auto-scanned
Community Pulse Active
Discussed on Hacker News, Reddit
- Mac Pros, Ara, and Modularity — Hacker News · 179 pts
- Modular monolith and microservices: Modularity is what matters — Hacker News · 148 pts
- Science Comparison: Virtuality vs Modularity — Reddit · 147 pts
3 mentions across 2 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 480 GitHub stars; 3 contributors; last commit 93d ago; license no license.
Things to check
- Effectiveness depends on the quality and completeness of functional requirements or codebase context provided. The Balanced Coupling model may not align with all architectural styles (e.g., event-driven, microservices-first).
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 480 GitHub stars; 3 contributors; last commit 93d ago; license no license.