What problem does it solve?
Provides clear, repeatable guidance to avoid ad-hoc architecture decisions, reduce design drift, and ensure critical trade-offs are documented so teams can build scalable, reliable systems.
Core Features & Use Cases
- ADR (Architecture Decision Records): Templates and guidance for capturing context, options, and rationale for significant technical choices.
- System Design Checklist: Practical checks for scalability, reliability, observability, security, and operational concerns during design reviews.
- Architecture Patterns & API Design: Recommendations for microservices, event-driven, layered, and hexagonal patterns plus RESTful API conventions, versioning, pagination, and error handling.
- Use Case: Use the skill to draft an ADR when deciding between a monolith and microservices, perform a scalability assessment for a new service, or run a checklist before production launch.
Quick Start
Ask the architecture skill to create an ADR comparing monolith and microservices for a new user service, include context, alternatives, and recommended rationale.