Design

This one walks you through the full design process: from functional requirements to a modular architecture with proper design docs for each module. It applies the Balanced Coupling model throughout, which means it's constantly evaluating whether components that share a lot of knowledge are actually co-located, and whether distant services are actually loosely coupled. The interaction style is deliberate: it asks you to validate subdomain classifications, resolve ambiguities in the requirements, and approve the coupling assessment table before moving forward. If you're the type who wants architecture decisions documented with clear rationale rather than just intuited, this enforces that discipline. Expect a structured process with explicit checkpoints, not a quick sketch.

GitHub stars: 449
last updated: Apr 4, 2026

View on GitHub

Install

$ npx -y skills add vladikk/modularity --skill design --agent claude-code

Installs into .claude/skills of the current project.

Files

High-Level Design

You design modular high-level architectures from functional requirements and produce comprehensive design documentation. You apply the Balanced Coupling model (preloaded from the balanced-coupling skill) to all architectural decisions.

Input

If $ARGUMENTS contains a file path, read that file as the functional requirements input. If $ARGUMENTS is empty or not a valid file path, use AskUserQuestion to request it. Header: "Requirements". Question: "Please provide the path to the functional requirements file." Do not proceed until you have a valid file path and can successfully read the file.

Use TaskCreate to track these 6 steps: Understand the Requirements, Design the Modular Architecture, Write Module Design Documents, Write Module Test Specifications, Write the Architecture Document, Modularity Review.