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.
Highly actionable reference content with excellent executable examples and useful gotcha fixes, but it is a monolithic single-file skill: everything lives inline in SKILL.md with no progressive disclosure, and there is meaningful duplication between the composition table, composition recipes, and preset sections. The registry and design sections are strong enough to stand alone as reference files.
Suggestions
Split the large standalone sections (Theming/CSS variables, Building a Custom Registry, Design Direction) into reference files under references/ and keep short summaries with pointers in SKILL.md.
Merge the "Reach for this first" table and the "Composition recipes" bullet list into a single source of composition guidance, and fold the standalone "Presets" section into the init options where --preset is already documented.
Trim the opening concept paragraph ("You are an expert in shadcn/ui — a collection of beautifully designed…") to the single non-obvious fact: components are copied as source code, not installed as a dependency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly dense reference material with little concept over-explanation, but it can be tightened: the "Reach for this first" table and the "Composition recipes" bullets repeat the same compositions, presets are documented twice (init options plus a standalone "Presets" section), and the intro re-explains what shadcn/ui is. | 3 / 5 |
Actionability | Fully executable throughout: copy-paste CLI invocations with every flag explained, complete components.json/CSS/TSX blocks, and correct-vs-wrong examples for real gotchas (circular --font-sans reference, Avatar's nonexistent size prop). | 5 / 5 |
Workflow Clarity | Registry creation is sequenced (define → build → consume) and the destructive init (which rewrites globals.css) is backed by an explicit post-init checklist plus --dry-run/--diff/--view affordances, but there is no validate-then-proceed loop for registry builds or `add --all` batch operations — a minor validation gap. | 4 / 5 |
Progressive Disclosure | Well-sectioned with clear headers and tables, but ~570 lines are inlined in a single SKILL.md with no reference files at all — the theming token reference, registry specification, and design-direction guidance clearly belong in separate files pointed to from the overview. | 3 / 5 |
Total | 15 / 20 Passed |