Content
85%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-structured, actionable architecture skill with a phased workflow and explicit exit checkpoints, supported by real reference and script files. The only weaknesses are minor verbosity (metaphor + cheat-sheet restatement) and the lack of copy-paste code scaffolding.
Suggestions
Tighten conciseness by removing or shrinking the house metaphor and merging the 'Decision rules' cheat sheet into the relevant phases instead of restating them.
Improve actionability by adding a small copy-paste scaffolding snippet (e.g., a sample module folder tree with the suffix conventions) so the flat-by-aggregate layout can be reproduced without consulting the reference.
Consider adding one concrete before/after example of an ACL port + adapter interface signature in the body, so the core vendor-decoupling action is immediately executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely efficient and assumes Claude's competence (no basic explanations of DDD or circuit breakers), but the house metaphor and the 'Decision rules' cheat sheet restate content already covered in the phases and could be trimmed. It sits above the 'mostly efficient' anchor but not fully lean. | 4 / 5 |
Actionability | Gives concrete, executable guidance — validation commands (`node scripts/validate-structure.mjs [root]`), concrete folder layouts (`billing/subscription/`), file suffixes (`.entity.ts`), naming conventions (`module.aggregate.action`), and quantified thresholds (~10% retry budget). It is a design/instruction skill rather than a code skill, so the absence of full scaffolding code is the minor gap keeping it below 5. | 4 / 5 |
Workflow Clarity | A clear Phase 0–7 sequence where every phase has an explicit 'Exit:' checkpoint, plus an automated-checks section providing a validate→fix loop ('exit non-zero on violation and print the offending paths', blocking on structural failures). | 5 / 5 |
Progressive Disclosure | The body is an overview that points to one-level-deep references via two clear tables ('Core model' and 'Reference guide'); every referenced path (references/*.md, assets/architecture-template.html, scripts/*.mjs) resolves to a real bundle file, and the skill explicitly says to load references only when the current phase needs them. | 5 / 5 |
Total | 18 / 20 Passed |