system-architect

System architecture design for microservices involves defining component boundaries, service responsibilities, and communication patterns. This Skill generates C4 diagrams visualizing Context, Container, and Component layers, creates Architecture Decision Records documenting trade-offs, and provides technology recommendations tailored to your scalability requirements.

An Architecture Decision Record documents critical architectural choices, their rationale, and trade-offs. ADRs create institutional knowledge and prevent repeated decisions. This Skill generates ADRs automatically during system design, capturing functional and technical requirements alongside decision context.

The choice depends on scalability needs, team structure, and deployment complexity. This Skill performs ATAM and payoff analyses comparing monolithic and microservices approaches, evaluates technology stacks for each model, and generates C4 diagrams to visualize the implications of each architectural choice.

Yes. C4 Model diagrams effectively represent cloud-native architectures across abstraction levels. This Skill generates Mermaid-based C4 diagrams for Context, Container, and Component views, integrating cloud services, security boundaries, and data flows into your architecture documentation.

Security architecture covers authentication, authorization, data isolation, and threat boundaries. This Skill integrates security architecture into design workflows, documents security decisions in ADRs, and includes security trade-offs in technology evaluation to ensure scalable, maintainable, and secure systems.

Structured architectural design captures both functional and technical requirements against business objectives. This Skill produces C4 diagrams, ADRs, and trade-off analyses that bridge business requirements and technical implementation, supporting alignment through documented decision rationale and steering memory integration.