angular-ddd

A set of Domain-Driven Design guidelines for building business logic in Angular and TypeScript. Domain-Driven Design is an approach that models software around the rules and concepts of the business.

In plain words
What is it for?
Use it when creating or reviewing domain models, aggregates, value objects, repositories, domain services, bounded contexts, or domain events.
Why use it?
It provides consistent patterns for keeping business rules explicit, protected, and testable instead of scattering them through application code.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/fmflurry/settings-opencode/angular-ddd
Any agent
npx skills add fmflurry/settings-opencode --skill angular-ddd
Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

Made for: Claude Code, Codex.

Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,387 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00141 $0.02387
Opus 5 $0.00071 $0.01193
Sonnet 5 $0.00028 $0.00477
Haiku 4.5 $0.00014 $0.00239

Measured yesterday against content hash 78156eda049e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

angular-ddd 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 yesterday.

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.

.claude/skills/angular-ddd/SKILL.md · 139 lines

How it starts

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

angular-ddd

Domain-Driven Design guidance for Angular/TypeScript domain code. Makes DDD principles explicit and enforceable for the coder and code-reviewer agents.

When to Activate

  • Creating or modifying domain models (entities, value objects, aggregates)
  • Adding repositories, factories, or domain services
  • Defining or refactoring bounded contexts
  • Reviewing domain code for DDD compliance
  • Refactoring anemic models toward rich behavior
  • Enforcing aggregate invariants or encapsulation rules

Provenance

Content is synthesized from established DDD literature:

  • Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software (2003) — "Blue Book"
  • Vaughn Vernon, Implementing Domain-Driven Design (2013) — "Red Book"
  • Martin Fowler, bliki articles on Anemic Domain Model, Domain Event, etc.
  • TypeScript-specific idioms: branded types, discriminated unions, readonly, Object.freeze

This is a practitioner synthesis, not a verbatim reproduction. Where sources disagree, the Red Book's pragmatic guidance takes precedence for implementation details.

Core Principles

  1. The domain model is the software. Business logic lives in domain objects and pure functions, not in services or components. (Evans, ch. 1)
  2. Ubiquitous Language. Code names match the domain expert's vocabulary. No translation layer between business and code. (Evans, ch. 2)
  3. Bounded Contexts define boundaries. Each context owns its model. Shared types across contexts are a design smell. (Evans, ch. 14)
  4. Aggregates enforce invariants. All mutations go through the aggregate root. External code never reaches inside. (Vernon, ch. 10)
  5. Value Objects are immutable and identity-free. They describe characteristics, not things. (Evans, ch. 5)
  6. Repositories return aggregates, not tables. Persistence is an infrastructure concern. (Vernon, ch. 12)

TypeScript Idioms

The Angular-specific delta vs. the .NET DDD skill:

Concept .NET idiom TypeScript idiom
Identity CustomerId record struct Branded type: type CustomerId = string & { readonly __brand: 'CustomerId' }
Immutability readonly record struct readonly props + Object.freeze() for VOs; ReadonlyArray<T> for collections
Domain events sealed record : IDomainEvent Discriminated union with readonly kind discriminant
Domain model sealed class with private setters type alias with readonly props (per [[angular-clean-architecture]] convention)
Domain rules Static methods on entity Pure exported functions in core/rules/
Ports interface in Core abstract class with abstract methods returning Observable<T> (per [[angular-clean-architecture]] convention)
Equality Equals/GetHashCode override Structural: compare all fields; identity: compare id field

Read the full file on GitHub · 139 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 139 lines · 141 tokens per session scan A 78156eda049e

Subscribe to this mod's changes

angular-ddd is a skill published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 141 tokens to every session and 2,387 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens