Use before non-trivial feature or bugfix work — phrases like "let's add X", "investigate Y", "understand how Z works", or when the user runs /archspec:investigate.
Maintains the plugin's architecture quality models, styles, patterns, technology profiles, reference architectures, migration guides, domain guidance, decision rules, machine rule…
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.
Models a business in its own language. Use when the domain has real business rules to capture.
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…
Deterministic architecture quality gate for verified review artifacts. Use in local checks or CI to validate architecture configuration, block configured confirmed severities,…
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.
Refine underdefined product or system architecture through focused interactive decisions. Use when the user wants architecture sparring before a formal implementation plan or…
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.
Converts an accepted architecture decision for confirmed findings into an executable migration roadmap.
Assess architecture decisions, ADR compliance, coupling analysis, and design principles
Run an Architecture Review Board that filters proposals by blast radius, reviews them through fixed lenses, issues binding decisions recorded as ADRs, and honors an appeals path.
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering.
Architecture evaluation criteria and technology standards for the homelab. Preloaded into the designer agent to ground design decisions in established patterns and 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.
Review software architecture for SOLID principles, design patterns, scalability, and maintainability. Use when evaluating system design or planning refactoring.
Ensure design docs explicitly capture risks, assumptions, and open questions with owners, deadlines, and mitigation plans.
Architectural rules engine — pattern validation, duplication detection, stack compatibility, and design pattern enforcement.
Use when code work touches runtime shape: services, app/CLI/background flows, deployment/IaC, observability, resilience, external integrations, ownership, and runtime coupling.
Run a bounded architectural refactor loop. Use this when the user asks to improve architecture, refactor toward a stated design, untangle module boundaries, fix dependency…
[Architecture] Use when grading project architecture and scalability quality for greenfield init or brownfield audit: build/CI scalability, distributed-monolith risk, module…
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation.
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…
Compares architecture styles, patterns, technologies, and keep-current options for confirmed findings or an approved Greenfield design brief with explicit quality-attribute…
Generates technical architecture specification from PRD. Covers architecture pattern, tech stack, data models, and app structure.