abmbodj/microservices-patterns
.github/skills/microservices-patterns/SKILL.md
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
development
Updated Mar 29, 2026
$ install --global
skillsauthnpx skillsauth add abmbodj/riven-mobile microservices-patternsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 6:13 PM36.4s2 files scanned
SKILL.md
- name:
- microservices-patterns
- description:
- Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
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.mdfor detailed patterns and examples.
Related Skills
abmbodj/zustand-store-ts
development
VerifiedTrustedCommunity
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
SKILL.mdUpdated Mar 29, 2026
abmbodj/zoom-automation
tools
VerifiedTrustedCommunity
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
SKILL.mdUpdated Mar 29, 2026
abmbodj/zoho-crm-automation
tools
VerifiedTrustedCommunity
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
SKILL.mdUpdated Mar 29, 2026
abmbodj/zendesk-automation
tools
VerifiedTrustedCommunity
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
SKILL.mdUpdated Mar 29, 2026