system-design

To document system architecture, you need to outline components, data models, interfaces, API design, dependencies, and scalability decisions. This Skill provides structured templates and best practices to generate an ARCHITECTURE.md file for new projects.

Scalable architecture design requires patterns that balance performance, security, and maintainability. You can apply decision frameworks to evaluate technology and select appropriate patterns based on your specific project goals and constraints.

An ARCHITECTURE.md file should document components, data models, interfaces, API design, dependencies, and scalability decisions. You can use structured guidance to map out deployment considerations and capture these architecture decisions systematically.

Yes, you can use this for technology evaluation and API design. It provides decision frameworks to assess technology choices and offers structured guidance for defining interfaces, data models, and deployment considerations.

You need structured guidance for system design when creating new change requests, evaluating technologies, or updating ARCHITECTURE.md. It helps balance performance, security, and maintainability while ensuring all components and dependencies are documented.

To balance performance and maintainability in system design, apply patterns and decision frameworks that evaluate trade-offs. You can input project goals and constraints to receive a structured plan that documents these architectural decisions.