Convert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns.
Use when architecture choices need executable guardrails: dependency rules, cycle checks, boundary tests, ownership review gates, ADR compliance, runtime/resilience checks, and CI…
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service…
Architecture governance and assessment tool. Evaluate cloud architectures against best practices and generate actionable improvement reports.
scalable-monorepo-starter의 8가지 아키텍처 불변 규칙 + shadcn 마이그레이션 보강 가드(배럴 export, cn 사용, prop mutation)를 정적 스캔으로 검증하는 스킬.
Architecture guardrails for Engram across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state flow, or…
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
Interpret and triage architecture scanner output — cluster findings by module and root cause, classify true positives vs false positives vs acceptable design, and produce a…
Detección de patrones de arquitectura, sugerencias de mejora y recomendaciones para proyectos nuevos
Analyze, review, and plan architecture alternatives through a structured interview. Use when the user needs tradeoffs surfaced before implementation or a Linear decision note…
Inventory your cloud architectures and assess risks. Query architecture blueprints, evaluate Well-Architected scores, and identify governance gaps.
Architecture consultation for Conductor orchestrator. Makes decisions about system design, patterns, component boundaries, and technical architecture.
Detect clean architecture layer violations and check dependency rule violations. Verify dependency direction of events→facades→services→repository.
Use when implementation, refactoring, or review may affect architecture. Start from prompts/memory/index.md.
Create or revise repository `ARCHITECTURE.md` files as short, stable architecture codemaps. Use when an agent needs to author or edit `ARCHITECTURE.md`, restructure an…
Build comprehensive ARCHITECTURE.md files following matklad's canonical guidelines — bird's-eye views, ASCII/Mermaid diagrams, codemaps, invariants, and layer boundaries.
Аудит и планирование архитектурной миграции cable_designer: uv workspace, schema-per-context, boundary enforcement, SQLModel to SQLAlchemy 2.0.
Воркфлоу инициализации нового проекта — структура, конфиги, документация, первый коммит. Используй при создании проекта с нуля.
Use when architecture crosses ownership or review boundaries: CODEOWNERS/OWNERS, module coverage, cross-owned dependencies, socio-technical coordination, and governance paths.
Client-server architecture for web/mobile apps with centralized services and API design.
Apply CQRS and Event Sourcing for read/write separation and audit trails. Use when auditability is critical.
Apply event-driven async messaging to decouple producers and consumers. Use for real-time processing.
Functional Core, Imperative Shell: isolate deterministic logic from side effects for testability.
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure.
Layered (n-tier) architecture with enforced layer boundaries and separation of concerns.
Microkernel architecture with a minimal core and plugin-based extensibility for platforms.
Apply microservices for independent deployment and per-service scaling. Use when bounded contexts are clear.
Design pipes-and-filters for sequential data transformations. Use when data flows through processing stages.
Apply serverless FaaS patterns for event-driven workloads with minimal infrastructure. Use when cost scales with usage.
Design coarse-grained service architecture for deployment independence without microservices complexity and overhead.
Apply data-grid architecture for high-traffic stateful workloads with in-memory processing and linear scalability.
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints.
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
Organizational coding standards and architectural patterns. References comprehensive skills for detailed patterns. Use when making architecture decisions or implementing features.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.
Core architectural principles for StepLeague - modular design, system thinking, future-proofing, and maintenance reduction.
Validate UI architecture boundaries, backend contracts, and ADR need before spec planning. Use when starting a new UI feature or invoking /ui-architecture-preflight.
Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent…
Creates an upfront system architecture proposal before implementation begins. Defines bounded contexts, layer strategy, system-wide patterns, and quality attributes — the…
Use when code changes need staged structural design: boundary extraction, modularization, dependency inversion, migrations, anti-corruption layers, tests, rollout gates, and…
Quick reference for Portfolio Buddy 2 project structure. Use when: adding new features, modifying existing components, understanding data flow, or onboarding to the codebase.
Meta-skill for maintaining and evolving Alex's cognitive architecture through deliberate documentation and pattern extraction.
Expert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.
Assess architecture decisions, ADR compliance, coupling analysis, and design principles
Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.
Use when code work touches runtime shape: services, app/CLI/background flows, deployment/IaC, observability, resilience, external integrations, ownership, and runtime coupling.
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Use to collapse over-engineered abstractions, remove unnecessary layers, or consolidate redundant logic.
Automated SRP validation using multi-dimensional detection. Use when reviewing code for SRP compliance, checking "is this doing too much", validating architectural boundaries,…
確定した仕様を、モジュール境界・データフロー・状態管理・失敗時挙動を持つ設計案に落とし込む。Use when: WF-03 Solution Design で設計の叩き台を作りたい時、実装前にアーキテクチャの骨子を固めたい時。
Comprehensive system architecture design and implementation workflow that orchestrates expert analysis, technical decision-making, and architectural pattern selection using the…
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure.
Use when working in massCode and you need repo-wide architecture rules, naming conventions, decomposition boundaries, or guidance on which massCode skill to load next.
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps).
Use this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure modifications align with established…
Generate a reference architecture specification from analyzed frameworks. Use when (1) designing a new agent framework based on prior art, (2) defining core primitives (Message,…
Activate BEFORE any system design decision, service boundary definition, database schema change, or technology selection. Ensures human reasoning leads, AI challenges.