Microservices Architect
Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
Install
npx skills add theguysudo/ENZO --skill microservices-architectgit clone --depth 1 https://github.com/theguysudo/ENZO.git /tmp/ENZO
mkdir -p ~/.claude/skills
cp -r /tmp/ENZO/skills-bundled/microservices-architect ~/.claude/skills/microservices-architectPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Microservices Architect Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence. ## Core Workflow 1. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries. - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently. 2. **Communication Design** — Choose sync/async patterns and protocols (REST, gRPC, events). - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query/command pairs with sub-100 ms SLA use synchronous calls. 3. **Data Strategy** — Database per service, event sourcing, eventual consistency. - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts. 4. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks. - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path. 5. **Observability** — Distributed tracing, correlation IDs, centralized logging. - *Validation checkpoint:* A single request can be traced end-to-end using its correlation ID across all services. 6. **Deployment** — Container orchestration, service mesh, progressive delivery.
Details
- Skill name
microservices-architect- Repository
- theguysudo/ENZO
- Path
skills-bundled/microservices-architect/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
- Copies
- Found in 2 GitHub repos
FAQ
What does the Microservices Architect skill do?
Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
How do I install the Microservices Architect skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add theguysudo/ENZO --skill microservices-architect. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Microservices Architect popular?
It lives in theguysudo/ENZO, which has 121 GitHub stars and 29 forks.
Related skills
Angular Architect
121theguysudo/ENZO
Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.
API Designer
121theguysudo/ENZO
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
Architecture Designer
121theguysudo/ENZO
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
Nansen Binance Publisher
223NeverSight/learn-skills.dev
Automatically fetch multi-dimensional on-chain data using Nansen CLI, compile a comprehensive and beautifully formatted daily report, and publish it to Binance Square. Auto-run on messages like 'generate nansen daily report', 'post nansen daily to square', or when the user triggers the slash commands `/nansen` or `/post_square`.
Legacy Modernizer
121theguysudo/ENZO
Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.
Nestjs Expert
121theguysudo/ENZO
Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating TypeORM or Prisma, or working with .module.ts, .controller.ts, and .service.ts files. Invoke for guards, interceptors, pipes, validation, Swagger documentation, and unit/E2E testing in NestJS projects.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.