Design
Agent skills for taking work from idea to merged PR
npx -y skills add magarcia/skills --skill designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Check design-system and UI consistency for diffs that touch user-facing surfaces. Use for visual changes, design checks, or as the UI stage of $ship, including small component, style, copy, and layout changes.
SKILL.md
1.7 KB, as published. Nobody here has run it
Design
Gate on the diff: if it does not touch components, styles, tokens, templates, markup, copy, or layout, report "no UI changes in diff" and stop.
- Load context — Read the applicable
AGENTS.mdfiles and the design-system documentation they identify, including the component library, tokens, spacing, typography, breakpoints, and themes. - Inspect statically — Find hand-written values where tokens exist, reimplemented component variants, placeholder copy, and accessibility defects in semantics, labels, alt text, focus states, contrast, or keyboard access.
- Look at the UI — Start the documented development environment or Storybook. Use
$agent-browserfor real interaction and screenshots unless the repository explicitly requires another tool; load its current core workflow before issuing browser commands. Check empty, loading, error, and populated states; hover, focus, active, and disabled states; long and minimal content; project breakpoints; and supported themes. Support every "looks correct" claim with a screenshot. - Fix or flag — Fix mechanical defects within scope, such as a wrong token, missing focus style, or broken breakpoint. Present tradeoffs before changes that involve visual judgment, intentional-looking behavior, or other screens.
Check at least one additional consumer when the diff changes a shared component. Preserve consistency rather than redesigning or adding unrequested aesthetic changes.