microservice-design-skill

Generate a Confluence-ready Microservice Architecture section from a solution description.

Updated Mar 2, 2026

Search Tags:#architecture #ddd #kubernetes #observability #containers #service-mesh #microservice

Ready to run

npx skills add https://github.com/dacy/architect-skill --skill microservice-design-skill

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines creating a complete, opinionated Microservice Architecture section for a Solution Intent or standalone service decomposition, ensuring consistent boundaries, data ownership, and deployment practices across teams.

Core Features & Use Cases

Decompose a system into bounded contexts mapped to services aligned with DDD principles.
Enforce 12-Factor App principles, service mesh patterns, and independent data stores.
Produce a Confluence-ready Markdown section including topology, data ownership, resilience, and deployment guidance.
Use cases: architecting a multi-service platform (for example, an e-commerce solution with catalog, cart, and orders) or migrating from a monolith to a distributed set of services.

Quick Start

Generate a complete Microservice Architecture section by applying the enterprise standards to your solution description

Frequently Asked Questions about microservice-design-skill

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

FAQPage Schema

How do I design a microservice architecture aligned with DDD principles?▼

To design a microservice architecture, you decompose a system into bounded contexts mapped to services. This ensures consistent service boundaries, data ownership, and deployment practices aligned with Domain-Driven Design and enterprise standards.

What is the best way to define service boundaries and data ownership for distributed systems?▼

Defining service boundaries and data ownership requires identifying bounded contexts from your solution description and enforcing independent data stores. This approach codifies deployment constraints and keeps distributed services decoupled.

How do I generate Confluence-ready documentation for microservice topology and resilience?▼

You generate Confluence-ready Markdown documentation by applying enterprise microservice standards to your solution. The output includes topology, data ownership, resilience patterns, and deployment guidance for your architecture section.

Can I use this approach to migrate from a monolith to a service mesh and Kubernetes deployment?▼

Yes, you can migrate from a monolith to a distributed set of services on Kubernetes. The design process applies 12-Factor App principles, service mesh patterns, and highlights potential anti-patterns with remediation guidance.

What are common microservice anti-patterns and how do I remediate them?▼

Common microservice anti-patterns are identified by evaluating your design against enterprise standards. The process highlights these misalignments and provides specific remediation guidance to keep your architecture aligned with best practices.

When should I not use a microservice architecture for my application?▼

You should reconsider a microservice architecture if your system cannot be cleanly decomposed into bounded contexts or if independent data stores create excessive operational overhead. The design process highlights potential anti-patterns to help evaluate this fit.