Content
77%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 consultant skill with an excellent phased workflow, strong validation checkpoints, and clean progressive disclosure to verified reference files. Its main weakness is conciseness — overlapping sections and consultant framing add length — and the absence of any concrete frontend code example in the build phase.
Suggestions
Consolidate 'What This Skill is NOT' and 'Expert Behavior Guidelines' with Core Principles to remove overlap and cut roughly 30-40 lines of redundant framing.
Add one short, concrete frontend code snippet (e.g., a design-token CSS custom properties block matching the Design Direction template) to the Atomic Build phase so the central deliverable is executable, not just instructional.
Trim consultant-voice aphorisms ('every token spent on discovery saves 10x in rework') that do not change behavior.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient in places but carries redundancy — 'What This Skill is NOT' restates Core Principles in negative form and 'Expert Behavior Guidelines' overlaps 'Opinionated guidance', plus consultant framing like 'A wrong first draft wastes more time than 2 minutes of discovery' could be trimmed. Not below midpoint: the content is mostly high-value and well-organized rather than padded with concepts Claude already knows. | 3 / 5 |
Actionability | Provides concrete executable guidance: Stitch MCP calls (create_project, generate_screen_from_text, generate_variants, edit_screens, get_screen), a copy-paste Design Direction Summary template, and a prompt formula. Falls short of 5 only because the actual code-generation phase offers no concrete frontend code example, leaving the central deliverable abstract. | 4 / 5 |
Workflow Clarity | The 7-phase workflow is clearly sequenced with explicit validation checkpoints at each transition — 'Do not proceed to Phase 3 until you have at least ONE concrete visual reference', 'Wait for explicit approval', and 'Does this match your vision?' — plus a feedback loop requiring changes to the current unit before advancing. | 5 / 5 |
Progressive Disclosure | The body is an overview that defers deep dives to three real, verified one-level-deep references (design-principles.md, collection-guide.md, stitch-integration.md), each clearly signaled in a Reference Files section with load-on-demand timing guidance, making navigation easy. | 5 / 5 |
Total | 17 / 20 Passed |