Content
71%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-structured, opinionated rules skill with concrete paths, commands, code patterns, and a thorough workflow. Its weaknesses are moderate: dead reference links within the bundle, some repetition of the extraction doctrine across sections, and no explicit failure-recovery loop in the workflow.
Suggestions
Ship the six ./rules/*.md files referenced throughout the body (ownership, component-shape, cross-platform, react-performance, registry, shadcn-proofing) or inline/remove the dead links so every reference resolves within the bundle.
Consolidate the extraction doctrine — currently repeated in Principles, Ownership & Extraction, Major-Release Law, and the Extraction Test — into a single authoritative section to cut token cost.
Add an explicit error-recovery branch to the workflow (e.g., what to do when the registry changelog check, pnpm brl, or package typecheck fails) to close the validation loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive with no explanations of concepts Claude already knows, but extraction guidance is repeated across four sections (Principles, Ownership & Extraction, Major-Release Law, Extraction Test), which is trimmable redundancy. Not 5 because that repetition costs tokens without adding guidance. | 4 / 5 |
Actionability | Concrete repo paths, real commands ("pnpm brl", "registry-kits.ts", "registry-ui.ts"), and good/bad tsx snippets make the guidance mostly executable. Not 5 because the code examples are illustrative fragments of repo patterns rather than copy-paste runnable code. | 4 / 5 |
Workflow Clarity | The 11-step workflow is clearly sequenced with decision points and explicit verification (registry changelog check, pnpm brl, "Verify the smallest honest surface" with tiered checks). Not 5 because there is no explicit error-recovery loop for what to do when a check or verification fails. | 4 / 5 |
Progressive Disclosure | Structure and signaling are good (section-per-rule with links, "Load these only when the task needs the detail"), but 6 of 7 referenced paths — ./rules/ownership.md, component-shape.md, cross-platform.md, react-performance.md, registry.md, shadcn-proofing.md, and the .agents/rules/plate-ui/references/ files — do not exist in the bundle (only references/component-audit.md is present), so most navigation links fail. Not 4 because broken reference paths undermine navigation; not 2 because the in-file structure itself is well organized. | 3 / 5 |
Total | 15 / 20 Passed |