Vertical Slice Architecture
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.
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 vertical-slice-architecturegit clone --depth 1 https://github.com/eralmansouri/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/vertical-slice-architecture ~/.claude/skills/vertical-slice-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Vertical Slice Architecture Decompose software around business capabilities, workflows, tasks, and explicit use cases. A vertical slice is a logical unit of change, not a mandatory folder layout, endpoint style, framework, or deployment. It may span UI, HTTP, workers, persistence, and message consumers. ## Add Or Change A Feature 1. Name the business intent with an action such as `PlaceOrder` or `DispatchShipment`. 2. Identify the capability that owns the behavior and affected state. 3. Classify the use case as a command, query, or workflow. 4. Define request and response contracts for this use case only. 5. Choose the simplest implementation that enforces its rules. 6. Place input validation, authorization, business rules, and orchestration deliberately. 7. Add pipeline steps only for demonstrated cross-cutting needs. 8. Handle cross-boundary effects through explicit APIs, commands, or events. 9. Co-locate the endpoint, contract, handler, validation, and slice-specific persistence. 10. Test behavior, persistence, and the externally visible contract at useful seams. ## Design Rules - Organize primarily by feature, not controllers, services, repositories, DTOs, or entities. - Keep implementation choices local. One slice can use direct SQL while another uses an aggregate. - Treat CQRS as separate command and query code paths. It does not require messaging, event sourcing, separate databases, or eventual consistency.
Details
- Skill name
vertical-slice-architecture- Repository
- eralmansouri/skills
- Path
skills/vertical-slice-architecture/SKILL.md- Repo updated
- 15 October 2026
FAQ
What does the Vertical Slice Architecture skill do?
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.
How do I install the Vertical Slice Architecture 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 Vertical Slice Architecture 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.
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
Service Boundaries
9eralmansouri/skills
Use for service boundaries, bounded capabilities, modular monoliths, microservices, monolith decomposition, data ownership, shared databases, API coupling, anti-corruption layers, and architecture topology decisions.
Xrpl Dev
5XRPL-Commons/xrpl-dev-skills
End-to-end XRPL development playbook. Covers XRP Ledger dApp development including project scaffolding (create-xrp), wallet integration (xrpl-connect), client SDKs, transactions, tokens, NFTs, DEX/AMM, cross-chain interoperability (Axelar), and security best practices.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.