agentleFS
Above-the-Fold-StudioAbove-the-Fold-Studio/designmd-skills/skills/color-and-contrast/SKILL.md

color-and-contrast

Skill0 starsChanged 3 months agoMITView on GitHub

Build purposeful interface color roles with legible contrast, clear states, and restrained emphasis.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use color as a system of roles rather than a collection of attractive values.

    line 8
  2. Distinctive:

    Do not communicate meaning with color alone.

    line 12
  3. Distinctive:

    Test light and dark themes independently.

    line 29
  4. Distinctive:

    Check transparency over every supported surface.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Color and Contrast

Use color as a system of roles rather than a collection of attractive values. Apply this when defining tokens, correcting contrast, separating interaction states, or reducing noisy and inconsistent emphasis.

Do not communicate meaning with color alone. Do not claim accessibility from a palette screenshot; evaluate the actual foreground, background, size, weight, state, and adjacent colors.

Workflow

  1. Inventory semantic roles: canvas, surface, text levels, border, action, focus, selection, success, warning, error, data series, and disabled states.
  2. Trace each role to its real usage. Separate brand color from interactive color when one value cannot safely serve both.
  3. Establish neutral structure first, then reserve chroma for meaning and priority. Remove decorative competition before adding saturation.
  4. Measure text and essential graphical-object contrast against their actual backgrounds. Include hover, active, focus, selected, disabled, and forced color or high-contrast behavior where applicable.
  5. Pair status color with text, iconography, shape, or placement. Ensure links and controls remain identifiable without hue perception.
  6. Test light and dark themes independently; do not mechanically invert values. Check transparency over every supported surface.
  7. Express stable roles as semantic tokens and document intentional exceptions.

Output

Return the semantic role map, contrast or state failures, recommended token and usage changes, non-color cues, and the combinations actually verified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.