Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, directive, validation-rich design skill that assumes Claude's competence and sequences work clearly with a handoff checklist. Its main gap is actionability at the implementation level: it directs technically deep GSAP/Three.js/smooth-scroll operations without concrete code or patterns.
Suggestions
Add a concise, copy-paste code pattern for GSAP ScrollTrigger integration with the chosen smooth-scroll engine (including the refresh-after-media/fonts step and reduced-motion bypass), so the 'connect the chosen engine correctly' directive is executable rather than descriptive.
Provide a minimal Three.js cleanup/disposal block (cancel animation frame, dispose geometries/materials/render targets/textures/renderer, handle context loss) to make the disposal checklist concrete.
Show one short reduce-motion bypass example that renders final states immediately under prefers-reduced-motion: reduce, illustrating the 'render final states immediately' rule for the hardest-to-get-right case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive throughout, assuming Claude's competence (it never explains what GSAP, Three.js, or smooth-scroll engines are) and packing each bullet with actionable guidance; not a 2 because there is no unnecessary concept explanation or padding that could be tightened. | 3 / 3 |
Actionability | Guidance names concrete tools and rules ('Use GSAP', 'choose exactly one' of Lenis/Locomotive, 'Dispose animation frames, observers... render targets, textures, geometries, materials, and the renderer'), but for technically deep directives like ScrollTrigger integration, Three.js/WebGL setup, and reduce-motion bypass it gives no concrete code or implementation patterns, leaving key HOW-details unspecified; not a 1 because the named-tool directives are specific and actionable at the design level, and not a 3 because no executable examples or copy-paste patterns are provided. | 2 / 3 |
Workflow Clarity | The body is a numbered §1–§7 sequence culminating in a dedicated 'Validate before handoff' section with an explicit checklist and a 'Run the production build and fix every failure' feedback loop, matching the anchor for a clear sequence with explicit validation and error-recovery; not a 2 because validation checkpoints are explicit, not merely implicit. | 3 / 3 |
Progressive Disclosure | There are no bundle files (references/scripts/assets are absent) and the skill is self-contained, but it is well-organized into seven clearly titled sections with a framing intro; per the rubric's simple-skills note, a self-contained skill with no need for external references can score 3 on well-organized sections, and there are no nested references to penalize. | 3 / 3 |
Total | 11 / 12 Passed |