Content
78%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 lean, highly directive design-policy skill with specific thresholds, explicit do/don't rules, and a closing review checklist. The one structural defect is the orphaned bundle reference: references/visual-direction.md exists but no section of the body ever points to it.
Suggestions
Link the reference from the body where it is relevant, e.g. in 'Choose a direction': "For a new app with no established brand, work through [references/visual-direction.md](references/visual-direction.md) and record the result in DESIGN.md."
Make the build sequence explicit as a short ordered flow (direction → build → review) so the section order reads as a process rather than a topic list.
Add one compact before/after sketch of a focused starting view to make the abstract directives ('Every visible element should orient the user...') concrete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense directive prose with no padding and no explanations of concepts Claude already knows — e.g., "Never use browser `alert`, `confirm`, or `prompt` dialogs", "Density should come from useful data, not extra chrome", "aiming for 100 ms". Every sentence is product-specific policy, so every token earns its place. | 5 / 5 |
Actionability | For an instruction-only skill the guidance is largely concrete and executable: explicit do/don't lists ("Do not add a page title that repeats the selected navigation item, a subtitle or eyebrow under a title, a count strip..."), numeric thresholds ("aiming for 100 ms", "within 400 ms"), and routing rules ("Read `shadcn-ui` when implementing or composing a standard control"). It stops short of 5 because some directives remain abstract judgment calls ("Pick a visual direction that fits the product's brand and domain") with no compact good-vs-bad example to anchor them. | 4 / 5 |
Workflow Clarity | The sections form a coherent implicit sequence — choose a direction, build the focused view, use the design system, coordinate with the agent, then an explicit validation pass: "Check that the main job and next action are obvious. Look at the default, loading, empty, error, and success states... and check a narrow viewport." It is below 5 because the sequence is implicit (no ordered steps) and there is no feedback loop instructing what to do when the review finds problems. | 4 / 5 |
Progressive Disclosure | The body itself is well organized at the right altitude (~93 lines, clear section headers), but the bundle contains references/visual-direction.md (102 lines of direction-choosing guidance) that is never linked or mentioned anywhere in SKILL.md, so it is undiscoverable rather than merely 'not clearly signaled'. This matches the level-3 anchor ('references present but not clearly signaled') and is above level 2 because nothing that belongs in a separate file is inlined. | 3 / 5 |
Total | 16 / 20 Passed |