Content
86%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 tight, well-organized ruleset that assumes competence and gives concrete, executable preset guidance. Its only soft spots are prose-only per-preset usage and an unexplained 'WP3b+' phase token that slightly muddies the message-streaming guidance.
Suggestions
Add a minimal copy-paste usage snippet for one or two presets (e.g. sharedAxisPush with AnimatePresence) so the most common case is fully executable, not just described.
Briefly decode 'WP3b+' (e.g. a one-line note on what that project phase refers to) or drop the phase label so the message-streaming rule stands on its own.
For the 'add a new pattern to presets.ts' workflow, note a quick self-check (e.g. exported preset + doc comment present, reduced-motion variant included) to give it an explicit checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and declarative throughout ('Components never define their own durations, easings, or springs'; 'animate transform/opacity only'); assumes Claude's competence and never explains basic concepts, so every token earns its place. | 5 / 5 |
Actionability | Provides a concrete hook import/destructure plus named APIs and specific values (custom={1}/{-1}, AnimatePresence wrapping), but only the import line is fully copy-paste ready while per-preset usage is conveyed in prose. | 4 / 5 |
Workflow Clarity | The single action (use useMotionPresets(); add new patterns INTO presets.ts with a doc comment) is unambiguous, but the 'WP3b+' phase token is unexplained and there is no validation checkpoint for the add-a-preset workflow. | 4 / 5 |
Progressive Disclosure | Under 50 lines with no bundle files and no need for external references, organized under clear headers ('## The presets', '## Rules'), meeting the simple-skill bar for a 5. | 5 / 5 |
Total | 18 / 20 Passed |