architecture▌

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.

42 Clean Architecture rules organized by priority for designing maintainable, testable software systems. \n \n Covers 8 rule categories from dependency direction and entity design (critical) through testing architecture (low-medium), each with specific guidance and code examples \n Dependency rules enforce inward-pointing dependencies, interface ownership, and acyclic component graphs to prevent architectural decay \n Entity and use case rules isolate business logic from frameworks, persistence,

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

This skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles.

Analyze, audit, and improve project structure.

Plan and optimize your website's page hierarchy, navigation, URL structure, and internal linking. \n \n Provides page hierarchy templates for six site types (SaaS, content, e-commerce, documentation, hybrid, small business) with typical depth and URL patterns \n Includes navigation design rules (header nav limits, dropdown organization, breadcrumb implementation) and URL structure principles (human-readable slugs, hierarchy alignment, redirect strategies) \n Delivers structured output: ASCII tre

$23