architecture▌

$22

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

This skill provides comprehensive architecture review capabilities for Python backend applications, covering all aspects of system design from infrastructure to code organization.

Generate software architecture documentation using C4 model Mermaid diagrams. \n \n Supports all four C4 levels: System Context, Container, Component, and Deployment diagrams, plus Dynamic diagrams for request flows \n Includes syntax and examples for people, systems, containers, components, boundaries, and relationships with directional and styling options \n Provides microservices modeling guidance for single-team and multi-team ownership, plus event-driven architecture patterns \n Recommends

Create branded visual diagrams in various formats with customizable styles.

Implement proven backend architecture patterns for maintainable, testable, and scalable systems. \n \n Covers three core patterns: Clean Architecture (layered dependency inward), Hexagonal Architecture (ports and adapters), and Domain-Driven Design (bounded contexts, aggregates, value objects) \n Includes complete directory structures, code examples, and implementation patterns for Python backends using FastAPI, asyncpg, and similar frameworks \n Demonstrates practical separation of concerns: do

Use this skill for system-level design decisions rather than implementation details within a single service or component.

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

High-level system architecture design, decision documentation, and technology trade-off evaluation for distributed systems. \n \n Guides full architecture workflows from requirements gathering through stakeholder review, with explicit trade-off analysis and failure mode planning \n Produces architecture diagrams (Mermaid format), Architecture Decision Records (ADRs), and technology recommendations with documented rationale \n Covers architectural patterns, microservices structuring, scalability

Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).