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

Modular High-Level Design (Balanced Coupling)

Turns a functional requirements file into a coupling-balanced modular architecture plus per-module design docs, test specs, and an architecture overview.

Dev & CodingAdvanced★ 544⑂ 33AI score 8/10Last updated: Aug 31, 2026

What it does

  • Reads your functional requirements file, restates them, and asks targeted one-at-a-time questions to close gaps in domain classification, org structure, and integration style.
  • Classifies DDD subdomains (core/supporting/generic) to gauge volatility, then scores every integration on strength × distance × volatility using BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY, flagging distributed-monolith and big-ball-of-mud risks in a table.
  • Generates docs/design/<date>/ artifacts: per-module design.md (responsibilities, encapsulated knowledge, integration contracts, change vectors), per-module tests.md (unit, contract, boundary, behavior cases), and a global architecture.md.
  • Runs a self-review loop that keeps rebalancing the design until no Critical or Significant coupling issues remain.

Who it's for

  • Backend engineers, tech leads, and architects bootstrapping a new system's high-level design.
  • Anyone who needs defensible reasoning for microservice or module boundaries.
  • Teams that want module-level test specifications written before implementation starts.

Examples

  1. design docs/requirements/payments.md — approve the subdomain table and module map, then get a full design doc set generated.
  2. Before splitting a monolith, feed in the requirements and use the coupling table to spot high-strength/high-distance links, then redesign them as contract-based APIs.
  3. For modules owned by separate teams, surface imbalances caused by organizational distance and get concrete rebalancing actions in the review step.

· · · 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/design/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/design folder from the GitHub repo vladikk/modularity into my ~/.claude/skills/design/.
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 and go to a folder where you keep repos.
  2. Clone the repo: git clone https://github.com/vladikk/modularity.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skills: cp -r modularity/skills/* ~/.claude/skills/ (copy all of them — this skill relies on the companion balanced-coupling skill).
  5. In your project folder, start claude and confirm design appears in the skill list.
  6. Prepare a markdown file with your functional requirements, then invoke: design path/to/functional-requirements.md.
  7. Answer the multiple-choice questions and approve each step; output lands in docs/design/<date>/.
View source on GitHub ↗License: NOASSERTION