Content
93%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 tightly written, repo-specific skill that tells the agent exactly where to look (paths, components, commands), how to work (copy the closest existing example), and how to verify (light/dark screenshot), while correctly pushing detail into the project's own design pages and story files rather than inlining it. The only soft spot is that the working sequence is conveyed by section order rather than explicit steps, which costs it a point on workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence ("find the closest thing that already exists and copy it... not a gate to clear before starting") and every section carries project-specific knowledge Claude could not know: component inventory, source paths, the stories/`Default` convention, DESIGN.md locations, and the demos command. No padding or explanation of generally known concepts, matching the 'every token earns its place' anchor. | 5 / 5 |
Actionability | Guidance is concrete and executable throughout: exact paths (`packages/but-ui-react/src/`, `web/node_modules/@gitbutler/but-ui-react/src/`), a copy-paste command (`pnpm -F @gitbutler/but-ui-react demos`), a named component inventory (Button, Popup, Select, Field, Checkbox, Switch, Tooltip, EmptyState, Snackbar, Toasts, Banner), and a precise copy-the-closest-story procedure. As an instruction-only skill whose guidance is fully actionable, the absence of inline code is not penalized. | 5 / 5 |
Workflow Clarity | A clear sequence is present through section order — start from the library, copy the closest example and adapt, consult design pages, apply wording rules, then verify — and an explicit check step exists ("Look at the result in light and dark, and keep one screenshot"). It sits at level 4 rather than 5 because the sequence is implied by section order rather than explicitly enumerated, and there is no error-recovery guidance; it is above level 3 because the ordering and a validation checkpoint are unambiguous and no destructive/batch operations are involved. | 4 / 5 |
Progressive Disclosure | The skill is a short (~45 content lines), well-sectioned overview with no bundle files, and it appropriately delegates bulk detail to existing one-level-deep repo resources (each component's stories, the `DESIGN.md` index and its `design/` pages, `AGENTS.md`) with explicit guidance to load selectively ("Read the pages for what you are building, not all of them"). This matches the clear-overview with well-signaled references anchor. | 5 / 5 |
Total | 19 / 20 Passed |