Individual skill
microservices-boundary-definer
Applies Domain-Driven Design (DDD) bounded contexts and event storming to decompose monoliths into clean services.
skills/development/microservices-boundary-definer/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 607 bytesSKILL.mdcore · 1,842 bytesexamples/example.mddoc · 947 bytes
Read excerpt
## Purpose
Define high-cohesion, low-coupling service boundaries using Domain-Driven Design (DDD) strategic design principles, avoiding distributed monolith anti-patterns and chatty network coupling.
## When to Use
- Planning the extraction of services from a monolithic codebase.
- Splitting a team or scaling engineering throughput across organizational boundaries (Conway's Law).
- Correcting overly granular nanoservices that require distributed transactions.
## What to Analyze
1. **Domain Entities & Aggregates**: Group data that must maintain transactional consistency within a single boundary.
2. **Ubiquitous Language**: Identify terms that mean different things in different contexts (e.g. `Account` in Billing vs `Account` in Auth).