microservice-architect

Design and document microservices architectures with decomposition and communication patterns.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/MUmerRazzaq/fast-next-todo --skill microservice-architect-mumerrazzaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microservice-architect
Source: https://github.com/MUmerRazzaq/fast-next-todo/tree/main/.claude/skills/microservice-architect
Command: npx skills add https://github.com/MUmerRazzaq/fast-next-todo --skill microservice-architect-mumerrazzaq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill guides developers and architects in planning, designing, and modeling microservices architectures effectively, addressing the complexity of distributed systems.

Core Features & Use Cases

  • System Decomposition: Assists in identifying service boundaries using DDD principles, suitable for building modular systems.
  • Communication Planning: Helps select appropriate interaction patterns like REST, gRPC, or messaging for efficient service integration.
  • Data & Infrastructure Planning: Aids in choosing data management strategies and infrastructure components such as service discovery and API gateways.
  • Architecture Documentation: Supports creating architecture diagrams (C4 model) and formal service contracts for clear API communication.

Quick Start

Use this Skill to draft a microservices architecture plan for your new e-commerce platform, including service definitions, communication patterns, and infrastructure setup.

Frequently Asked Questions about microservice-architect

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

FAQPage Schema
How do I design a microservices architecture for a scalable e-commerce platform?

Designing a microservices architecture involves decomposing your e-commerce platform into modular services using DDD principles, selecting communication patterns like REST or messaging, and setting up infrastructure components such as API gateways to ensure scalable and maintainable distributed systems.

What is the best way to define service boundaries in a distributed system?

Defining service boundaries in a distributed system is best achieved by applying Domain-Driven Design principles to identify cohesive business capabilities, ensuring your microservices architecture remains modular, loosely coupled, and independently scalable.

How do I choose between REST, gRPC, and messaging for microservices communication?

Choosing between REST, gRPC, and messaging for microservices communication requires evaluating your integration patterns for efficient service interaction, balancing synchronous needs against asynchronous event-driven workflows based on specific data and infrastructure requirements.

Can I generate C4 model architecture diagrams and formal API contracts for my system?

You can generate C4 model architecture diagrams and formal service contracts to document clear API communication, ensuring your microservices architecture is comprehensively planned and aligned with distributed system best practices.

Do I need to plan data management strategies before decomposing my monolithic application?

Planning data management strategies is essential before decomposing a monolithic application, as selecting appropriate data ownership and consistency models ensures your microservices remain loosely coupled and maintainable.

What infrastructure components are required for a maintainable microservices architecture?

Required infrastructure components for a maintainable microservices architecture include service discovery and API gateways, which manage service integration and routing while supporting scalable distributed system operations.