software-design-ddd-domain-modeling

software-design-ddd-domain-modeling is a skill for Claude Code, Codex from xiaohei-info/oh-my-multica. It costs 43 tokens per session (1,984 once invoked), scanned A, original, MIT.

A guide for modeling the business areas inside a software system. It covers domain boundaries, bounded contexts, relationships between contexts, aggregates, and consistency boundaries; a bounded context is an area with its own clear meaning and rules.

In plain words
What is it for?
Use it to split a business into domains and subdomains, define context boundaries and translations, set aggregate boundaries, and reflect those decisions in architecture documents.
Why use it?
It helps resolve unclear business concepts and ownership before they cause conflicting models or consistency problems in the design.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to split a business into domains and subdomains, define context boundaries and translations, set aggregate boundaries, and reflect those decisions in architecture documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add xiaohei-info/oh-my-multica --skill software-design-ddd-domain-modeling
Clone the repo
git clone --depth 1 https://github.com/xiaohei-info/oh-my-multica

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for software-design-ddd-domain-modeling

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling/github.svg)](https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling)
Your own site
<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for software-design-ddd-domain-modeling

Your own site · 80×15
<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-ddd-domain-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,984 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01984
Opus 5 $0.00022 $0.00992
Sonnet 5 $0.00009 $0.00397
Haiku 4.5 $0.00004 $0.00198

Measured 12d ago against content hash b44ec7c8df98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

software-design-ddd-domain-modeling scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/omac/agents/architect/skills/software-design-ddd-domain-modeling/SKILL.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DDD Domain Modeling for Architecture

Overview

This skill is the architect-private domain modeling workflow for architecture design.

Use it when the real difficulty is not selecting middleware, but deciding:

  • how the business should be split into domains and subdomains
  • where bounded contexts should begin and end
  • how contexts relate and where translation / anti-corruption is needed
  • where aggregate and consistency boundaries should sit
  • how those modeling decisions should appear in 概要设计 or 详细设计 rather than staying as abstract DDD vocabulary

Core principle: domain modeling is not a theory appendix; it is a design tool for reducing semantic and consistency ambiguity before implementation.

This skill is intentionally narrower than the architect general playbook. It does not try to own the whole architecture delivery chain. It specializes in the part of architecture work where domain boundaries and model structure dominate the design outcome.

When to Use

Use when:

  • the architecture task is at 概要设计 or 详细设计 stage and domain boundaries are still unclear
  • the user asks about 领域 / 子域 / 限界上下文 / 上下文映射 / 聚合 / 事件风暴
  • the system has business complexity that cannot be explained well by component diagrams alone
  • service boundaries or ownership boundaries depend on language/model boundaries
  • multiple teams or subsystems disagree on concepts, state ownership, or consistency responsibility

Do not use when:

  • the main problem is only delivery packaging or stage planning
  • the task is only code-level refactor or implementation optimization
  • the problem is mostly diagram set choice with no meaningful domain ambiguity
  • the work is a tiny technical feature with no real business boundary question

Why This Skill Exists Separately

The architect general playbook answers:

  • what stages the design should go through
  • what artifacts should be produced
  • where risk should be front-loaded
  • how handoff happens

This skill answers a different question:

  • how to shape the semantic and consistency structure of the system before those artifacts are finalized

Read the full file on GitHub · 259 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 259 lines · 43 tokens per session scan A b44ec7c8df98

Subscribe to this mod's changes

software-design-ddd-domain-modeling is a skill published in the GitHub repository xiaohei-info/oh-my-multica (26 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 1,984 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.