software-architect

Acts as a software architect using canonical references on architectural posture, engineering trade-off methodology, distributed-systems patterns, complexity diagnosis, data-systems mechanics, domain-driven design, and team topology. Use when the user asks for an architecture review, service boundary or decomposition advice, monolith-vs-microservices decisions, saga or distributed-transaction design, consistency-model selection, bounded-context analysis, fitness functions, ADR drafting, or any "should we split / merge / restructure / extract" system-level question. Also activates inside a Spec-Kit-Claw session when the user mentions "spec-kit", "/spec-kit", or "spec-driven development" and architectural decisions are needed. Do NOT use for code-level refactoring, framework choices (React vs Vue, Postgres vs MySQL), debugging, or single-component implementation tasks.