Service Boundaries
Use for service boundaries, bounded capabilities, modular monoliths, microservices, monolith decomposition, data ownership, shared databases, API coupling, anti-corruption layers, and architecture topology decisions.
Install
/plugin marketplace add eralmansouri/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add eralmansouri/skills --skill service-boundariesgit clone --depth 1 https://github.com/eralmansouri/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/service-boundaries ~/.claude/skills/service-boundariesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Service Boundaries Design logical ownership before physical topology. A service is the authority over a cohesive set of business capabilities and the data needed to perform them. Repositories, containers, processes, and databases do not prove that a useful boundary exists. ## Decision Workflow 1. Name the measurable outcome: release autonomy, failure isolation, security, throughput, team ownership, or cost. 2. Map business capabilities, workflows, language, rules, state transitions, and authoritative decisions. 3. Identify candidate boundaries by cohesion, lifecycle, ownership, and reasons to change. 4. Verify that commands can usually be decided with locally owned data. 5. Map dependencies in both directions and classify their coupling. 6. Test whether a monolith plus ordinary scaling solves the stated constraint. 7. Price distribution: latency, partial failure, contracts, deployment, observability, consistency, and support. 8. Choose monolith, modular monolith, services, or a hybrid per capability. 9. Extract only a boundary with a concrete beneficiary and sufficiently stable ownership. 10. Record the context, alternatives, consequences, and triggers for reconsideration. ## Boundary Rules - Start with behavior and business decisions, not tables or entity nouns. - One logical owner controls each state transition and authoritative write. - Ownership includes meaning, rules, lifecycle, behavior, and supporting data.
Details
- Skill name
service-boundaries- Repository
- eralmansouri/skills
- Path
skills/service-boundaries/SKILL.md- Repo updated
- 15 October 2026
FAQ
What does the Service Boundaries skill do?
Use for service boundaries, bounded capabilities, modular monoliths, microservices, monolith decomposition, data ownership, shared databases, API coupling, anti-corruption layers, and architecture topology decisions.
How do I install the Service Boundaries skill?
Claude Code plugin: /plugin marketplace add eralmansouri/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Service Boundaries popular?
It lives in eralmansouri/skills, which has 9 GitHub stars and 2 forks.
Related skills
Codebase Design
9eralmansouri/skills
Use for code-level module design, deep modules, interfaces, seams, adapters, testability, refactoring shallow modules, and finding architecture improvements in an existing codebase.
Design Review
9eralmansouri/skills
Design review of a codebase area, branch, or PR. Maps its bounded contexts, vertical slices, and modules, then judges where rules live and whether flexibility sits where change actually happens. Use when the user asks for a design or architecture review, or when a review should judge structure rather than bugs or style.
Domain Driven Design
9eralmansouri/skills
Use for domain-driven design, domain modeling, ubiquitous language, bounded contexts, aggregates, invariants, entities, value objects, domain services, domain events, and deciding whether a rich domain model is warranted.
Vertical Slice Architecture
9eralmansouri/skills
Use for vertical slice architecture, feature folders, task-based APIs and UI, CQRS commands and queries, handlers, request pipelines, controller design, code structure, cohesion, and feature-level testing.
Run Debugger
9duvoai/skills
Investigate why a Duvo Run failed or produced the wrong outcome. Use when the user shares a failed Run, asks "why did this Run fail", or wants to fix a recurring failure on an Agent. Reads the Run's transcript and the Build that was active for it via the Duvo public API, names the root cause from a fixed failure-mode taxonomy, and proposes one concrete fix — handing off to aop-writer for any AOP rewrite.
Workflow Debugger
9duvoai/skills
Audit a Duvo Agent — or a multi-Agent workflow connected by a Queue — across many Runs to find systemic inefficiencies and quality issues, then recommend concrete AOP and architecture changes. Use when the user asks to "analyze this workflow", "audit my Agent", "why is this Agent slow / inconsistent / low quality across runs", "why does my queue keep backing up", or wants a health check over an Agent's recent Runs — as opposed to debugging one failed Run (that's run-debugger). Reads recent Runs, eval scores, the producer/consumer queue topology, and the AOPs those Runs actually ran against via
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.