skills.rest
lamb92009
lamb92009COMMUNITY
Explore all skills by this author →
GitHub

microservices-architect

Identify service boundaries and architecture patterns for distributed systems.

Updated Feb 11, 2026
Search Tags:#architecture#microservices#observability#service-mesh#domain-driven-design#saga#event-sourcing
One-click install
npx skills add https://github.com/lamb92009/claude-skills --skill microservices-architect-lamb92009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: microservices-architect
Source: https://github.com/lamb92009/claude-skills/tree/main/microservices-architect
Command: npx skills add https://github.com/lamb92009/claude-skills --skill microservices-architect-lamb92009

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps architecture teams design distributed systems, decompose monoliths, and implement robust microservices patterns, providing clear boundary definitions and guidance for resilience and observability.

Core Features & Use Cases

  • Domain-driven design for service boundaries and bounded contexts
  • Pattern guidance for resilience (circuit breakers, bulkheads, retries) and service mesh setup
  • Event-driven patterns (Saga, Event Sourcing, CQRS) and data ownership strategies
  • Observability, deployment considerations, and governance for cloud-native architectures

Quick Start

Provide a comprehensive microservices design plan for an existing monolith, including bounded contexts, data ownership, recommended tech stack, and a high-level migration path.

Frequently Asked Questions about microservices-architect

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

FAQPage Schema
How do I define service boundaries when decomposing a monolith?▼

Event-driven patterns like Saga and Event Sourcing manage distributed transactions and state reconstruction. CQRS separates read models from write operations, providing specific guidance for implementing resilient event-driven microservices architectures.

What is the best way to handle data ownership in a microservices architecture?▼

Service mesh setup handles resilience patterns like circuit breakers, bulkheads, and retries. This configuration provides network-level fault tolerance and traffic management to guide robust cloud-native deployments without modifying application code.

How do I implement observability and tracing for distributed systems?▼

This microservices architecture design suits cloud-native deployments and monolith decompositions across multiple teams. It provides specific guidance for distributed systems requiring bounded contexts, event-driven patterns, and service mesh implementation.

When do I need a saga pattern for microservices?▼

The saga pattern is needed for managing distributed transactions across multiple service boundaries in event-driven architectures. It provides a sequence of local transactions to maintain data consistency without two-phase commits.

Related Skills

Explore More Software Engineering Skills→
LLM-Dev-OpsLLM-Dev-Ops
1

V3 DDD Architecture

Decompose monolithic orchestrators into bounded contexts with Domain-Driven Design.

Official
Advanced
camelranchentertainmentcamelranchentertainment
1

microservices-architect

Design microservice boundaries and resilience patterns for distributed systems.

Community
Advanced
duanbiao2000duanbiao2000
3

service-mesh-observability

Implement observability stacks for Istio and Linkerd meshes with tracing and metrics.

Community
Advanced
KentoShimizuKentoShimizu
7

architecture-monolith

Define modular monolith module boundaries and contracts within a single deployable unit.

Community
Advanced