architecture▌

Use this skill when:

A disciplined approach to structuring software so that business rules remain independent of frameworks, databases, and delivery mechanisms. Apply these principles when designing system architecture, reviewing module boundaries, or advising on dependency management.

Framework for analyzing requirements, evaluating trade-offs, and documenting architectural decisions. \n \n Guides context discovery through structured questions and project classification before design begins \n Provides ADR templates and trade-off analysis framework for capturing decision rationale and alternatives \n Includes decision trees and anti-pattern guidance for selecting appropriate architectural patterns \n Emphasizes simplicity-first approach: add complexity only when proven necess

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

This skill provides comprehensive guidance for implementing Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design tactical patterns in Java 21+ Spring Boot 3.5+ applications. It ensures clear separation of concerns, framework-independent domain logic, and highly testable codebases through proper layering and dependency management.

Use this skill when you need to:

Generate system architecture diagrams using Mermaid, PlantUML, C4 models, and flowcharts for technical documentation. \n \n Supports multiple diagram types: system architecture, sequence diagrams, C4 context and component diagrams, deployment diagrams, data flows, and class diagrams \n Text-based, version-control-friendly formats that integrate directly into documentation and code repositories \n Includes best practices for consistent notation, meaningful color coding, logical grouping with subg

Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.

Structured framework for analyzing requirements, evaluating trade-offs, and documenting architectural decisions. \n \n Provides context discovery questions and project classification to align architecture with actual requirements \n Includes trade-off analysis templates and ADR (Architecture Decision Record) documentation patterns for capturing decision rationale \n Offers decision trees and anti-pattern guidance to help select appropriate architectural patterns \n Emphasizes simplicity-first ap

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.