adaptive-architectureDesign systems that evolve and work offline (Local-First, WASM, CRDTs). Use when: local-first, offline-first, crdt, automerge, yjs, wasm, webassembly, edge ai, resiliency.
api-standardsEnforce REST/GraphQL API design and governance standards. Use when: design api, review api standards, enforce api governance.
arch-debtIdentify architectural anti-patterns — coupling, circular dependencies, God objects — and propose concrete migration paths. Use when: architecture debt, coupling, God object, Big Ball of Mud, circular dependency, spaghetti, modularize, arch debt.
arch-patternsRecommends and analyzes system architecture patterns (Microservices, EDA, Serverless, etc.) based on requirements. Use when: architecture, system design, scalability, microservices, event-driven, serverless.
architecture-governanceAutomated fitness functions (ArchUnit) to prevent architectural drift. Use when: architecture governance.
attribute-driven-designDrive architecture from quality-attribute scenarios using the iterative ADD 3.0 method, producing a reviewable design workbook. Use when: run attribute-driven design, design from quality attribute scenarios, add 3.0 design round, decompose architecture element, choose tactics and patterns, build an
blockchain-dltArchitect and audit Distributed Ledger/Blockchain systems and Smart Contracts. Use when: design blockchain, write smart contract, dlt architecture, web3 integration, ethereum, solidity, ledger.
compatibility-designManage breaking changes, migrations, and API evolution. Use when: compatibility, migration, versioning, breaking change, deprecation, legacy support, expand contract.
critical-systems-archDesign architecture for safety-critical and high-reliability systems. Use when: design critical system, architect safety-critical application, enforce high reliability.
design-patternsIdentifies, implements, and refactors code using standard Design Patterns (GoF + Modern). Use when: design pattern, refactor pattern, strategy pattern, observer pattern, factory pattern, singleton.
diagrammingChoose and create the right diagram type (UML, C4, ER, BPMN, domain) in standard notation; Mermaid-compatible output. Use when: create diagram, draw diagram, which diagram, diagram this, visualize, sequence diagram, class diagram, flowchart, architecture diagram, ER diagram, state diagram, activity
domain-modelCreate or review a domain model — bounded contexts, entities, value objects, aggregates, domain events, relationships. Use when: domain model, bounded context, ubiquitous language, context map, domain design, domain analysis, domain events, aggregate, entities, DDD analysis.
enterprise-migration-scenarioPlan and execute complex enterprise-scale legacy migrations. Use when: plan enterprise migration, migrate legacy to microservices, architect system migration.
enterprise-patternsImplement robust Enterprise Architecture Patterns. Use when: implement enterprise pattern, add circuit breaker, design saga pattern.
error-handling-strategyCentralized error handling (RFC 7807), circuit breakers, and user-facing fallbacks. Use when: error handling strategy.
event-driven-architectureDesign and implement Event-Driven and Async Architectures. Use when: design event-driven system, implement eda, setup message broker topology.
event-governanceSchema Registry enforcement (Avro/JSON), CloudEvents standard, and Event Evolution rules. Use when: event governance.
fitness-functionsDefine objective, measurable tests for architectural characteristics and wire them into CI as automated, continuous architecture governance. Use when: write architecture fitness functions, measure architectural characteristics, enforce layering rules in ci, set a latency budget test, atomic vs holis
graphql-schemaSchema design, federation, and resolution strategies. Use when: graphql schema.
legacy-modernizationAnalyze, document, and modernize legacy systems (COBOL, Mainframe, Fortran). Use when: legacy code, cobol, mainframe, fortran, ibm z, jcl, db2, cics, modernization, rewrite, migration.
microservicesDesign and implement microservices architecture. Use when: design microservices, split monolith, architect distributed system.
middleware-designDesigning robust middleware chains (Auth, Rate Limiting, Logging). Use when: middleware design.
monolithDesign and refactor Monolithic and Modular Monolithic architectures. Use when: design monolith, build modular monolith, enforce boundaries.
realtime-commWebSocket handling, Pub/Sub patterns, and persistent connections. Use when: realtime comm.
state-managementManage client-side state, side effects, and data flow. Use when: state management.
system-qualitiesDefine and enforce Quality Attributes (Non-Functional Requirements). Use when: define NFRs, analyze system qualities, set SLAs.
system-scalabilityAudit and architect scaling boundaries and bottlenecks. Use when: scale up, scale out, horizontal scalability, vertical scaling, load balancing, analyze scalability.
systems-architectureGenerate comprehensive C4 models and System Architecture documents. Use when: generate c4 model, document system architecture, architect entire system.
visual-whiteboardingUse spatial-canvas MCP servers (Miro, Draw.io, Figma) to map architectures, user flows, and wireframes. Use when: whiteboard, miro, draw.io, figma, canvas, spatial, wireframe.