Automated summary
This skill assesses whether full Domain-Driven Design is worth adopting, then plans and routes DDD work from strategic modeling through tactical implementation and evented architecture.
Strengths
- Provides an explicit viability checklist (complex or fast-changing rules, cross-team model collisions, unstable contracts, auditability) before committing to DDD
- Sequences the work: strategic artifacts (subdomains, bounded contexts, glossary) before tactical patterns
- Includes a routing map to specialized skills (context mapping, CQRS, event sourcing, sagas, projections, ADRs)
- Enforces a consistent output format: scope, current stage, artifacts produced, open risks and next step
Limitations
- It is a planning and routing skill: it does not generate framework-specific code or the in-depth DDD manual (delegated to another skill)
- Heavily depends on real access to domain experts, which it cannot replace
- References companion skills (@ddd-strategic-design, @cqrs-implementation, etc.) that must exist in the environment
Use it at the start of a business-heavy project to decide whether full DDD is justified and to lay out the modeling stages.
Avoid it for simple CRUD, localized bug fixes, or when no domain knowledge or product proxy is available.
Security analysis
SafeThe skill is pure planning guidance: no declared tools, no executable commands, no network calls, no file writes, and no handling of secrets or credentials. It only instructs the agent to reason about DDD adoption and route to other named skills, so there is no meaningful execution risk. The only structural note is that it references an auxiliary file (references/ddd-deliverables.md) and @-style skill handles, which are inert text references.
No concerns found
How this analysis is madeExamples
Use the domain-driven-design-planner skill to assess whether our billing platform should adopt full DDD. Run the viability check, then tell me which specialized skill to route to and which artifacts we must produce this week.We have three teams colliding on the same order model. Use the domain-driven-design-planner skill to produce subdomains, bounded contexts and a language glossary, then recommend the next step toward tactical patterns.Our audit requirements are strict and integration contracts keep changing. Use the domain-driven-design-planner skill to decide if event sourcing and CQRS are warranted, and route the work to the right skills with a staged plan.name: domain-driven-design-planner description: "Decide whether full DDD is worth it, then plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture (CQRS, event sourcing, sagas, projections). Use for the up-front viability check and staged planning; for the in-depth DDD manual (bounded contexts, aggregates, ubiquitous language, repositories) use domain-driven-design." risk: safe source: "sickn33/antigravity-awesome-skills" tags: "[ddd, domain, bounded-context, architecture]" date_added: "2026-02-27"
Domain-Driven Design
Use this skill when
- You need to model a complex business domain with explicit boundaries.
- You want to decide whether full DDD is worth the added complexity.
- You need to connect strategic design decisions to implementation patterns.
- You are planning CQRS, event sourcing, sagas, or projections from domain needs.
Do not use this skill when
- The problem is simple CRUD with low business complexity.
- You only need localized bug fixes.
- There is no access to domain knowledge and no proxy product expert.
Instructions
- Run a viability check before committing to full DDD.
- Produce strategic artifacts first: subdomains, bounded contexts, language glossary.
- Route to specialized skills based on current task.
- Define success criteria and evidence for each stage.
Viability check
Use full DDD only when at least two of these are true:
- Business rules are complex or fast-changing.
- Multiple teams are causing model collisions.
- Integration contracts are unstable.
- Auditability and explicit invariants are critical.
Routing map
- Strategic model and boundaries:
@ddd-strategic-design - Cross-context integrations and translation:
@ddd-context-mapping - Tactical code modeling:
@ddd-tactical-patterns - Read/write separation:
@cqrs-implementation - Event history as source of truth:
@event-sourcing-architectand@event-store-design - Long-running workflows:
@saga-orchestration - Read models:
@projection-patterns - Decision log:
@architecture-decision-records
If templates are needed, open references/ddd-deliverables.md.
Output requirements
Always return:
- Scope and assumptions
- Current stage (strategic, tactical, or evented)
- Explicit artifacts produced
- Open risks and next step recommendation
Examples
Use @domain-driven-design to assess if this billing platform should adopt full DDD.
Then route to the right next skill and list artifacts we must produce this week.
Limitations
- This skill does not replace direct workshops with domain experts.
- It does not provide framework-specific code generation.
- It should not be used as a justification to over-engineer simple systems.
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/domain-driven-design-planner-msh3utlp/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/domain-driven-design-planner-msh3utlp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/domain-driven-design-planner-msh3utlp/download' --output '.skill-downloads/domain-driven-design-planner-msh3utlp/SKILL.md.part' && mv '.skill-downloads/domain-driven-design-planner-msh3utlp/SKILL.md.part' '.skill-downloads/domain-driven-design-planner-msh3utlp/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/domain-driven-design-planner-msh3utlp/SKILL.md' && test -s '.skill-downloads/domain-driven-design-planner-msh3utlp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/domain-driven-design-planner' && cp -R '.skill-downloads/domain-driven-design-planner-msh3utlp' '.claude/skills/domain-driven-design-planner'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/domain-driven-design-planner-msh3utlp'openskills read 'domain-driven-design-planner-msh3utlp'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/domain-driven-design-planner-msh3utlp/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.