System Decomposition

Break complex systems into bounded contexts with DDD. Map business capabilities to service boundaries, define ubiquitous language, assess cohesion/coupling. Use when refactoring monoliths or designing new architectures.

48 stars 10 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill system-decomposition
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/system-decomposition ~/.claude/skills/system-decomposition

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# System Decomposition

Systematically decompose complex systems using Domain-Driven Design: identify business capabilities, define bounded contexts, evaluate cohesion/coupling, design integration patterns.

## Context

You are decomposing a system into services or modules. Your role is to:

- Map business capabilities (not technical layers)
- Define bounded contexts with explicit boundaries
- Establish ubiquitous language (shared vocabulary per context)
- Assess cohesion (focus) and coupling (dependencies)
- Design integration patterns (sync API vs async events)

Good decomposition follows business domains, not technology layers. Anti-pattern: UserService, OrderService, PaymentService (implementation detail names) instead of Auth Realm, Commerce Hub, Payment Platform (domain names).

## Domain Context

Based on Eric Evans' _Domain-Driven Design_ and Sam Newman's _Building Microservices_:

- **Bounded Context**: Explicit boundary around business capability. Each context has its own domain model.
- **Ubiquitous Language**: Shared vocabulary within context (Order, Customer, Invoice). Prevents translation errors.
- **Aggregate**: Entity cluster within context. Single consistency boundary. Example: Order + OrderItems as one aggregate.
- **Integration**: How contexts communicate (Sync via API, Async via events, Shared database)
- **Cohesion**: Does everything in the context serve one purpose?
- **Coupling**: How many other services must it call?

## When to Use This Skill
Read the full skill on GitHub

Details

Skill name
system-decomposition
Path
architect/system-design/skills/system-decomposition/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the System Decomposition skill do?

Break complex systems into bounded contexts with DDD. Map business capabilities to service boundaries, define ubiquitous language, assess cohesion/coupling. Use when refactoring monoliths or designing new architectures.

How do I install the System Decomposition skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is System Decomposition popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.