Content
77%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-engineered, rule-driven body with a clear escalation sequence, strong validation gates around the risky eject/restore operations, and mostly executable commands and code. Its weaknesses are structural: the full component contract and CLI detail are inlined in SKILL.md instead of being split into reference files, and the shared-feature composition path lacks a concrete code example.
Suggestions
Move the 17-component design-system contract enumeration and the detailed ejection CLI command reference (inspect/diff/restore) into a reference file such as references/contract.md, linked from a short summary in SKILL.md, so the body stays an overview.
Add a minimal executable example of the controller-plus-render-slot composition in "Customize A Shared Feature" — currently the only core workflow with no code or command.
Trim known-knowledge explanation such as the list of styling runtimes adapters "may use" down to the one rule that matters (className/style are optional interop hooks, not Tailwind/CVA requirements).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and instructional with almost no filler — e.g. "Ejection is for intentional product customization, not for hiding an upgrade failure" — but a few lines explain things Claude already knows, such as "They are ordinary React components and may use MUI-style providers, React Aria, CSS modules, CSS-in-JS, or another styling runtime." That is over-explanation of standard React styling options, keeping it below the 'every token earns its place' anchor but above the 'mostly efficient with some unnecessary explanation' anchor. | 4 / 5 |
Actionability | Most workflows ship copy-paste-ready material: the `defineDesignSystem` registration block, the conformance-kit invocation, the four `agent-native eject` commands, and the `docs-search`/`source-search`/`rg` lookup commands. It misses the 5 anchor because "Customize A Shared Feature" — a core path — gives only abstract direction ("Prefer feature-level headless controllers over rebuilding individual widgets... Use a product-level render slot") with no controller/slot code example, and adapter implementations are named but never shown. | 4 / 5 |
Workflow Clarity | The escalation order is an explicit six-step numbered sequence, and the risky batch operation (ejection, which copies files and rewrites imports) has genuine validation checkpoints and recovery loops: dry-run by default that prints "the file closure, consumer import rewrites, protected package contracts, and verification commands before writing", hash-gated restore that "refuses to remove locally edited files... and prints their diff instead", and an After Ejecting checklist ("Run the manifest verification commands plus the app's formatter, typecheck, and focused tests"). This matches the full validation-plus-feedback-loop-plus-checklist anchor. | 5 / 5 |
Progressive Disclosure | The single-file body (~205 lines) has clear headers and easy navigation, but it is well over the simple-skill size where sections alone suffice, and contract-detail content that belongs in a separate reference file is inlined — notably the 17-component design-system contract enumeration ("nine leaf components... eight behavior components") and the detailed ejection CLI subcommand walkthrough. There is no reference material split out at all (no references/, scripts/, or assets/ directories exist), which is why this sits at the 'content that should be separate is inline' anchor rather than the good-structure anchor. | 3 / 5 |
Total | 16 / 20 Passed |