Content
57%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of DDD tactical patterns with good scoping sections and one solid code example. However, it falls short on actionability by only demonstrating one pattern (aggregate invariant enforcement) while leaving value objects, repositories, and domain events as abstract bullet points. The workflow lacks validation steps and the referenced checklist file doesn't exist in the bundle.
Suggestions
Add concrete code examples for value objects, repository interfaces, and domain events—not just the aggregate pattern—to make the skill actionable across all claimed patterns.
Include a validation/verification step in the workflow, such as 'Run domain model tests to verify invariants hold' or a checklist for reviewing aggregate boundaries.
Either provide the referenced `references/tactical-checklist.md` file in the bundle or inline the essential checklist items directly in the skill.
Tighten the instructions from abstract principles ('Keep domain behavior in domain objects') into specific, executable guidance (e.g., show a before/after refactoring from anemic to rich model).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and assumes Claude's competence with DDD concepts. The 'Use this skill when' and 'Do not use this skill when' sections add some bulk but are reasonable scoping. Minor verbosity in the Limitations section stating obvious negatives. | 4 / 5 |
Actionability | The instructions are high-level principles rather than concrete, executable guidance. The TypeScript example is good and executable for one pattern (aggregate with invariant), but value objects, repositories, and domain events are only mentioned abstractly without concrete code examples. Key patterns are described rather than demonstrated. | 3 / 5 |
Workflow Clarity | The five numbered steps provide a rough sequence for applying tactical patterns, but there are no validation checkpoints, no feedback loops for verifying that invariants are correctly modeled, and no explicit verification steps. For a skill involving refactoring and structural changes, the absence of validation guidance is notable. | 3 / 5 |
Progressive Disclosure | References `references/tactical-checklist.md` for detailed checklists, which is good progressive disclosure intent. However, no bundle files are provided, so the reference is a dead link. The skill itself is reasonably structured with clear sections, but the single reference to a non-existent file weakens the score. | 3 / 5 |
Total | 13 / 20 Passed |