Files
Reuven f25bcf2073 feat: add 10 new ruflo plugins, optimize all 32, add READMEs and user guide
New plugins: ruflo-adr (ADR lifecycle), ruflo-ddd (domain-driven design),
ruflo-sparc (SPARC methodology), ruflo-neural-trader (trading strategies),
ruflo-ruvector (vector embeddings), ruflo-knowledge-graph (entity graphs),
ruflo-market-data (OHLCV ingestion), ruflo-migrations (schema management),
ruflo-observability (logging/tracing), ruflo-cost-tracker (token budgets).

Optimizations across all 32 plugins:
- All pass `claude plugin validate` (removed invalid manifest arrays)
- 51/51 skills have argument-hint frontmatter
- Model routing: 4 haiku, 24 sonnet, 2 opus (cost-optimized)
- Neural learning hooks on 25/30 agents
- Cross-references between 6 related plugin pairs
- Pathfinder graph traversal algo for researcher agent
- READMEs for all 32 plugins + plugins/README.md catalog
- discover-plugins skill updated with full 32-plugin catalog

Co-Authored-By: claude-flow <ruv@ruv.net>
2026-04-29 23:46:54 -04:00

1.5 KiB

name, description
name description
ddd Domain-Driven Design scaffolding and boundary enforcement

$ARGUMENTS

Route DDD commands based on the subcommand:

Subcommands

ddd context create <name>

Scaffold a new bounded context directory structure. Invoke the /ddd-context skill with the context name.

ddd context list

List all bounded contexts by scanning src/*/domain/ directories:

find src -maxdepth 2 -name "domain" -type d | sed 's|src/||;s|/domain||'

ddd aggregate <context> <name>

Generate an aggregate root with entity, value objects, repository interface, domain events, and unit test stubs. Invoke the /ddd-aggregate skill with <context> <name>.

ddd event <context> <name>

Create a domain event class in the target context:

  • File: src/<context>/domain/events/<name>.event.ts
  • Include: event name (past tense), timestamp, payload interface, static factory method
  • Register the event in the context's event index

ddd validate

Check domain boundary violations. Invoke the /ddd-validate skill.

ddd map

Visualize the context map with relationships:

  1. Scan all bounded contexts under src/
  2. Analyze imports to detect inter-context dependencies
  3. Output a context map showing:
    • Each bounded context and its aggregates
    • Relationships: upstream/downstream, ACL, shared kernel, published language
    • Boundary violations (direct imports instead of events/ACL)

Parsing

Parse $ARGUMENTS to extract the subcommand and its arguments. If no arguments are provided, show the help text listing all subcommands.