architect

Architecture Decision Records are generated by automating architectural decision making and documentation. The process captures context, options, and tradeoffs to produce clear artifacts that reduce ambiguity and accelerate handoffs across frontend, backend, and security teams.

System design and API contracts are outlined by defining high-level components, relationships, data flows, endpoints, data models, and interface boundaries. This establishes consistent governance and clear architectural artifacts during the planning, design, and hand-off phases.

You need to initiate a design session with requirements describing the target system's scale and constraints. Providing these inputs allows the system to generate accurate ADRs and a comprehensive system design outline tailored to your project.

Interface boundaries for frontend, backend, and security teams are defined by generating API contracts and data models. This enables consistent governance across multiple teams by satisfying requirements for clear API specifications and architectural artifacts.

Automating system design diagrams and data models applies specifically to multi-team software projects requiring ADRs and API contracts. The process focuses on planning, design, and hand-off phases, meaning it produces architectural artifacts rather than implementation code.

The Architect skill focuses on ADRs and system design because it solves the problem of defining and communicating robust system architecture. It reduces ambiguity in design and accelerates handoffs by producing clear architectural artifacts rather than executable code.