Skill

microservices-patterns

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing micros...

npx claudepluginhub absjaded/antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Supporting Assets

resources/implementation-playbook.md

SKILL.md

Similar Skills

finishing-a-development-branch

174.6k

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

systematic-debugging

174.6k

Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.

10 files

superpowers

writing-plans

174.6k

Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.

1 file

superpowers

Stats

Stars0

Forks0

Last CommitFeb 27, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

Microservices Patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Use this skill when

Decomposing monoliths into microservices

Designing service boundaries and contracts

Implementing inter-service communication

Managing distributed data and transactions

Building resilient distributed systems

Implementing service discovery and load balancing

Designing event-driven architectures

Do not use this skill when

The system is small enough for a modular monolith

You need a quick prototype without distributed complexity

There is no operational support for distributed systems

Instructions

Identify domain boundaries and ownership for each service.

Define contracts, data ownership, and communication patterns.

Plan resilience, observability, and deployment strategy.

Provide migration steps and operational guardrails.

Resources

resources/implementation-playbook.md for detailed patterns and examples.