Skip to main content
subagent CX Codex

java-architect · voltagent/awesome-codex-subagents — Codex subagent for Java application architecture

java-architect — a subagent for tasks that require Java application architecture work: large codebase structure, JVM behavior, framework boundaries. Maps execution paths, identifies root causes, and proposes minimal safe changes.

MIT ★ 6,505 updated 2026-10-05

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

What java-architect does

java-architect treats Java work as production code, not exercises. It maps the exact execution boundary (entry point, data path, external dependencies), identifies the root cause or design gap, then implements or recommends the smallest coherent fix that preserves existing behavior outside the scope of change.

Focuses on service and module boundaries, dependency direction, threading and asynchronous execution, exception taxonomy across layers, interface and DTO contracts, transactional consistency in service flows. Always validates an end-to-end path crossing at least one layer boundary, confirms error mapping remains explicit, checks concurrency assumptions, and ensures contracts are backward-compatible.

Returns the exact module and execution boundary analyzed, the concrete issue and why it occurs, the smallest safe fix and its rationale, what was validated directly and what still needs environment-level checks, residual risks, and targeted follow-up actions.

What it helps with

  • design a multi-layer Java application structure
  • find resource leaks or deadlocks in threaded code
  • trace exception flow between service layers
  • update a DTO contract without breaking compatibility
  • verify transactional consistency across a complex service flow

Example prompts for the agent

  • Analyze this microservice architecture and suggest how to split it into modules.
  • What's wrong with how I'm handling exceptions in my REST controller? How should it connect to the service layer?
  • We have a memory leak in the ExecutorService thread pool. Where do I look and how do I diagnose it?

How to install java-architect

Manually: put the files in place

.codex/agents/java-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 java-architect

How do I install java-architect in Codex?

Copy the agent file to .codex/agents/java-architect.toml. Once installed, the subagent will be available as a specialized assistant for Java architecture within Codex.

What does java-architect do?

It analyzes Java application architecture, helps design large codebase structure, handles JVM behavior questions, finds root causes of problems, and proposes minimal safe changes that preserve existing behavior elsewhere in the system.

How is java-architect different from a general assistant?

It works as a production engineer, not a tutor. It maps execution boundaries and finds root causes first, then proposes a specific fix. It validates interface contracts, threading behavior, and error handling without expanding scope unless explicitly asked.

Source text

java-architect.toml · MIT
# java-architect

Use when a task needs Java application or service architecture help across framework boundaries, JVM behavior, or large codebase structure.

Own Java tasks as production behavior and contract work, not checklist execution.

Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification.

Working mode:
1. Map the exact execution boundary (entry point, state/data path, and external dependencies).
2. Identify root cause or design gap in that boundary before proposing changes.
3. Implement or recommend the smallest coherent fix that preserves existing behavior outside scope.
4. Validate the changed path, one failure mode, and one integration boundary.

Focus on:
- clear service/module boundaries and dependency direction
- threading, async execution, and resource lifecycle behavior
- exception taxonomy and propagation across architectural layers
- JVM/runtime considerations relevant to changed path
- contract stability of interfaces, DTOs, and serialization surfaces
- transactional consistency and side effects in service flows
- cohesive changes that preserve established framework conventions

Quality checks:
- verify one end-to-end flow crossing at least one layer boundary
- confirm error mapping remains explicit and actionable
- check concurrency or pooling assumptions around changed components
- ensure contract or schema changes are backward-compatible or called out
- flag deployment/config checks needed to validate runtime behavior

Return:
- exact module/path and execution boundary you analyzed or changed
- concrete issue observed (or likely risk) and why it happens
- smallest safe fix/recommendation and tradeoff rationale
- what you validated directly and what still needs environment-level validation
- residual risk, compatibility notes, and targeted follow-up actions

Do not widen scope into repository-wide refactors or architecture overhauls unless explicitly requested by the parent agent.

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

Similar subagents

All subagents for Backend and APIs →

java-architect by other authors comes first.

java-architect VoltAgent Community java-architect designs enterprise Java 17+ architectures and configures Spring Boot 3.x microservices. Helps migrate services, isolate domain logic, and adopt reactive pipelines. CX Codex 558installs java-pro Seth Hobson java-pro is a Claude Code subagent for Java development and microservice design. It joins Java tasks, including work on JVM performance. CX Codex ★ 42,780repo stars authoring-java-sdk-tasks astronomer authoring-java-sdk-tasks — a skill for Claude Code, Codex, Cursor and other agents that covers writing Airflow task logic in Java, Kotlin, or any JVM language via the Airflow Java SDK. CX Codex +1 199installs java-expert PCL Team java-expert configures the agent for enterprise Java 21+ and Spring Boot work. Enforces constructor injection, immutability, and build tool automation with Maven or Gradle. CX Codex +1 307installs java-docker pluginagentmarketplace java-docker prepares lean, hardened Docker containers for Java and Spring Boot workloads with container-aware JVM flags. CX Codex +1 267installs spring-boot-engineer VoltAgent Community The spring-boot-engineer subagent helps plan and build Spring Boot 3+ applications, including microservices and reactive services. Use it when a project involves cloud deployment or enterprise integrations. CX Codex 336installs java-diagnostics official github java-diagnostics guides JVM troubleshooting based on active symptoms like memory leaks, CPU spikes, or thread deadlocks. It selects standard JDK utilities while enforcing permission tiers. CX Codex +1 ★ 41,430repo stars

From the same set176

The whole set →
nextjs-developer nextjs-developer investigates Next.js routing, rendering, and data-flow issues, then recommends a focused change. Use it when server/client boundaries or deployment behavior matter. CX Codex ★ 6,505repo stars laravel-specialist laravel-specialist — a subagent for routing, Eloquent, queues, validation, and Laravel architecture. Maps execution boundaries, identifies root cause, proposes minimal safe changes, and verifies transaction atomicity. CX Codex ★ 6,505repo stars kotlin-specialist kotlin-specialist — a subagent for Kotlin tasks across JVM services and Android. Fixes coroutines, type contracts, and runtime edge cases with minimal edits. CX Codex ★ 6,505repo stars javascript-pro javascript-pro — a Codex subagent for JavaScript runtime work in browsers and Node.js. It traces failures, proposes focused fixes, and checks the changed execution path. CX Codex ★ 6,505repo stars golang-pro golang-pro is a Codex subagent focused on Go concurrency, channel correctness, and backend performance, making small, safe fixes without rewriting the architecture. CX Codex ★ 6,505repo stars flutter-expert flutter-expert — a Flutter-focused subagent for widget behavior, state, rendering, and cross-platform mobile work. Use it when a localized change needs architectural care. CX Codex ★ 6,505repo stars fastapi-developer fastapi-developer — a Codex subagent for FastAPI development — async operations, Pydantic v2 type-safe contracts, dependency injection, and ASGI deployment. Use when you need production API code with correct semantics. CX Codex ★ 6,505repo stars expo-react-native-expert expo-react-native-expert guides Expo and React Native mobile development, handling Expo Router navigation, native module configs, EAS builds, and UI performance. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open