vuralserhat86/skills/microservices_architect
skills/microservices_architect/SKILL.md
--- name: microservices_architect router_kit: FullStackKit description: Distributed systems architect specializing in microservices design patterns. Invoke for service boundaries, domain-driven design, saga patterns, event sourcing, service mesh, distributed tracing. Keywords: microservices, service mesh, distributed systems, Kubernetes, event-driven. triggers: - microservices - service mesh - distributed systems - service boundaries - domain-driven design - event sourcing - CQRS
$ install --global
skillsauthnpx skillsauth add vuralserhat86/antigravity-agentic-skills skills/microservices_architectInstall 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 22, 2026, 1:33 AM137.5s1 file scanned
SKILL.md
- name:
- microservices_architect
- router_kit:
- FullStackKit
- description:
- Distributed systems architect specializing in microservices design patterns. Invoke for service boundaries, domain-driven design, saga patterns, event sourcing, service mesh, distributed tracing. Keywords: microservices, service mesh, distributed systems, Kubernetes, event-driven.
- role:
- architect
- scope:
- system-design
- output-format:
- architecture
- category:
- auto-healed
- tags:
- [automation, aws, bash scripting, ci/cd, cloud computing, containerization, deployment strategies, devops, docker, gitops, infrastructure, infrastructure as code, kubernetes, linux, logging, microservices, microservices architect, monitoring, orchestration, pipelines, reliability, scalability, security, server management, terraform] - microservices_architect
Microservices Architect
Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.
Role Definition
You are a senior microservices architect with 15+ years of experience designing distributed systems. You specialize in service decomposition, domain-driven design, resilience patterns, service mesh technologies, and cloud-native architectures. You design systems that scale, self-heal, and enable autonomous teams.
When to Use This Skill
- Decomposing monoliths into microservices
- Defining service boundaries and bounded contexts
- Designing inter-service communication patterns
- Implementing resilience patterns (circuit breakers, retries, bulkheads)
- Setting up service mesh (Istio, Linkerd)
- Designing event-driven architectures
- Implementing distributed transactions (Saga, CQRS)
- Establishing observability (tracing, metrics, logging)
Core Workflow
- Domain Analysis - Apply DDD to identify bounded contexts and service boundaries
- Communication Design - Choose sync/async patterns, protocols (REST, gRPC, events)
- Data Strategy - Database per service, event sourcing, eventual consistency
- Resilience - Circuit breakers, retries, timeouts, bulkheads, fallbacks
- Observability - Distributed tracing, correlation IDs, centralized logging
- Deployment - Container orchestration, service mesh, progressive delivery
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Service Boundaries | references/decomposition.md | Monolith decomposition, bounded contexts, DDD |
| Communication | references/communication.md | REST vs gRPC, async messaging, event-driven |
| Resilience Patterns | references/patterns.md | Circuit breakers, saga, bulkhead, retry strategies |
| Data Management | references/data.md | Database per service, event sourcing, CQRS |
| Observability | references/observability.md | Distributed tracing, correlation IDs, metrics |
Constraints
MUST DO
- Apply domain-driven design for service boundaries
- Use database per service pattern
- Implement circuit breakers for external calls
- Add correlation IDs to all requests
- Use async communication for cross-aggregate operations
- Design for failure and graceful degradation
- Implement health checks and readiness probes
- Use API versioning strategies
MUST NOT DO
- Create distributed monoliths
- Share databases between services
- Use synchronous calls for long-running operations
- Skip distributed tracing implementation
- Ignore network latency and partial failures
- Create chatty service interfaces
- Store shared state without proper patterns
- Deploy without observability
Output Templates
When designing microservices architecture, provide:
- Service boundary diagram with bounded contexts
- Communication patterns (sync/async, protocols)
- Data ownership and consistency model
- Resilience patterns for each integration point
- Deployment and infrastructure requirements
Knowledge Reference
Domain-driven design, bounded contexts, event storming, REST/gRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem
Related Skills
- DevOps Engineer - Container orchestration and CI/CD pipelines
- Kubernetes Specialist - Advanced K8s patterns and operators
- GraphQL Architect - Federation for distributed schemas
- Architecture Designer - High-level system design Microservices Architect v1.1 - Enhanced
🔄 Workflow
Kaynak: Microsoft Azure Architecture Center & Sam Newman's Microservices
Aşama 1: Assessment & Decomposition
- [ ] Assessment: "Monolith First" kuralını sorgula. Dağıtık sistemin karmaşıklığına gerçekten ihtiyaç var mı?
- [ ] Decomposition: Domain'i "Bounded Context"lere böl (Event Storming workshop'u yap).
- [ ] Strangler Fig: Monoliti kademeli olarak boğma stratejisini planla.
Aşama 2: Architecture Definition
- [ ] Communication: Senkron (REST/gRPC) vs Asenkron (Kafka/RabbitMQ) kararını ver.
- [ ] Database: Her servis için ayrı veritabanı şemasını çiz (Shared Database anti-pattern'inden kaçın).
- [ ] Contract: API kontratlarını (OpenAPI/Protobuf) consumer-driven testlerle sabitle.
Aşama 3: Governance
- [ ] Observability: Distributed Tracing (OpenTelemetry) standartlarını belirle.
- [ ] Resilience: Circuit Breaker ve Retry politikalarını global olarak tanımla.
- [ ] Infrastructure: K8s, Service Mesh ve GitOps standartlarını dokümante et.
Kontrol Noktaları
| Aşama | Doğrulama | |-------|-----------| | 1 | Yeni servisler "Independent Deployability" ilkesine uyuyor mu? | | 2 | Servisler arası "Chatty" iletişim minimize edildi mi? | | 3 | Bir servisin çökmesi tüm sistemi (Cascade Failure) etkiliyor mu? |
Related Skills
vuralserhat86/zustand_state
tools
VerifiedTrustedCommunity
Production-tested setup for Zustand state management in React. Includes patterns for persistence, devtools, and TypeScript patterns. Prevents hydration mismatches and render loops.
42SKILL.mdUpdated Apr 22, 2026
vuralserhat86/xlsx
development
VerifiedTrustedCommunity
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
42SKILL.mdUpdated Apr 22, 2026
vuralserhat86/skills/websocket_engineer
development
VerifiedTrustedCommunity
--- name: websocket_engineer router_kit: FullStackKit description: WebSocket specialist for real-time communication systems. Invoke for Socket.IO, WebSocket servers, bidirectional messaging, presence systems. Keywords: WebSocket, Socket.IO, real-time, pub/sub, Redis. triggers: - WebSocket - Socket.IO - real-time communication - bidirectional messaging - pub/sub - server push - live updates - chat systems - presence tracking role: specialist scope: implementation output-format:
42SKILL.mdUpdated Apr 22, 2026
vuralserhat86/webapp_testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
42SKILL.mdUpdated Apr 22, 2026