Content
88%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.
The body is a dense, executable pattern catalog with strong decision guidance and explicit rules, assuming Claude's competence throughout. The main gap is progressive disclosure: heavy code is inlined with no reference files to split it.
Suggestions
Move the larger full implementations (modal, toast stack, end-to-end list example) into files under references/ and link to them one level deep, keeping only compact illustrations inline in SKILL.md.
Consider extracting the rules + anti-patterns table into a references/RULES.md so the main body can stay a lean overview plus quick-start patterns.
If a token/spring quick-reference is useful, place it in references/TOKENS.md rather than relying entirely on the sibling motion-foundations skill being loaded.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Assumes Claude's competence — no padding explaining what motion or React is — and every line earns its place, though the body is long because it inlines many full code blocks rather than offloading some to reference files. | 4 / 5 |
Actionability | Provides fully executable, copy-paste TSX for button, stagger, modal, toast, page transition, scroll reveal, scroll progress, expanding card, shared-element crossfade, accordion, plus an end-to-end example. | 5 / 5 |
Workflow Clarity | A pattern catalog rather than a destructive/batch workflow; decision tables ('Choosing the right pattern', 'mode=wait vs sync'), eight explicit numbered rules, and an anti-pattern table with fixes make each single action unambiguous. | 5 / 5 |
Progressive Disclosure | Well-organized into clear sections with no nested references, but no bundle/reference files exist and substantial full implementations (modal, toast, end-to-end example) are inlined that could live one level deep in a references/ directory. | 4 / 5 |
Total | 18 / 20 Passed |