Content
82%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 high-quality, highly actionable reference: comprehensive executable Framer Motion/GSAP/reduced-motion code, principled design rules ('Quando NAO Animar', flash/vestibular safety limits), and well-signaled one-level-deep bundle references. The main costs are length (~730 lines with sections that could be offloaded to references) and prose that re-explains concepts (FLIP, library internals) Claude already knows.
Suggestions
Trim explanations of known concepts — the FLIP definition, morphicons API mode enumeration, and vestibular-effect prose — down to the skill's own rules; keep only what is non-obvious.
Move the GSAP ScrollTrigger hooks and/or the multimodal haptic/som guidance into a reference file (like the existing ui-motion-lab-gsap.html pattern) to shrink the SKILL.md body toward an overview.
Make the performance checkpoint verifiable: alongside 'Manter 60fps em todas as animações', state a concrete check (e.g., DevTools Performance recording criteria or a reduced-motion checklist item) so the Evidencia de Conclusao can actually be validated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and mostly earns its tokens (tokens, variants, rules, tables), but several passages explain concepts Claude already knows — the FLIP definition ('FLIP (First, Last, Invert, Play) mede a posicao antes e depois...'), the morphicons API modes and provenance caveats, and vestibular-disorder effects — and the 'Fontes Externas' section repeats provenance details already stated inline. These are minor over-explanations that could be trimmed, matching anchor 4 rather than 3 where padding would be the rule rather than the exception. | 4 / 5 |
Actionability | Nearly every section ships complete, copy-paste-ready code with imports and full components: motion tokens, entry/exit/stagger Variants, AnimatePresence page wrappers, ButtonPress/CardHover/FocusRing micro-interactions, SkeletonToContent, useStickyStack/useHorizontalPan GSAP hooks, and the useReducedMotion hook with usage. Specific examples cover the common cases, matching the top anchor. | 5 / 5 |
Workflow Clarity | A lifecycle is present and sequenced (Entradas Esperadas → Responsabilidades → Evidencia de Conclusão → Handoff sections), and there is an explicit validation feedback loop ('ligar prefers-reduced-motion... e revisitar cada tela animada... Corrigir o CSS/asset faltante e testar de novo'). It is not a linear process skill, though — many sections are parallel reference patterns rather than ordered steps, and some checkpoints (e.g., the 60fps requirement) are stated as rules with no way to verify — so anchor 4 fits better than 5. | 4 / 5 |
Progressive Disclosure | All four bundle files (decision-gate-and-review.md, naocodei-vanilla-effects.md, ui-motion-lab-gsap.html, view-transitions-api.md) exist, are referenced one level deep, and each reference is clearly signaled with a when-to-use summary (e.g., 'Ver references/naocodei-vanilla-effects.md', the ui-motion-lab description with grammar timings). However the SKILL.md body itself is ~730 lines with substantial sections (GSAP ScrollTrigger hooks, morphicons detail, multimodal feedback tables) that could equally live in reference files, so structure is good but content splitting has minor gaps — anchor 4 rather than 5. | 4 / 5 |
Total | 17 / 20 Passed |