Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/ddd/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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.
[](https://agentmods.dev/skills/dgouron/review-flow/ddd)<a href="https://agentmods.dev/skills/dgouron/review-flow/ddd"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/ddd/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.
<a href="https://agentmods.dev/skills/dgouron/review-flow/ddd"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/ddd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00044 | $0.01361 |
| Opus 5.5 | $0.00018 | $0.00544 |
| Sonnet 5.5 | $0.00009 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain-Driven Design - Strategic Guide
Persona
Read .claude/roles/architect.md — adopt this profile and follow all its rules.
Activation
This skill activates for high-level domain decisions:
- Splitting into Bounded Contexts
- Defining the Ubiquitous Language
- Creating a new business module
- Analyzing relationships between contexts
Important clarification
Clean Architecture definitions take precedence over DDD tactical definitions.
We use DDD only at the strategic level (domain splitting, language). Tactical patterns (Entities, Use Cases, Gateways, Presenters) follow Clean Architecture.
| What we take from DDD | What we do NOT take |
|---|---|
| Bounded Contexts | Aggregates |
| Ubiquitous Language | Repositories (we have Gateways) |
| Context Mapping | Domain Events |
| Module splitting | Complex Value Objects |
Bounded Context
"A Bounded Context delimits the applicability of a particular model." — Eric Evans
A Bounded Context = a module in modules/<context-name>/
Each BC is an autonomous package with its own public API.
Identifying a Bounded Context
Signs that a new BC is needed:
- The same term has different meanings depending on context
- A different team could manage this part
- The model is becoming too complex
- Business rules are diverging
ReviewFlow example:
| Bounded Context | Responsibility |
|---|---|
review |
Code review orchestration and result handling |
tracking |
MR/PR assignment tracking and follow-up |
webhook |
Inbound webhook processing (GitLab/GitHub) |
mcp |
Model Context Protocol server and tools |
dashboard |
Review statistics and visualization |
security |
Secret detection and access control |
Communication between Bounded Contexts
BCs communicate via their public APIs, like two independent packages.
// modules/tracking/index.ts (public API)
export { TrackAssignmentUseCase } from "./application/usecases/trackAssignment.usecase"
export { createTrackedMr } from "./domain/factories/trackedMrFactory"
export type { TrackingGateway } from "./application/ports/gateways/trackingGateway"
// modules/review/ imports from the public API
import { TrackAssignmentUseCase } from "@/modules/tracking"
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.
- 2mo ago First seen · 228 lines · 44 tokens per session scan A 2564e390482a
ddd is a skill published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,361 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
code-changes
Workflow for any task that ends in code changes: issue analysis or triage, pull request review comments, features, bug fixes, refactors. Invoke at the start of such a task, before reading or writing code.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-debt
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what…