Content
61%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-organized rule index with genuinely useful executable examples for the highest-impact patterns, and good token discipline overall. Its two real defects are the broken reference layer — every referenced `rules/*.md` file is missing from the bundle, so the promised detail tier doesn't exist — and internal inconsistencies ("12 categories" claimed vs. 11 listed; `useStore` vs. `useGameStore`).
Suggestions
Ship the seven referenced rule files (rules/perf-never-set-state-in-useframe.md, rules/perf-zustand-selectors.md, rules/perf-visibility-toggle.md, rules/perf-r3f-perf.md, rules/frame-delta-time.md, rules/drei-use-gltf.md, rules/loading-suspense.md) in the bundle, or remove the dangling references — the "How to Use" section promises files that are not present.
Add a short explicit navigation workflow (task → category prefix → rule file or one-line summary) so the consumption order is unambiguous for a lookup-style skill.
Fix internal inconsistencies: the header claims "70+ rules across 12 categories" while only 11 categories are listed, and the Zustand "BETTER" example switches from `useGameStore` to an undefined `useStore`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean — one-line rule summaries, code only for critical patterns, and no explanation of basics — but the "Ecosystem Coverage" section spends eight lines describing what each library is ("React renderer for Three.js", "Physics engine"), knowledge Claude already has, and "When to Apply" duplicates the frontmatter triggers. This matches "efficient; minor instances of over-explanation that could be trimmed" rather than the padded anchor 3 case. | 4 / 5 |
Actionability | The critical patterns are shown as concrete, executable BAD/GOOD JSX (setState-in-useFrame vs. ref mutation, Zustand selectors, useGLTF with preload, Suspense, Perf) and the one-liners are terse directives. Minor gaps keep it below anchor 5: the "BETTER" Zustand snippet calls an undefined `useStore` (the earlier example uses `useGameStore`), and `useRef()` is untyped. | 4 / 5 |
Workflow Clarity | This is a reference catalog rather than a procedural skill; the priority table and "How to Use" section give consumption guidance, but the navigation path (identify the task's category → look up its prefix → read the rule file or one-liner) is left implicit and there are no checkpoints or feedback loops. It sits at "steps listed but sequence/checkpoints implicit" rather than anchor 4's clear sequenced procedure. | 3 / 5 |
Progressive Disclosure | The design is correct — one-line summaries in SKILL.md with detail in one-level-deep `rules/*.md` files, clearly listed — but the `rules/` directory does not exist in the bundle: none of the seven referenced files (e.g., `rules/perf-never-set-state-in-useframe.md`) ship, even though the text asserts "Only these rule files ship with this copy". The references dead-end, which is worse than the merely-unclear-signaling anchor 3 and lands at anchor 2. | 2 / 5 |
Total | 13 / 20 Passed |