← LeaderboardThe Skill Leaderboard

implementing-domain-driven-design

Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.

Published by ciembor ↗ciembor/agent-rules-books

Try your first task

implementing-domain-driven-design

Start a fresh conversation. Replace the highlighted placeholders.

Use implementing-domain-driven-design to implement [domain change] in bounded context [bounded context] within [codebase area], with explicit local terminology, invariant-focused aggregate boundaries, identity-based cross-aggregate references, and explicit translation at any context boundary.

Required inputs

  • [domain change]
  • [bounded context]
  • [codebase area]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: implementing-domain-driven-designdescription: Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.license: MIT

Implementing Domain-Driven Design Skill

Use this skill when a task involves implementing DDD in code: aggregate boundaries, invariants, repositories, domain events, application services, modules, factories, or bounded-context integration.

Before making design or code decisions, read and apply implementing-domain-driven-design.mini.md. Use implementing-domain-driven-design.md only as a deeper reference when the mini rules are not enough for the current implementation tradeoff.