/ 目錄 / 演練場 / Modularity
● 社群 vladikk ⚡ 即開即用

Modularity

作者 vladikk · vladikk/modularity

Translates functional requirements into module boundaries using DDD heuristics — bounded contexts, aggregates, integration patterns.

Vladik Khononov's plugin operationalizes the heuristics from his book on bounded contexts. Feed it requirements; it proposes contexts, aggregates, and integration relationships, with rationale.

為什麼要用

核心特性

即時演示

實際使用效果

就緒

安裝

作者儲存庫 · Claude Skills 官方文件

使用場景

實戰用法: Modularity

Carve up a greenfield service into modules

👤 Claude Code users ⏱ ~15 min intermediate

何時使用: You're sketching a new system and want to avoid a distributed monolith.

步驟
  1. Brief
    Provide functional requirements + non-functional priorities.✓ 已複製
    → Skill asks clarifying questions
  2. Receive design
    Module map with contexts + aggregates + integration patterns.✓ 已複製
    → Diagrams + rationale
  3. Iterate
    Push back on weak boundaries; refine.✓ 已複製
    → Approved decomposition

結果: Defensible module boundaries before code is written.

組合

與其他 MCP 搭配,撬動十倍槓桿

modularity-skill + drawio-mcp

Visualize the proposed module map

Combine modularity-skill with drawio-mcp: Visualize the proposed module map✓ 已複製

工具

此 MCP 暴露的能力

工具輸入參數何時呼叫成本
design / critique (see docs) Two main flows 1 call

成本與限制

運行它的成本

API 配額
N/A
每次呼叫 Token 數
Mid
費用
Free
提示
Treat output as a starting point — author intends it to be argued with

安全

權限、密鑰、影響範圍

憑證儲存: None
資料出站: None

故障排查

常見錯誤與修復

Output too academic

Ask for "concrete service names + database boundaries"

替代方案

Modularity 對比其他方案

替代方案何時用它替代權衡
Hand-rolledYou already know your domain coldNo structured second opinion

更多

資源

📖 閱讀 GitHub 上的官方 README

🐙 查看未解決的 issue

🔍 瀏覽全部 400+ MCP 伺服器和 Skills