architecture▌

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.

$22

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

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

Create branded visual diagrams in various formats with customizable styles.

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).

Analyze codebases for architectural friction and propose module-deepening refactors as testability improvements. \n \n Explores codebases organically to surface shallow modules, tightly-coupled components, and untested seams rather than following rigid heuristics \n Applies John Ousterhout's \"deep module\" principle: small interfaces hiding large implementations for better testability and AI navigability \n Generates multiple radically different interface designs (minimalist, flexible, caller-o

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.