Ddd tactical patterns

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/ddd-tactical-patterns

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill ddd-tactical-patterns

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.

SKILL.md

1.6 KB, 279 tokens by cl100k_base, as published. Nobody here has run it

DDD Tactical Patterns

Use this skill when

Translating domain rules into code structures.
Designing aggregate boundaries and invariants.
Refactoring an anemic model into behavior-rich domain objects.
Defining repository contracts and domain event boundaries.

Do not use this skill when

You are still defining strategic boundaries.
The task is only API documentation or UI layout.
Full DDD complexity is not justified.

Instructions

Identify invariants first and design aggregates around them.
Model immutable value objects for validated concepts.
Keep domain behavior in domain objects, not controllers.
Emit domain events for meaningful state transitions.
Keep repositories at aggregate root boundaries.

If detailed checklists are needed, open references/tactical-checklist.md.

Example

class Order {
  private status: "draft" | "submitted" = "draft";

  submit(itemsCount: number): void {
    if (itemsCount === 0) throw new Error("Order cannot be submitted empty");
    if (this.status !== "draft") throw new Error("Order already submitted");
    this.status = "submitted";
  }
}

Limitations

This skill does not define deployment architecture.
It does not choose databases or transport protocols.
It should be paired with testing patterns for invariant coverage.