Menu
Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Active token optimization and context efficiency specialist. ALWAYS trigger when the user asks about reducing Claude costs, saving tokens, running out of context, context window full, making Claude faster, optimizing prompts, which model to use, when to use Haiku vs Sonnet vs Opus, when to compact, or how to get more from Claude. Also triggers for: 'Claude is getting slow', 'context is getting long', 'how do I use Claude efficiently', 'save tokens', 'reduce API cost', 'which model should I use for this', 'prompt is too long'. Works alongside token-tracker for cost monitoring.
Token usage tracking and cost monitoring specialist. ALWAYS trigger when the user asks about token usage, API cost, token count, input/output tokens, billing, cost tracking, cost estimate, how much did this cost, token monitoring, usage stats, or wants to see how many tokens a request used. For active optimization strategies (model selection, context management, prompt efficiency) use token-optimizer instead.
CTO-level engineering leadership advisor. Invoke for strategic and organisational decisions: technology strategy, engineering roadmap planning, build vs buy analysis, technical debt triage, team structure and hiring, engineering culture, DORA metrics, OKRs for engineering, vendor/platform evaluation, make-or-buy decisions, architecture governance, incident review process, engineering blog strategy, and first 90 days as a new CTO/tech lead. NOT for writing code — for implementation use the relevant stack skill.
Platform engineering and SRE specialist. Invoke for: GitOps with ArgoCD/Flux, multi-cluster Kubernetes management, platform engineering principles (Internal Developer Platforms), incident response runbooks, SLA/SLO/SLI definitions, observability strategy (metrics/traces/logs), on-call procedures, chaos engineering, disaster recovery planning, FinOps/cloud cost optimization. For standard Docker/CI/CD pipeline setup use devops-cicd instead.
Advanced Flutter architecture specialist. Use for Flutter architecture decisions, NOT standard Flutter implementation (use flutter-dev for that). Invoke for: Flutter clean architecture, feature-first project structure, advanced Riverpod patterns (Notifier/AsyncNotifier/family), advanced Bloc (Cubit vs Bloc tradeoffs, BlocObserver), Flutter performance profiling (DevTools, shader compilation, jank), custom RenderObject, platform channels/MethodChannel, multi-module monorepo, Flutter plugin authoring, isolates/compute(), build_runner code generation, get_it/injectable DI, Flutter 3.x upgrade migrations.
Use when building Laravel 11+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
| name | microservices-architect |
| description | Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing. |
| license | MIT |
| metadata | {"author":"https://github.com/Jeffallan","version":"1.0.0","domain":"api-architecture","triggers":"microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing","role":"architect","scope":"system-design","output-format":"architecture","related-skills":"devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert"} |
Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.
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.
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 |
When designing microservices architecture, provide:
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
