Skip to main content
subagent CX Codex

microservices-architect · voltagent/awesome-codex-subagents — Codex subagent for service architecture

microservices-architect maps service boundaries, contracts, and failure paths. Use it to review a distributed design or plan a change to service ownership.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/microservices-architect.toml
Open on GitHub

What microservices-architect does

The subagent maps responsibilities and dependencies in the affected domain, then looks for mismatched ownership, hidden coupling through shared database assumptions, and gaps in failure handling. It reviews API and event contracts, synchronous versus asynchronous communication, consistency guarantees, retries, and timeouts across service calls.

Its response summarizes the current design, ranks architecture risks, and recommends boundary or contract changes. For major boundary risks, it gives a safer alternative and considers migration order, deployment, and rollback. It does not recommend a broad topology change without evidence tied to current failures or scaling pain.

For Codex, place the agent file at .codex/agents/microservices-architect.toml.

What it helps with

  • find shared-schema assumptions that couple services
  • review API and event contracts between services
  • assess retries and timeouts across distributed flows
  • plan a service-boundary migration with rollback in mind

Example prompts for the agent

  • Map the service responsibilities in this domain and find coupling through shared database assumptions.
  • Review the contract between these services and suggest a safer option for the main boundary risk.
  • Analyze failure paths in this distributed flow, including migration order and rollback implications.

How to install microservices-architect

Manually: put the files in place

.codex/agents/microservices-architect.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about microservices-architect

How do I install microservices-architect in Codex?

Place the agent file at .codex/agents/microservices-architect.toml.

What does microservices-architect do?

It maps service responsibilities and dependencies, reviews contracts and consistency, and identifies failure-handling gaps. It then ranks risks and suggests changes with migration considerations.

Which risks does it check in a microservices design?

It looks for coupling through shared database or schema assumptions, boundary choices that can widen an incident, and deployment or rollback implications.

Source text

microservices-architect.toml · MIT
# microservices-architect

Use when a task needs service-boundary design, inter-service contract review, or distributed-system architecture decisions.

Treat microservice architecture as boundary, consistency, and failure-management design.

Working mode:
1. Map service responsibilities and dependency graph for the affected domain.
2. Identify ownership mismatches, coupling, and failure-path gaps.
3. Propose smallest architecture-safe adjustments with rollout impact.

Focus on:
- service ownership and responsibility boundaries
- API/event contract clarity between services
- synchronous vs asynchronous communication tradeoffs
- consistency guarantees and compensation behavior
- timeout/retry/circuit-breaker behavior in cross-service flows
- observability boundaries and correlation strategy across hops
- operational overhead introduced by additional service splits

Architecture checks:
- flag hidden coupling via shared DB/schema assumptions
- identify boundary choices that amplify incident blast radius
- distinguish immediate correctness risk vs structural debt
- call out where monolith-style coupling remains despite service split

Quality checks:
- provide at least one safer alternative for each major boundary risk
- include migration sequencing considerations for boundary changes
- surface deployment and rollback implications in distributed flows

Return:
- current distributed design summary in affected area
- prioritized architecture risks
- recommended boundary/contract changes
- migration and operational caveats

Do not recommend broad topology changes without clear evidence tied to current failure or scaling pain.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Backend and APIs →

microservices-architect by other authors comes first.

microservices-architect VoltAgent Community microservices-architect designs distributed architectures and breaks monoliths into independent microservices. Sets up communication patterns across services using gRPC, Kafka, and service meshes. CX Codex 376installs microservices-expert personamanagmentlayer microservices-expert — a skill for microservices architecture, service communication, and distributed workflows. Use it when a task involves service mesh, failure handling, or system design. CX Codex +1 181installs microservices-architecture aj-geddes microservices-architecture guides AI coding assistants through microservice design, service boundaries, and distributed messaging. Helps break apart monoliths into isolated services. CX Codex +1 530installs graphql-architect VoltAgent Community graphql-architect designs GraphQL schemas for microservices, federation, and distributed graphs. Use it when an API needs structured evolution or query analysis. CX Codex 1,038installs microservices-patterns Seth Hobson microservices-patterns — a practical guide to service boundaries, event-driven communication, data ownership, and resilience patterns for distributed systems. CX Codex +1 13,176installs architect-reviewer VoltAgent Community architect-reviewer evaluates system design decisions, architecture patterns, and tech stack choices at a macro level. Useful before large-scale refactoring or when designing new service boundaries. CX Codex 743installs backend-architect davila7 Turns the agent into a backend architect: service boundaries, API contracts, resilience, observability. Useful when the design decision comes before the code. CX Codex +1 501installs

From the same set176

The whole set →
websocket-engineer websocket-engineer handles WebSocket lifecycles, reconnect logic, message contracts, and state sync across unstable connections in Codex. CX Codex ★ 6,505repo stars ui-fixer The ui-fixer subagent applies small patches to reproduced UI bugs. Use it when the fix should stay close to the owning component and avoid unrelated refactoring. CX Codex ★ 6,505repo stars ui-designer ui-designer — a subagent that designs interfaces and interactions before coding. Delivers concrete recommendations on layout, component states, and accessibility—in a form ready to implement. CX Codex ★ 6,505repo stars mobile-developer The mobile-developer subagent for Codex implements and debugs mobile features amid device constraints, lifecycle transitions, and degraded network conditions. CX Codex ★ 6,505repo stars graphql-architect graphql-architect — a subagent that audits GraphQL schemas for architectural flaws, performance risks, and security gaps. Guides schema evolution, resolver design, and federation without breaking clients. CX Codex ★ 6,505repo stars fullstack-developer fullstack-developer handles bounded cross-layer features from user actions down to backend effects and UI updates. Useful when a single worker needs to own the full integration path. CX Codex ★ 6,505repo stars frontend-developer frontend-developer — a scoped subagent for frontend changes and UI bug fixes, with checks for state integrity, accessibility, and nearby regressions. CX Codex ★ 6,505repo stars electron-pro electron-pro — a subagent for Electron development: helps map responsibility across main, preload, and renderer processes, design IPC bridges, verify security boundaries, and validate packaging assumptions. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open