agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/color-theory/SKILL.md

color-theory

Skill220 starsChanged 20 days agoMITView on GitHub

Use when constructing a reusable palette for a visual system: choose a harmony, assign semantic roles and light/dark token values, account for brand and cultural meaning plus color-vision deficiency, and ensure interaction states never rely on hue alone. Not for measuring an existing interface against an accessibility standard.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check contrast for every text/background pair against the WCAG target (hand off measurement to wcag-conformance-audit).

    line 14
  2. Distinctive:

    Every text/background pair meets the declared contrast target.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Theory

Choose and justify a color system for a design by mechanism — harmony, contrast, and meaning — not by taste alone.

Steps

  1. State the job the palette must do: hierarchy, mood, brand fit, and any accessibility target.
  2. Build the palette from a defined relationship (complementary, analogous, triadic, mono) plus neutrals; give each role a name (primary/accent/surface/text), not just a hex.
  3. Check contrast for every text/background pair against the WCAG target (hand off measurement to wcag-conformance-audit); never ship a pair on vibes.
  4. Account for color meaning/culture and color-vision deficiency; ensure no state is encoded by hue alone.
  5. Define the palette as tokens with light/dark values so the system, not a one-off, carries the color.

Acceptance

  • Each color has a named role and a stated relationship to the others.
  • Every text/background pair meets the declared contrast target; no hue-only signaling.
  • The palette is expressed as reusable tokens, not scattered hex values.

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.