DDD Compliance Check
Two-mode DDD compliance validation for Java projects. Auto-detects mode from user's trigger phrase.
Mode Detection
| Trigger Phrases |
Mode |
Scope |
| "check my changes", "pre-commit", "review this code", "validate my code" |
Incremental |
git diff only |
| "full audit", "architecture review", "DDD compliance report", "check entire project", "pre-release" |
Full |
All Java files |
Incremental Mode
Workflow
- Find changed files:
git diff --cached --name-only --diff-filter=ACMR | grep '\.java$' (also check unstaged and HEAD diff)
- Classify by layer: Map package path to layer using layer rule files in
references/.
- Load relevant rules: Only load rule files matching changed layers. Always load
references/anti-patterns.md.
- Check each file: Validate structural rules (base class, package, naming), dependency rules (no forbidden imports), anti-patterns.
- Report: Per-file violations with severity and fix. Skip "looks good" for clean files.
If no Java files changed: "No Java files changed — nothing to check."
Full Mode
Workflow
- Discover:
find . -name "*.java" -not -path "*/target/*" -not -path "*/test/*" | sort
- Load all rules: Read every layer rule file in
references/. Load references/base-classes-reference.md and references/exception-handling.md as needed.
- Layer-by-layer audit: Group by layer, check package, base class, naming, dependencies, structure, exception mode.
- Cross-layer: Verify dependency direction (
grep -r "import org\.bookiosk\.ddd\."), detect anemic models, check exception boundaries.
- Report: Executive summary with compliance score, per-layer breakdown, anti-patterns section, dependency graph, ranked recommendations.
See examples/violation-report.md for sample output.
Layer Checklists
See references/shared-checks.md for the complete severity table (CRITICAL/HIGH/MEDIUM/LOW) and per-layer checklists.
Red Flags
These thoughts mean STOP — you're about to make a mistake:
| Thought |
Reality |
| "This import looks wrong but the code compiles" |
Compilation ≠ architecture compliance. Check the layer dependency rules. |
| "It's just one setter, what's the harm?" |
Public setId on aggregates breaks identity protection. Every violation matters. |
| "I'll skip the cross-layer check, the file looks fine" |
Domain→infrastructure imports are invisible without explicit grep. |
| "This exception pattern is different but it works" |
Wrong exception mode breaks the entire error handling contract. |
| "The design pattern makes the code cleaner" |
Design patterns in domain layer are FORBIDDEN — no exceptions. |
| "I'll report 'looks good' for files with no issues" |
Only report problems. Silence means clean. |
| "A perfect score isn't possible, so I'll be lenient" |
Architectural decay accelerates. Flag every real violation. |
Common Mistakes
- Flagging intentional violations as CRITICAL — verify with author before escalating
- Skipping cross-layer dependency check — domain→infrastructure is the #1 architecture decay vector
- Ignoring exception mode mismatch — 阻断型 layer throwing to 分支型 caller breaks error handling contract
- Incremental mode checking unchanged files — only touch
git diff output
Quality Checklist
Before finalizing:
1---2name: ddd-check3description: DDD compliance check for Java projects with auto mode detection. Use when user mentions "DDD check", "DDD audit", "check my changes", "architecture review", "pre-commit check", "DDD compliance", "review this code", or "check entire project".4license: Apache-2.05---6
7# DDD Compliance Check
8
9Two-mode DDD compliance validation for Java projects. Auto-detects mode from user's trigger phrase.
10
11## Mode Detection
12
13| Trigger Phrases | Mode | Scope |
14|---|---|---|
15| "check my changes", "pre-commit", "review this code", "validate my code" | **Incremental** | `git diff` only |
16| "full audit", "architecture review", "DDD compliance report", "check entire project", "pre-release" | **Full** | All Java files |
17
18## Incremental Mode
19
20### Workflow
21
221. **Find changed files**: `git diff --cached --name-only --diff-filter=ACMR | grep '\.java$'` (also check unstaged and HEAD diff)
232. **Classify by layer**: Map package path to layer using layer rule files in `references/`.
243. **Load relevant rules**: Only load rule files matching changed layers. Always load `references/anti-patterns.md`.
254. **Check each file**: Validate structural rules (base class, package, naming), dependency rules (no forbidden imports), anti-patterns.
265. **Report**: Per-file violations with severity and fix. Skip "looks good" for clean files.
27
28If no Java files changed: "No Java files changed — nothing to check."
29
30## Full Mode
31
32### Workflow
33
341. **Discover**: `find . -name "*.java" -not -path "*/target/*" -not -path "*/test/*" | sort`
352. **Load all rules**: Read every layer rule file in `references/`. Load `references/base-classes-reference.md` and `references/exception-handling.md` as needed.
363. **Layer-by-layer audit**: Group by layer, check package, base class, naming, dependencies, structure, exception mode.
374. **Cross-layer**: Verify dependency direction (`grep -r "import org\.bookiosk\.ddd\."`), detect anemic models, check exception boundaries.
385. **Report**: Executive summary with compliance score, per-layer breakdown, anti-patterns section, dependency graph, ranked recommendations.
39
40See `examples/violation-report.md` for sample output.
41
42## Layer Checklists
43
44See `references/shared-checks.md` for the complete severity table (CRITICAL/HIGH/MEDIUM/LOW) and per-layer checklists.
45
46## Red Flags
47
48These thoughts mean STOP — you're about to make a mistake:
49
50| Thought | Reality |
51|---|---|
52| "This import looks wrong but the code compiles" | Compilation ≠ architecture compliance. Check the layer dependency rules. |
53| "It's just one setter, what's the harm?" | Public setId on aggregates breaks identity protection. Every violation matters. |
54| "I'll skip the cross-layer check, the file looks fine" | Domain→infrastructure imports are invisible without explicit grep. |
55| "This exception pattern is different but it works" | Wrong exception mode breaks the entire error handling contract. |
56| "The design pattern makes the code cleaner" | Design patterns in domain layer are FORBIDDEN — no exceptions. |
57| "I'll report 'looks good' for files with no issues" | Only report problems. Silence means clean. |
58| "A perfect score isn't possible, so I'll be lenient" | Architectural decay accelerates. Flag every real violation. |
59
60## Common Mistakes
61
62- **Flagging intentional violations as CRITICAL** — verify with author before escalating
63- **Skipping cross-layer dependency check** — domain→infrastructure is the #1 architecture decay vector
64- **Ignoring exception mode mismatch** — 阻断型 layer throwing to 分支型 caller breaks error handling contract
65- **Incremental mode checking unchanged files** — only touch `git diff` output
66
67## Quality Checklist
68
69Before finalizing:
70- [ ] Mode correctly detected from user's trigger phrase
71- [ ] Only relevant rule files loaded (incremental) or all layers covered (full)
72- [ ] Every violation references the specific rule file and section heading
73- [ ] Each violation includes the exact fix, not just the problem
74- [ ] CRITICAL issues listed first, prioritized by blast radius
75- [ ] Anti-patterns cross-checked against `references/anti-patterns.md`
aiskillstore