architecture▌

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

Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns for context. Provides frameworks for pattern selection, ADR creation, and technical debt management.

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

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.

Use this skill to pick the best Swift architecture playbook for SwiftUI/UIKit codebases and apply it to the user’s task.

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

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

Reference knowledge for building well-structured browser games. These patterns apply to both Three.js (3D) and Phaser (2D) games.

Information Architecture creates logical structures that help users find and understand information easily.

Analyzes codebases to generate comprehensive architectural documentation with diagrams and implementation patterns. \n \n Auto-detects technology stacks (.NET, Java, React, Angular, Python, Node.js, Flutter) and architectural patterns (Clean Architecture, Microservices, Layered, MVVM, Hexagonal, Event-Driven, Serverless, Monolithic) \n Generates C4, UML, Flow, or Component diagrams at multiple abstraction levels showing subsystems, dependencies, and data flow \n Documents core components, layers