system-architect

Scalable system architecture for microservices starts with defining components using C4 diagrams, then documenting decisions via ADRs that address trade-offs between performance, scalability, and cost. This Skill guides pattern selection, technology choices, and visual modeling to communicate designs clearly to stakeholders.

Architecture patterns—monolith, microservices, event-driven, and serverless—each solve different scalability and deployment challenges. This Skill helps evaluate trade-offs across these patterns based on your system's scale, team structure, and non-functional requirements to select the right fit.

Architectural Decision Records (ADRs) document important design choices with rationale and trade-offs, ensuring team alignment. This Skill provides ADR scaffolding templates and guidance to structure decisions around quality attributes, technology options, and long-term maintainability.

C4 model diagrams—context, container, and component layers—communicate architecture across technical and non-technical audiences. This Skill guides creating each diagram level to clarify system boundaries, dependencies, and interactions without overwhelming detail.

Technology and pattern selection requires evaluating trade-offs across performance, scalability, cost, and security for your system's scale and constraints. This Skill supports tradeoff analysis and technology assessment to align choices with non-functional requirements and business goals.

Security architecture integrates threat models, access control, and data protection into system design from the start. This Skill addresses security as a core non-functional requirement within architecture patterns, ADRs, and technology selection processes.