ddd-context
Create and manage a DDD bounded context with standard directory structure. Use when starting a new subdomain, splitting a monolith into bounded contexts, or scaffolding the domain/application/infrastructure layout for a fresh module.
Install
npx skills add https://github.com/ruvnet/ruflo --skill ddd-contextSKILL.md
Create a bounded context directory structure for the given context name.
Parse $ARGUMENTS as the context name (kebab-case). If empty, list existing contexts.
Steps
Validate name: Ensure the context name is kebab-case and does not already exist under
src/.Create directory structure:
src/<context-name>/ domain/ entities/ value-objects/ events/ services/ repositories/ application/ infrastructure/Generate index files:
src/<context-name>/domain/entities/index.ts-- barrel export for entitiessrc/<context-name>/domain/value-objects/index.ts-- barrel export for value objectssrc/<context-name>/domain/events/index.ts-- barrel export for domain eventssrc/<context-name>/domain/services/index.ts-- barrel export for domain servicessrc/<context-name>/domain/repositories/index.ts-- barrel export for repository interfacessrc/<context-name>/domain/index.ts-- re-export all domain submodulessrc/<context-name>/application/index.ts-- barrel export for application servicessrc/<context-name>/infrastructure/index.ts-- barrel export for infrastructure implementationssrc/<context-name>/index.ts-- public API of the bounded context (re-exports domain and application only, NOT infrastructure)
Store in domain model graph:
mcp__plugin_ruflo-core_ruflo__agentdb_hierarchical-store --parent "domain" --child "context:<context-name>" --relation "contains" mcp__plugin_ruflo-core_ruflo__memory_store --key "ddd-context-<context-name>" --value "Created bounded context" --namespace tasksReport: Confirm the context was created and list the generated files.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".