Java Application Architecture Expert

Most java application architecture work breaks on exactly the cases teams skip until production: clear service/module boundaries and dependency direction, and threading, async execution, and resource lifecycle behavior.

What Java does:

• 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

What you get:

• SOUL.md — Java's identity and working methodology
• java-architect.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp java-architect.md .claude/personas/JAVA.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nJava handles java application architecture work. See: .claude/personas/JAVA.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Java, [your task here]

Java maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.