Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-crafted, token-efficient skill body: crisp triggers and anti-triggers, a coherent five-step design workflow, an executable invariant example, and a properly signaled single reference that exists and is well organized. The main gaps are coverage (only the entity pattern has code) and the lack of an explicit validation/testing checkpoint in the workflow.
Suggestions
Add one short executable example for a value object (validation at construction, equality by value) and a domain event (e.g., `OrderSubmitted` with a minimal payload) so each directed pattern also has concrete form.
Add an explicit verification step to the workflow, e.g., "6. Confirm every invariant identified in step 1 has an enforcing test" instead of deferring this to Limitations.
The reference pointer could name the section a reader needs (e.g., 'open `references/tactical-checklist.md` for per-pattern checklists') — a small polish that makes navigation even more direct.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: no space is spent explaining what DDD is, what repositories are for, or how TypeScript works. Every section (Use when / Do not use when / Instructions / Example / Limitations) earns its place, matching the anchor "every token earns its place" — nothing to trim, so not 4. | 5 / 5 |
Actionability | Concrete, executable guidance dominates: imperative, specific directives ("Identify invariants first and design aggregates around them", "Keep repositories at aggregate root boundaries") plus a runnable TypeScript example enforcing invariants in `Order.submit`. Not 5 because only the entity pattern gets code — value objects, repositories, and domain events are directed but not exemplified, leaving coverage gaps; not 3 because what is provided is genuinely executable, not pseudocode. | 4 / 5 |
Workflow Clarity | The five instructions form a coherent, correctly ordered design workflow (invariants → value objects → behavior placement → events → repositories). Validation is only deferred ("should be paired with testing patterns for invariant coverage") rather than built in as a checkpoint, which keeps it below 5; this is a design-guidance skill, not a destructive/batch operation, so the validation cap does not apply, and the sequence is far too coherent for 3. | 4 / 5 |
Progressive Disclosure | The ~45-line body is cleanly sectioned and defers detail behind a single, clearly signaled, one-level-deep reference ("If detailed checklists are needed, open `references/tactical-checklist.md`"), which exists and contains exactly the promised checklists. No inlined bulk content and no nested references, matching the ideal structure; nothing to improve toward a different anchor. | 5 / 5 |
Total | 18 / 20 Passed |