architecture

This skill provides a structured framework for software architects and engineers to navigate complex system design challenges. It focuses on the principle that requirements should drive architecture, while trade-offs must be evaluated explicitly through Architecture Decision Records (ADRs). By following this framework, users can move from high-level system requirements to validated, well-documented architectural decisions that prioritize simplicity and maintainability.

• Facilitates systematic requirements analysis and constraint identification.

• Supports trade-off evaluation using standardized frameworks to compare patterns and technologies.

• Automates the creation and management of ADRs to capture architectural rationale and historical context.

• Includes pattern selection guidance through decision trees and anti-pattern warnings to avoid common pitfalls.

• Integrates with related skills such as database design, API pattern development, and deployment architecture planning.

• Users should start with the context-discovery tools when initializing a new system design to identify project classification.

• Follow the core principle that simplicity is the ultimate sophistication; only add complexity when proven necessary.

• Use the validation checklist before finalizing architecture to ensure all requirements are understood and trade-offs are documented.

• Input expected includes project requirements, design constraints, and candidate architectural patterns; outputs are structured ADRs and documented rationale.

• Practical tip: If you are unsure of a design path, use the pattern-selection decision trees to weigh the pros and cons of modular vs. monolithic approaches.