Content
67%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 focused, domain-specific rules document with concrete paths and clear decision guidance rather than generic explanation. Its main weakness is repetition of the upstream-first rule across sections and the absence of any progressive-disclosure split despite exceeding the simple-skill line count.
Suggestions
Consolidate the repeated 'upstream first' rule into a single Core Contract statement and have Registry/Template Rules reference it, trimming redundancy for conciseness.
Move the detailed registry dependency rules (namespaces, URL rewriting, compatibility input) into a references/ file and summarize them in SKILL.md to improve progressive disclosure.
Add one short worked example showing the decision flow on a concrete change (check ../shadcn -> copy pattern -> state divergence reason) to lift actionability and workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean bullet directives with no padding of concepts Claude already knows, but the 'upstream first' rule is restated across Core Contract, Registry Rules, and Template Rules, so it could be tightened; fits 'mostly efficient but some redundancy'. | 3 / 5 |
Actionability | Concrete, specific guidance with real paths and examples (apps/www/src/registry/*, tooling/scripts/update-template.sh, https://platejs.org/r/*.json, bare names like button/command/popover) and clear prefer-over rules; not a 5 because it is instruction-only with no executable snippet covering a common case end-to-end. | 4 / 5 |
Workflow Clarity | An implicit decision workflow (check ../shadcn first, copy patterns, diverge only with stated reason) with checkpoint-like signals ('Stop and reassess', 'If you diverge, say exactly why', 'fix both sides together'); not a 5 because there is no explicit validate-fix-retry loop, though none is strictly required for this rules skill. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the body is well-organized into clear headers (Core Contract, Ownership, Registry Rules, Template Rules, Current Divergences, Red Flags); not a 5 because at ~130 lines the under-50-line simple-skill exception does not apply and some detailed dependency rules could live in a reference file. | 4 / 5 |
Total | 15 / 20 Passed |