architecture▌

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

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

$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

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

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

Create branded visual diagrams in various formats with customizable styles.

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

CSS architecture patterns for scalable, maintainable styling systems across teams and projects. \n \n Covers three core methodologies: BEM (Block Element Modifier) for component naming, SMACSS for modular organization, and CSS-in-JS with Styled Components for dynamic styling \n Includes reference guides for CSS Variables, Utility-First CSS (Tailwind pattern), and practical implementation examples \n Best suited for large-scale stylesheets, component-based design systems, and multi-team collabora

Comprehensive guide to designing, implementing, and maintaining microservices architectures. Covers service decomposition, communication patterns, data management, deployment strategies, and observability for distributed systems.