Skills ddd-tactical-patterns

📦

ddd-tactical-patterns

Name: ddd-tactical-patterns
Author: sickn33

Content revision r2 Safe ⚙️ External commands

Design Domain Models with DDD Tactical Patterns

Domain rules often become scattered across controllers and persistence code. This skill structures them with aggregates, value objects, repositories, and domain events.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "ddd-tactical-patterns" from https://skillstore.io/skills/sickn33-ddd-tactical-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-ddd-tactical-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-ddd-tactical-patterns.md Signed manifest GET /api/skills/sickn33-ddd-tactical-patterns/manifest Signed lockfile GET /api/skills/sickn33-ddd-tactical-patterns/lockfile

Test it

Using "ddd-tactical-patterns". Model order submission where an order must contain items and may be submitted once.

Expected outcome:

Aggregate root: Order. Invariants: at least one item and draft status. Transition: submit. Event: OrderSubmitted.

Using "ddd-tactical-patterns". Review a service that validates money values and directly saves ORM records.

Expected outcome:

Introduce an immutable Money value object. Move validation into construction. Define a repository interface that persists aggregate roots without exposing ORM entities.

Using "ddd-tactical-patterns". Choose consistency boundaries for inventory reservation and payment authorization.

Expected outcome:

Keep each capability in its own aggregate. Publish stable domain events and coordinate eventual consistency outside both aggregate roots.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All five static findings are false positives caused by ordinary DDD prose, Markdown backticks, and a fenced TypeScript example. The skill contains no executable shell command, system reconnaissance, prompt injection, or other harmful intent.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (2)

SKILL.md:33 SKILL.md:37-47

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-ddd-tactical-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-ddd-tactical-patterns/security.svg)](https://skillstore.io/skills/sickn33-ddd-tactical-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-ddd-tactical-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-ddd-tactical-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-ddd-tactical-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). ddd-tactical-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-ddd-tactical-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-ddd-tactical-patterns-2026,
  author = {sickn33},
  title = {ddd-tactical-patterns security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-ddd-tactical-patterns/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ddd-tactical-patterns security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-ddd-tactical-patterns/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-ddd-tactical-patterns:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Model a New Business Workflow

Translate workflow rules into aggregates, value objects, methods, and domain events.

Refactor an Anemic Domain Model

Move business rules from controllers and services into behavior-rich domain objects.

Review Tactical DDD Boundaries

Assess aggregate consistency, repository scope, value semantics, and event payload design.

Try These Prompts

Identify the Core Invariants

Review this business rule set: [rules]. List the invariants, affected concepts, and state transitions before proposing any classes.

Design an Aggregate

Design an aggregate for [workflow]. Define its root, entities, value objects, invariants, commands, and meaningful domain events.

Refactor a Domain Model

Review this model: [model description]. Find anemic behavior, misplaced rules, persistence leakage, and weak boundaries. Propose a focused tactical DDD refactor.

Evaluate Cross-Aggregate Consistency

Analyze these aggregates and transaction requirements: [details]. Separate immediate invariants from eventual consistency. Recommend repository and domain event boundaries with tradeoffs.

Best Practices

State invariants explicitly before selecting entities or aggregate boundaries.
Keep transactions within one aggregate whenever business rules permit.
Pair each modeled invariant with focused automated tests.

Avoid

Do not place core business rules only in controllers or application services.
Do not expose persistence models as domain entities.
Do not require synchronous consistency across unrelated aggregates without a proven invariant.

Frequently Asked Questions

What tactical patterns does this skill cover?

It covers entities, value objects, aggregates, repositories, domain events, and explicit invariant enforcement.

Does this skill define bounded contexts?

No. Establish strategic boundaries before applying these tactical patterns.

Can it choose a database or ORM?

No. It keeps domain design separate from database and ORM selection.

When should I avoid full DDD?

Avoid it when the domain is simple and tactical abstractions add more complexity than value.

How should repositories be scoped?

Define repositories around aggregate roots and expose operations in domain language.

How should domain events be designed?

Use past-tense names, minimal stable payloads, and versioned schemas for breaking changes.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/ddd-tactical-patterns

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

10 downloads · 101 views

File structure

📁 references/

📄 tactical-checklist.md

📄 SKILL.md