V3 DDD Architecture
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
microservices-architect
Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.
nestjs-modular-monolith
Specialist in designing and implementing scalable modular monolith architectures using NestJS with DDD, Clean Architecture, and CQRS patterns. Use when building modular monolith backends, designing bounded contexts, creating domain modules, implementing event-driven module communication, or when user mentions "modular monolith", "bounded contexts", "module boundaries", "DDD", "CQRS", "clean architecture NestJS", or "monolith to microservices". Do NOT use for simple CRUD APIs, frontend work, or general NestJS questions without architectural context.
domain-analysis
Identifies subdomains and suggests bounded contexts in any codebase following DDD Strategic Design. Use when analyzing domain boundaries, identifying business subdomains, assessing domain cohesion, mapping bounded contexts, or when the user asks about DDD strategic design, domain analysis, or subdomain classification.
m09-domain
CRITICAL: Use for domain modeling. Triggers: domain model, DDD, domain-driven design, entity, value object, aggregate, repository pattern, business rules, validation, invariant
moai-foundation-philosopher
Strategic thinking framework integrating First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering for deeper problem-solving. Use when performing architecture decisions, technology selection trade-offs, root cause analysis, cognitive bias detection, or first principles decomposition. Do NOT use for code quality validation (use moai-foundation-quality instead) or implementation workflows (use moai-workflow-ddd instead).
moai-workflow-testing
Comprehensive testing and development workflow specialist combining DDD testing, characterization tests, performance profiling, code review, and quality assurance. Use when writing tests, measuring coverage, creating characterization tests, performing TDD, running CI/CD quality checks, or reviewing pull requests. Do NOT use for debugging runtime errors (use expert-debug agent instead) or code refactoring (use moai-workflow-ddd instead).
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, and agent catalog reference. Use when referencing TRUST 5 gates, SPEC workflow, EARS format, DDD methodology, agent delegation patterns, or MoAI orchestration rules. Do NOT use for context and token management (use moai-foundation-context instead) or strategic analysis (use moai-foundation-philosopher instead).
moai-workflow-ddd
Domain-Driven Development workflow specialist using ANALYZE-PRESERVE-IMPROVE cycle for behavior-preserving code transformation. Use when refactoring legacy code, improving code structure without functional changes, reducing technical debt, or performing API migration with behavior preservation. Do NOT use for writing new tests (use moai-workflow-testing instead) or creating new features from scratch (use expert-backend or expert-frontend instead).
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development methodology. Use when creating SPEC documents, writing EARS requirements, defining acceptance criteria, planning features, or orchestrating the /moai plan phase. Do NOT use for implementation (use moai-workflow-ddd instead) or documentation generation (use moai-workflow-project instead).
ddd:software-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
domain-model-extractor
Extract domain models from monolithic codebases using DDD principles for microservices decomposition
Flutter Layer-based Clean Architecture + DDD
Standards for separation of concerns, layer dependency rules, and DDD in Flutter.
Laravel Clean Architecture
Expert patterns for DDD, DTOs, and Ports & Adapters in Laravel.
tactical-ddd
Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design. Triggers on: domain modeling, aggregate design, 'entity', 'value object', 'repository', 'bounded context', 'domain event', 'domain service', code touching domain/ directories, rich domain model discussions.
qcsd-ideation-swarm
QCSD Ideation phase swarm for Quality Criteria sessions using HTSM v6.3, Risk Storming, and testability analysis before development begins. Uses a 5-tier browser cascade: Vibium → agent-browser → Playwright+Stealth → WebFetch → WebSearch-fallback.
V3 DDD Architecture
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
V3 QE DDD Architecture
Domain-Driven Design architecture for Agentic QE v3. Implements modular, bounded context architecture with clean separation of concerns for quality engineering domains.
qcsd-cicd-swarm
QCSD Verification phase swarm for CI/CD pipeline quality gates using regression analysis, flaky test detection, quality gate enforcement, and deployment readiness assessment. Consumes Development outputs (SHIP/CONDITIONAL/HOLD decisions, quality metrics) and produces signals for Production monitoring.
qcsd-refinement-swarm
QCSD Refinement phase swarm for Sprint Refinement sessions using SFDIPOT product factors, BDD scenario generation, and requirements validation.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
qcsd-development-swarm
QCSD Development phase swarm for in-sprint code quality assurance using TDD adherence, code complexity analysis, coverage gap detection, and defect prediction. Consumes Refinement outputs (BDD scenarios, SFDIPOT priorities) and produces signals for Verification.
spring-boot-project-creator
Creates and scaffolds a new Spring Boot project (3.x or 4.x) by downloading from Spring Initializr, generating package structure (DDD or Layered architecture), configuring JPA, SpringDoc OpenAPI, and Docker Compose services (PostgreSQL, Redis, MongoDB). Use when creating a new Java Spring Boot project from scratch, bootstrapping a microservice, or initializing a backend application.
ddd-hexagonal-architecture
Provides comprehensive guidance for hexagonal architecture including ports and adapters, domain isolation, and dependency inversion. Use when the user asks about hexagonal architecture, needs to implement ports and adapters pattern, or structure applications with hexagonal architecture.
ddd-cola
Provides comprehensive guidance for COLA architecture including adapter layer, application layer, domain layer, and infrastructure layer. Use when the user asks about COLA, needs to implement COLA architecture, structure applications with COLA, or work with COLA patterns.
ddd-event-driven
Provides comprehensive guidance for event-driven architecture including domain events, event sourcing, CQRS, and event patterns. Use when the user asks about event-driven architecture, needs to implement event-driven systems, or work with domain events.
mybatis-plus-generator
Provides comprehensive guidance for generating MyBatis-Plus code including Entity, Mapper, Service, ServiceImpl, Controller, DTO, VO, BO and other related objects from database tables. Use ONLY when the user explicitly mentions MyBatis-Plus, mybatis-plus-generator, or wants to generate code using MyBatis-Plus framework. This skill automatically generates standard CRUD methods and custom methods based on user requirements for MyBatis-Plus projects. Supports MVC and DDD architectures, Java and Kotlin languages. Do NOT trigger for generic code generation, JPA/Hibernate, or other ORM frameworks.
ddd-microservices
Provides comprehensive guidance for DDD in microservices including bounded contexts, service boundaries, event-driven architecture, and microservice patterns. Use when the user asks about DDD microservices, needs to design microservices with DDD, or implement microservice architectures.
ddd4j-project-creator
A comprehensive skill for creating new ddd4j (Domain-Driven Design for Java) projects based on ddd4j-boot framework. Use ONLY when the user explicitly mentions creating a ddd4j project, initializing ddd4j project, or setting up ddd4j-boot project. Supports three project types: single-module monolith, multi-module monolith, and microservices. Generates project scaffolding based on ddd4j-boot architecture with DDD, Hexagonal Architecture, Clean Architecture, and COLA V5 patterns. Do NOT trigger for generic DDD projects, JPA/Hibernate projects, or other ORM frameworks without explicit ddd4j mention.
ddd-clean-architecture
Provides comprehensive guidance for clean architecture including layer separation, dependency rules, and architectural patterns. Use when the user asks about clean architecture, needs to implement clean architecture principles, or structure applications with clean architecture.
domain-driven-design
Domain-Driven Design tactical patterns for complex business domains. Use when modeling entities, value objects, domain services, repositories, or establishing bounded contexts.
concept-modeler
从模糊的用户需求中提取领域概念——实体、流程和"暗物质"(用户没说的)。基于 DDD(领域驱动设计)方法论。
architecture-clean-ddd
Architecture Clean + DDD + Hexagonal - Atoll Tourisme. Use when designing architecture or reviewing code structure.
ddd-patterns
Patterns DDD - Atoll Tourisme. Use when implementing DDD patterns.
ddd-modeling
ドメインエキスパートとの対話を通じてユビキタス言語(用語集)とドメインモデルを作成する。新規プロジェクト開始時のドメイン理解、既存システムのリファクタリング前のモデル整理、チーム内での用語統一が必要な場合に使用。「DDDでモデリングしたい」「ドメインモデルを作成」「用語集を整理」「ユビキタス言語を定義」などのリクエストで起動。
usecase-description
ユーザーストーリーを詳細なユースケース記述に展開する。正常系・異常系・代替フロー、ビジネスルールを明確化する。ユーザーストーリー作成後、DDDモデリングや設計の前に使用。「ユースケースを詳細化したい」「フローを整理したい」「異常系を洗い出したい」「ビジネスルールを明確にしたい」などのリクエストで起動。
requirements
要件・設計フェーズを実行。user-story → ui-sketch → usecase-description → feasibility-check → ddd-modeling → analyzing-requirements を順次実行し、DESIGN.md を生成。「設計フェーズを開始」「要件を整理したい」「/requirements」などで起動。
feasibility-check
技術的な実現可能性を検証し、PoCの計画を立てる。ユースケース記述後、DDDモデリングや本格実装の前に技術リスクを洗い出す場合に使用。「技術的に実現できるか確認したい」「PoCを計画したい」「技術リスクを洗い出したい」「不確実性を検証したい」などのリクエストで起動。
lana-review
Review code changes against LANA Bank's DDD patterns, event sourcing conventions, and architectural principles. Use when reviewing PRs, commits, or code changes.
domain-model-first
A guide to domain-model-centered development. It explains a method for designing and implementing domain models test-first and developing in the order: in-memory repository → use cases → infrastructure. Triggers: activated by development-process-related requests such as "want to start from the domain model", "DDD with TDD", "how to build an in-memory repository", "how to test use cases", "how to progress DDD development", etc.
domain-building-blocks
A design guide for DDD building blocks (value objects, entities, aggregates, domain services). Used when domain modeling, designing entities, deciding aggregate boundaries, or implementing value objects. Triggers: domain-modeling related requests such as “I want to create a value object,” “aggregate design,” “how to write domain services,” “difference between entity and value object,” or “I want to implement this in DDD.”
aggregate-design
Performs code reviews and design assistance based on DDD aggregate design rules. Used for designing new aggregates, reviewing existing aggregates, and during refactoring. Triggered by aggregate-design–related requests such as: 'I want to design an aggregate', 'Review an aggregate', 'Implement an Aggregate', 'Decide aggregate boundaries', 'Implement with DDD', etc.
DDD module pattern
Domain-layer packaging guidance based on DDD module patterns. Detects technology-driven packaging (entities/, value-objects/, services/, repositories/, etc.) and prompts migration to domain-terminology-based packaging. Guides module names in the domain layer so they become part of the ubiquitous language. Triggers: activated by domain-module-related requests such as “domain layer package structure”, “DDD module design”, “want to fix technology-driven packaging”, “want to stop using an entities/ folder”, “domain package review”, and similar.
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability
domain-entity-generator
Generates Domain Entities following DDD principles with factory methods, private setters, domain events, and proper encapsulation. Supports aggregate roots, child entities, and value objects.
domain-events-generator
Generates Domain Events and their handlers following DDD patterns. Implements event raising in entities, MediatR notification handlers, and the Outbox pattern for reliable event processing.
Milan Jovanovic Blog
Search Milan Jovanovic's .NET blog for Clean Architecture, DDD, CQRS, EF Core, and ASP.NET Core patterns. Use for finding applicable patterns, code examples, and architecture guidance. Invoke when working with .NET projects that could benefit from proven architectural patterns.