nickcrew/microservices-patterns
skills/microservices-patterns/SKILL.md
Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication.
$ install --global
skillsauthnpx skillsauth add nickcrew/claude-cortex 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: Apr 7, 2026, 8:29 PM7.2s8 files scanned
SKILL.md
- name:
- microservices-patterns
- description:
- Comprehensive microservices architecture patterns covering service decomposition, communication, data management, and resilience strategies. Use when designing distributed systems, breaking down monoliths, or implementing service-to-service communication.
Microservices Architecture Patterns
Expert guidance for designing, implementing, and operating microservices architectures.
When to Use This Skill
- Breaking down monolithic applications into services
- Designing distributed systems from scratch
- Implementing service communication patterns (sync/async)
- Managing data consistency across services
- Building resilient distributed systems
- Defining service boundaries and API contracts
Core Principles
- Single Responsibility - Each service has one reason to change
- Independent Deployability - No coordination required for deployments
- Decentralized Data - Each service owns its data exclusively
- Design for Failure - Embrace failures, build resilience
- Automate Everything - Deployment, scaling, and recovery
Quick Reference
Load detailed patterns on-demand:
| Task | Load Reference |
| --- | --- |
| Define service boundaries and decompose monoliths | skills/microservices-patterns/references/service-decomposition.md |
| Implement service communication (sync/async) | skills/microservices-patterns/references/communication-patterns.md |
| Manage data consistency and transactions | skills/microservices-patterns/references/data-management.md |
| Build resilient systems (circuit breakers, retries) | skills/microservices-patterns/references/resilience-patterns.md |
| Add observability (tracing, logging, metrics) | skills/microservices-patterns/references/observability.md |
| Plan deployments and migrations | skills/microservices-patterns/references/deployment-migration.md |
Workflow
1. Understand Requirements
- Map business capabilities and domains
- Assess scalability/resilience needs
- Identify team boundaries
2. Define Service Boundaries
Load references/service-decomposition.md for:
- Business capability decomposition
- DDD bounded contexts
- Service boundary validation
3. Design Communication
Load references/communication-patterns.md for:
- Synchronous: API Gateway, REST, gRPC
- Asynchronous: Message Queue, Pub/Sub, Event Sourcing
4. Manage Data
Load references/data-management.md for:
- Database per service pattern
- Saga distributed transactions
- CQRS read/write optimization
5. Build Resilience
Load references/resilience-patterns.md for:
- Circuit breakers
- Retry with exponential backoff
- Bulkhead isolation
- Rate limiting and timeouts
6. Add Observability
Load references/observability.md for:
- Distributed tracing
- Centralized logging
- Metrics and monitoring
7. Plan Deployment
Load references/deployment-migration.md for:
- Blue-Green, Canary, Rolling deployments
- Strangler Fig migration pattern
Common Mistakes
- Distributed Monolith - Tightly coupled, must deploy together
- Shared Database - Multiple services accessing same database
- Chatty APIs - Excessive synchronous service calls
- Missing Circuit Breakers - No cascading failure protection
- No Observability - Deploying without tracing/logging/metrics
- Ignoring Network Failures - Assuming reliable network
- No API Versioning - Breaking changes without versioning
Fixes: Load relevant reference files for detailed solutions.
Resources
- Books: "Building Microservices" (Newman), "Microservices Patterns" (Richardson)
- Sites: microservices.io, martinfowler.com/microservices
- Tools: Kubernetes, Istio, Kafka, Kong, Jaeger, Prometheus
Related Skills
nickcrew/product-strategy
development
VerifiedTrustedCommunity
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/agent-loops
development
VerifiedTrustedCommunity
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/product-manager
development
VerifiedTrustedCommunity
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
13SKILL.mdUpdated Apr 7, 2026
nickcrew/playwright-cli
tools
VerifiedTrustedCommunity
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
13SKILL.mdUpdated Apr 7, 2026