Skip to content
Agentmart
Submit a tool

domain-driven-design

Model business rules, aggregates, bounded contexts or domain terminology in an existing or new application.

Skill by atstaeff

IndexedMIT★ 3
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/atstaeff-domain-driven-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Model business rules, aggregates, bounded contexts or domain terminology in an existing or new application.

Use cases: design

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/domain-driven-design

What's inside

Skill name
domain-driven-design
Description
Model business rules, aggregates, bounded contexts or domain terminology in an existing or new application.
License
MIT
Instructions
15 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • domain-driven-design.md · references/

SKILL.md (first lines)

# Domain Driven Design

## Workflow

1. Build a small shared vocabulary from real user scenarios. Put business invariants close to the data they protect.
2. Define boundaries by behavior and ownership, not by copying database tables. Start with modules before distributed services.
3. Use dataclasses and explicit validation for new Python domain objects; use the project's established validation library at external boundaries.
4. Introduce aggregates, repositories or domain events only when they simplify invariants, persistence or a real integration.
5. Test business behavior without infrastructure; record the few decisions that constrain future changes.

## Focused references

- [Detailed examples](references/domain-driven-design.md): load only the section relevant to the task.

From atstaeff/ai-agents, MIT.

More from atstaeff/ai-agents

Signals

Stars
3
Forks
0
Open issues
0
Last commit (this folder)
Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from atstaeff

Cite this page

domain-driven-design skill. Agent Mart. https://agentmart.dev/skills/atstaeff-domain-driven-design (last updated 2026-10-24)