Automated summary
This skill applies Domain-Driven Design tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants.
Strengths
- Guides translating domain rules into robust code structures.
- Promotes aggregate design with explicit invariants.
- Encourages rich domain objects over anemic models.
- Defines clear boundaries for repositories and domain events.
Limitations
- Does not cover deployment architecture or database selection.
- Does not address transport protocols or infrastructure choices.
- Should be paired with testing patterns to ensure invariant coverage.
Use this skill when translating domain rules into code structures, designing aggregate boundaries, or refactoring an anemic model into behavior-rich domain objects.
Do not use if you are still defining strategic boundaries, the task is only API documentation or UI layout, or full DDD complexity is not justified.
Security analysis
SafeThe skill contains only instructional text about DDD tactical patterns and a static TypeScript example. It does not instruct any file system operations, network calls, or execution of commands, and there is no declared tool usage.
No concerns found
How this analysis is madeExamples
Help me design an Order aggregate in TypeScript with invariants: order must have at least one item, can only be submitted once, and status transitions are validated.Refactor this User class to follow DDD patterns: make it an entity with behavior, validate email as a value object, and emit a UserRegistered event.name: ddd-tactical-patterns description: Apply DDD tactical patterns in code using entities, value objects, aggregates, repositories, and domain events with explicit invariants. risk: safe source: self tags: [ddd, tactical, aggregates, value-objects, domain-events]
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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ddd-tactical-patterns-mm78nogq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ddd-tactical-patterns-mm78nogq/download' --output '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md.part' && mv '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md.part' '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md' && test -s '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ddd-tactical-patterns' && cp -R '.skill-downloads/ddd-tactical-patterns-mm78nogq' '.claude/skills/ddd-tactical-patterns'Cursor
test -f '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md' && test -s '.skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ddd-tactical-patterns' && cp -R '.skill-downloads/ddd-tactical-patterns-mm78nogq' '.cursor/skills/ddd-tactical-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ddd-tactical-patterns-mm78nogq'openskills read 'ddd-tactical-patterns-mm78nogq'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ddd-tactical-patterns-mm78nogq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.