AgentSkillsCN

ddd

为 TypeScript/Deno 代码库提供领域驱动设计指导。在编写或修改代码时应用此指导,以合理选择 DDD 构建模块(实体、值对象、聚合、领域服务、仓库),并保持通用语言的一致性。通过所有代码变更触发,确保领域模型的稳定性与一致性。

SKILL.md
--- frontmatter
name: ddd
description: Domain Driven Design guidance for TypeScript/Deno codebases. Apply when writing or modifying code to choose appropriate DDD building blocks (entities, value objects, aggregates, domain services, repositories) and maintain ubiquitous language. Triggers on all code changes to ensure domain model consistency.

Domain Driven Design

Apply these patterns when implementing domain logic in TypeScript/Deno.

Building Block Selection

Choose the appropriate type based on these criteria:

TypeIdentityMutabilityWhen to Use
Value ObjectNone (equality by value)ImmutableMeasurements, descriptions, identifiers, money, dates, addresses
EntityHas unique IDMutableThings with lifecycle, tracked over time, referenced by ID
AggregateRoot entity + childrenRoot controls mutationsConsistency boundary, transactional unit, enforce invariants
Domain ServiceNoneStatelessOperations spanning multiple aggregates, external integrations
RepositoryNoneStatelessPersistence abstraction for aggregates only

Quick Decision Flow

code
Does it have a unique identity that matters?
├─ No → Value Object
└─ Yes → Does it enforce invariants over child objects?
         ├─ Yes → Aggregate Root
         └─ No → Entity (likely part of an aggregate)

TypeScript Patterns

See references/patterns.md for implementation examples.

Ubiquitous Language

Update the project's ubiquitous language glossary when:

  • New domain concept introduced (add term + definition)
  • Meaning clarified through discussion (refine definition)
  • Naming conflicts discovered (resolve and document)
  • Bounded context boundary identified (note context for term)

Location: Document terms in code via types/interfaces. Add non-obvious terms to project documentation.

Naming Rules

  • Use domain expert terminology, not technical jargon
  • Prefer nouns for entities/value objects: Order, Money, Address
  • Prefer verbs for domain services: PricingService, ShippingCalculator
  • Name aggregates by their root: Order (not OrderAggregate)

Anti-Patterns to Avoid

  • Anemic domain model: Entities with only getters/setters, logic in services
  • God aggregate: Too many entities under one root (split by invariant boundary)
  • Repository per entity: Only aggregate roots get repositories
  • Leaking persistence: Domain objects should not know about storage