Skills Guide

Domain-Driven Design

VerifiedSafe

Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/28/2026
Claude Code
#ddd#bounded-context#architecture#domain-modeling#cqrs

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

This skill acts as an entry point for planning Domain-Driven Design work: it checks whether DDD is warranted, produces strategic artifacts, then routes to specialized skills (context mapping, tactical patterns, CQRS, event sourcing, sagas).

Strengths

  • Includes an explicit viability check before committing to full DDD, guarding against over-engineering
  • Clearly separates strategic, tactical, and evented stages with expected artifacts
  • Provides a precise routing map to specialized skills depending on the current task
  • Enforces a structured output format (scope, assumptions, risks, next step)

Limitations

  • Does not generate code or framework-specific implementations
  • Does not substitute for workshops with real domain experts
  • Routing depends on the referenced companion skills being available
When to use it

Use it at the start of a business-heavy project to decide whether DDD is justified and to plan the artifacts for the next stages.

When not to use it

Avoid it for simple CRUD, localized bug fixes, or when no domain knowledge or product proxy is accessible.

Security analysis

Safe
Quality score86/100

This is a purely advisory, documentation-style skill that routes DDD work to other skills. It declares no allowed tools, contains no executable commands, no network or file operations beyond optionally opening a local reference file, and no credential handling or destructive instructions. Risk of listing it is minimal.

No concerns found

How this analysis is made

Examples

Viability assessment for a billing platform
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.
Model a logistics domain
We have three teams clashing over the same order model in our logistics system. Run @domain-driven-design to identify subdomains and bounded contexts, then tell me which skills to invoke for context mapping and tactical modeling.
Decide between CQRS and event sourcing
Our auditability requirements are strict and integration contracts keep changing. Use @domain-driven-design to check viability, then route us toward CQRS, event sourcing, or saga orchestration with the artifacts each stage requires.

name: domain-driven-design description: Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns. risk: safe source: self tags: [ddd, domain, bounded-context, architecture]

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

  1. Run a viability check before committing to full DDD.
  2. Produce strategic artifacts first: subdomains, bounded contexts, language glossary.
  3. Route to specialized skills based on current task.
  4. 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-architect and @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 files

This 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.md

From the root of a test project, save the file as .skill-downloads/domain-driven-design-ms47vpyb/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-ms47vpyb' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/domain-driven-design-ms47vpyb/download' --output '.skill-downloads/domain-driven-design-ms47vpyb/SKILL.md.part' && mv '.skill-downloads/domain-driven-design-ms47vpyb/SKILL.md.part' '.skill-downloads/domain-driven-design-ms47vpyb/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-ms47vpyb/SKILL.md' && test -s '.skill-downloads/domain-driven-design-ms47vpyb/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/domain-driven-design' && cp -R '.skill-downloads/domain-driven-design-ms47vpyb' '.claude/skills/domain-driven-design'

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 installation
openskills install './.skill-downloads/domain-driven-design-ms47vpyb'

openskills read 'domain-driven-design-ms47vpyb'

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 sync

Manual 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-ms47vpyb/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.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

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.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

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.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot