microservices-architect

Name: microservices-architect
Availability: InStock
Author: belokonm

Design scalable microservices architectures with service decomposition and mesh implementation.

8|11|Updated Feb 15, 2026

Search Tags:#architecture #microservices #resilience #service-mesh #distributed-systems #api-gateway #service-decomposition

Ready to run

npx skills add https://github.com/belokonm/claude-supercode-skills --skill microservices-architect-belokonm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microservices-architect
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/microservices-architect-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill microservices-architect-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams struggle to design scalable and reliable microservices ecosystems, leading to fragmented boundaries and operational complexity.

Core Features & Use Cases

Service decomposition guidance for transforming monoliths into bounded contexts.
Inter-service communication patterns and service mesh recommendations (Istio/Linkerd).
Best practices for resilience, data ownership, deployment strategies, and API gateways.

Quick Start

Provide a high-level microservices decomposition plan for a given system.

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 bounded contexts?▼

Microservices decomposition starts by mapping domain boundaries into bounded contexts to define service responsibilities and data ownership. This approach guides the transition from a monolith by establishing clear service boundaries and independent data management for each service.

What communication patterns should I use for distributed systems?▼

Distributed systems communication patterns depend on your resilience requirements, selecting between synchronous and asynchronous interactions. Implementation involves configuring an API gateway for external requests and establishing internal service-to-service communication protocols that ensure reliability.

When do I need a service mesh for microservices architecture?▼

A service mesh is needed when managing complex microservices architectures requiring advanced traffic control and resilience patterns like circuit breakers and retries. It abstracts inter-service communication to provide consistent observability and reliability across your distributed system.

How do I implement resilience patterns like circuit breakers in microservices?▼

Resilience patterns like circuit breakers and retries are implemented within your microservices architecture to prevent cascading failures across distributed systems. These patterns cut off faulty service calls and automatically retry transient failures to maintain system stability.

How do I design an API gateway strategy for microservices?▼

API gateway strategy design involves creating a single entry point for external clients to route requests to underlying microservices. It handles cross-cutting concerns like authentication, rate limiting, and request aggregation before forwarding traffic to your distributed system.