Skip to content
TrustedSkillsbeta
Back to all skills

Domain Driven Design

Checked
bfollington·vlatest·backend·CC-BY-SA-4.0

Applies domain-driven design principles to AI agent architecture, ensuring alignment with business logic and complex problem domains.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bfollington/terma --skill domain-driven-design -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bfollington

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned bfollington/terma at 75e1bac231.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
75e1bac231
Manifest
plugins/tsal/skills/domain-driven-design/SKILL.md
Scanned
5 files, 2,809 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill equips AI agents with Domain-Driven Design (DDD) principles to structure complex software systems effectively. It enables agents to align technical architecture with business logic, ensuring codebases remain scalable and maintainable as requirements evolve.

When to use it

  • Refactoring legacy monolithic applications into modular microservices based on business capabilities.
  • Defining clear bounded contexts to isolate distinct business domains within a large codebase.
  • Generating domain models that accurately reflect real-world business rules rather than just database schemas.
  • Designing event-driven architectures where system components communicate through domain events.

Key capabilities

  • Identifying and modeling core domain entities and value objects.
  • Applying strategic design patterns like Ubiquitous Language and Bounded Contexts.
  • Structuring code to separate generic infrastructure concerns from specific business logic.
  • Facilitating communication between technical teams and non-technical stakeholders through shared terminology.

Example prompts

  • "Analyze this legacy customer service module and propose a Domain-Driven Design strategy to split it into bounded contexts."
  • "Generate a domain model for an inventory management system that strictly separates aggregate roots from value objects."
  • "Refactor this monolithic order processing script into microservices using event sourcing principles."

Tips & gotchas

  • DDD is most effective for complex business domains; avoid over-engineering simple CRUD applications.
  • Success relies heavily on establishing a Ubiquitous Language with stakeholders before writing code, as misaligned terminology leads to architectural drift.