domain-driven

What problem does it solve?

It prevents incomplete or placeholder business-module implementations by enforcing Domain-Driven Design structure, full CRUD coverage, and explicit relationships and business rules.

Core Features & Use Cases

• Bounded context and sub-module discovery: Enumerates the full set of required sub-modules for the target domain (e.g., entities, transactions, reports).
• Complete CRUD completeness enforcement: Applies a completeness matrix per entity (create, list, detail, update, delete, restore) and checks for gaps.
• Production-grade implementation rules: Requires real logic (no mock/placeholder implementations), validates relationships, and ensures authorization and 404 handling.

Example use case: design an Inventory module where Products, Warehouses, Stock Movements, Purchase Orders, Suppliers, Stock Counts, and Reports are all fully specified and implemented with correct entity relationships and business rules.

Quick Start

Use the domain-driven skill to generate a complete Inventory business module with bounded contexts, full CRUD for every entity, real implementation logic, and an entity relationship map.