All skills
mblode avatar

/ui-design

@e7db33d
by Matthew Blodemblode/agent-skills136 stars
12

Designs and builds React/Next/Tailwind UI and audits visual and interaction defects. Use when asked to "build a landing page", "extract our design system", "add dark mode", "make this responsive", "remove UI slop", or "audit this component". For product decisions use product-design; for browser measurements use ui-verification; for motion use ui-animation.

Use this Skill: https://skilld.dev/gh/mblode/agent-skills/ui-design

This session only. Nothing lands on disk.

guidelinescolors.md

≈663 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Colors

Covers: brand colors, accent colors, neutral palettes, text colors, default color families, semantic color scales.

  • Never default to indigo as the brand/accent color: use it only if the project already does or the user requests it.
  • Never default to gray-* or slate-* for neutral/text colors: use them only if the project already does or the user requests them; prefer zinc-* or neutral-*.
  • Prefer near-black and near-white over pure #000 and #fff for large surfaces and text-heavy UI. Pure extremes are reserved for deliberate contrast moments.
  • When a palette has a clear warm or cool bias, tint neutrals slightly in the same direction. Do not mix warm-neutral backgrounds with cool-neutral foregrounds unless the brand system already does.
  • On saturated fills, soften secondary text with a lighter tint of the fill hue or transparency rather than generic grey. Verify the resulting contrast in the rendered component.
  • Give palette colors distinct brightness roles as well as different hues. Similar-brightness accents compete, especially in charts, badges, and status-heavy UIs.
  • Increase contrast for primary tasks and important content; lower contrast for structural support like dividers, shadows, inactive chrome, and decorative marks.

Semantic color scales

When defining a custom multi-step palette, give each step a role so component states are derivable, not hand-picked: steps encode intent, not just lightness. For a 10-step scale (scale the mapping to the project's actual step count):

  • 100 background, 200 hover background, 300 active background
  • 400 border, 500 hover border, 600 active border
  • 700 solid fill (high contrast), 800 solid fill hover
  • 900 secondary text and icons, 1000 primary text and icons

Derive states by stepping up the scale: fill 700→800 on hover; background 100→200 (hover), 300 (active); border 400→500→600. Build the scale once; reference roles, never pick a new color per state.

Hold chroma as high as the gamut allows at each step rather than letting it fade toward neutral through the middle of the ramp, which is what makes a scale look chalky. Chroma has to fall away at the extremes because the gamut narrows there, so that is expected, not drift. When lightness alone leaves a difficult hue muddy, rotate the hue slightly as you step: toward yellow as the scale lightens, toward blue as it darkens, keeping the total shift within about 15 degrees end to end so the colour keeps its identity. Author the ramp in oklch() so equal lightness steps stay perceptually even across hues; HSL lightness is not perceptual.

Source: SKILL.md on GitHub

No alerts8d5 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    A comprehensive UI design and auditing skill that uses standard developer tools and trusted services like Tailwind CSS and placeholder asset APIs to build and verify React/Next.js interfaces. It includes explicit guardrails to prevent instruction following from analyzed project files.

  • Socket8d

    No alerts

  • Snyk8d

    Risk: LOW · No issues

  • Runlayer6mo

    4/5 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e7db33d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 hours ago.

Activeupdated last week

README badge

README badge for mblode/agent-skills/ui-design