architecture▌

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.

Clean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase/Repository patterns, and data layer design with Room, SQLDelight, and Ktor.

MVVM architecture for Flutter apps with unidirectional data flow and strict layer separation. \n \n Implements three-layer architecture: Data Layer (Services and Repositories), Domain Layer (UseCases for complex logic), and UI Layer (ViewModels and Views) \n Uses provider for dependency injection and ListenableBuilder for reactive UI updates with the Command pattern for user interactions \n Enforces unidirectional data flow: data flows down from Repositories to ViewModels to Views; events flow u

Architectural guidance for scalable Flutter apps using MVVM, layered design, and feature-first organization. \n \n Supports two project structures: feature-first (recommended for teams and medium-to-large apps) and layer-first (for smaller apps or solo developers) \n Defines three core layers: UI (Views and ViewModels), Data (Repositories and Services), and optional Domain (Use-cases) \n Covers key design patterns including Command Pattern, Result Type for error handling, Repository Pattern, and

Analyze, audit, and improve project structure.