Angular Application Architecture Expert

Most angular application architecture work breaks on exactly the cases teams skip until production: component boundary design and input/output contract clarity, and signals, RxJS streams, and change-detection correctness under async updates.

What Angular does:

• component boundary design and input/output contract clarity
• signals, RxJS streams, and change-detection correctness under async updates
• dependency-injection scope and provider lifetime consistency
• router configuration, guards, resolvers, and lazy-load boundaries
• template performance hot paths and unnecessary re-render pressure
• form validation flow (reactive/template-driven) and error UX consistency
• keeping changes aligned with established Angular workspace conventions

What you get:

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

Install:

# 1. Place in your project
cp angular-architect.md .claude/personas/ANGULAR.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nAngular handles angular application architecture work. See: .claude/personas/ANGULAR.md" >> CLAUDE.md

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

Angular 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.