skills.rest
enigmaicon-eng
enigmaicon-engCOMMUNITY
Explore all skills by this author →
GitHub

microservices-architect

Designs microservices architectures with bounded contexts, communication, resilience, and observability specifications.

1|Updated May 16, 2026
Search Tags:#microservices#domain-driven design#distributed tracing#resilience patterns#service boundaries#event sourcing#sagas
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill microservices-architect-enigmaicon-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-architect
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-skills/skills/microservices-architect
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill microservices-architect-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid brittle distributed systems by guiding how to design microservices with clear boundaries, safe communication, and production-ready reliability patterns.

Core Features & Use Cases

  • Domain decomposition & service boundaries: Use DDD bounded contexts to decide what belongs in each service and how responsibilities are split.
  • Communication & data strategy: Choose sync vs async patterns and enforce database-per-service ownership with consistency boundaries (including event sourcing and CQRS where appropriate).
  • Resilience & observability: Apply timeouts, retries, circuit breakers, bulkheads, correlation IDs, and distributed tracing so you can detect and recover from failures quickly.
  • Production deployment guidance: Define health/readiness probes and recommend progressive delivery approaches for safe rollout.

Quick Start

Use this skill to design a microservices architecture for a bounded-context decomposition and produce the communication, data ownership, resilience, and observability blueprint for each service.

Frequently Asked Questions about microservices-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a monolith into microservices using domain-driven design?▼

Microservices decomposition uses domain-driven design bounded contexts to split monolithic domains into separate services, defining clear responsibility boundaries and service ownership for each decomposed component.

How do I implement the saga pattern for distributed transactions across microservices?▼

Saga patterns coordinate distributed transactions across microservices through asynchronous event workflows, replacing two-phase commits with compensating events to maintain data consistency across separate service boundaries.

What is the best way to design resilience patterns like circuit breakers and retries for microservices?▼

Resilience patterns for microservices require explicitly specifying timeout, retry, and circuit-breaker behaviors per service interaction, alongside bulkheads to isolate failures and prevent cascading system outages.

How does distributed tracing work with correlation IDs in a microservices architecture?▼

Distributed tracing in microservices relies on correlation ID propagation across service calls, aligning tracing, metrics, and logging outputs to trace requests end-to-end through the distributed system.

When should I use event sourcing and CQRS in microservices data ownership?▼

Event sourcing and CQRS apply to microservices when enforcing database-per-service ownership requires append-only event logs for state changes and separate read models to query materialized views.

Can I use this approach for planning microservices deployment readiness and health probes?▼

Microservices deployment readiness planning defines health and readiness probes for each service and recommends progressive delivery approaches to ensure safe production rollouts and traffic routing.

Related Skills

Explore More Software Engineering Skills→
wesleyegbertowesleyegberto
3

microservices-architect

Define service boundaries for distributed systems using domain-driven design.

Community
Advanced
ArogyaReddyArogyaReddy

linkerd-patterns

Automate Linkerd service mesh deployment and configuration on Kubernetes.

Community
Advanced
MovchanetsMovchanets

backend-architect

Design scalable backend architectures and API strategies for distributed systems.

Community
Advanced
MatheusrlrMatheusrlr
1

nestjs-modular-monolith

Design NestJS modular monolith architectures with DDD, Clean Architecture, and CQRS patterns.

Community
Advanced