Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/ui-design-system
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools.
Passed 19 of 22 test cases with the skill, and 17 of 22 without it.
2 fixed17 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building a reusable DatePicker component for our shared enterprise UI library. Could you write a complete component contract defining its layout breakdown, configurable properties, interaction states, keyboard navigation patterns, and mobile viewport adaptations?
| Checked | Without skill | With skill |
|---|---|---|
| Defines the explicit purpose and appropriate use cases for the DatePicker component. | Missed | Passed |
| Specifies escape hatches for custom overrides within the component contract. | Passed | Passed |
| Identifies deprecated patterns in the component contract. | Missed | Passed |
The instructions your model reads when the skill loads.
Build a design system that reduces repeated decisions and keeps product behavior coherent across teams and surfaces.
Inventory existing tokens, components, duplicated patterns, accessibility behavior, and adoption constraints. Identify whether the real need is a new primitive, a variant, composition guidance, documentation, or cleanup of inconsistent usage.
Do not replace a working system solely to introduce a preferred naming scheme or library.
Use layers when they provide a real distinction:
surface, text-muted, border-danger, and focus-ring;Support themes by remapping semantic roles rather than duplicating component styles. Define units, naming, fallback behavior, and contrast requirements. Generate scales only when the inputs and algorithm are explicit; do not claim to have run a generator that is not available.
For each shared component, define:
Prefer composable primitives over large components with many unrelated boolean props. Avoid exposing visual details that bypass tokens without a justified escape hatch.
test cases passed, vs 17 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.