agentleFS
aka-kikaaka-kika/akakika-skills/skills/design/color-principles/SKILL.md

color-principles

Skill11 starsChanged 3 months agoMITView on GitHub

Use when reviewing or designing a color palette for a UI, website, or app — seven principles for premium, calm, accessible color (palette size, muted tones, contrast, accent restraint, near-black/white, consistency, whitespace).

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If everything shouts, nothing stands out.

    line 21
  2. Distinctive:

    Avoid saturated colors for large areas

    line 22
  3. Very specific:

    Use #1a1a1a or #121212 instead of #000

    line 37
  4. Distinctive:

    Don't crowd colors together

    line 46
  5. Distinctive:

    When reviewing a design, structure the response as:

    line 50

≈ “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

Premium Color Principles

Seven principles for color that feels calm, premium, and accessible. Use them to review or design any digital interface — and reference them by number when giving feedback.

Triggers: color, palette, UI design, visual hierarchy, contrast, muted tones, accent color, design feedback, color theory.

The 7 principles

1. Reduce your palette

The fewer colors you use, the more each one matters.

  • 3 colors maximum
  • Neutral grays as the base
  • One accent color — for CTAs only

2. Use muted tones more often

If everything shouts, nothing stands out.

  • Avoid saturated colors for large areas
  • Muted tones read as premium and calm

3. Create intentional contrast

Contrast tells users where to look first.

  • Minimum 4.5:1 for text (WCAG AA)
  • Target 7:1+ for premium (WCAG AAA)

4. Use accent colors sparingly

Accent colors only work when they're rare.

  • One accent per view/screen
  • Reserve it for the primary action

5. Avoid pure black and pure white

Tiny shifts create different feelings.

  • Use #1a1a1a or #121212 instead of #000
  • Use #FAFAF7 or #F5F5F0 instead of #FFF

6. Keep color behavior consistent

Users shouldn't have to relearn your colors.

  • One action = one color, always

7. Let whitespace support color

Whitespace makes color intentional.

  • Don't crowd colors together

Feedback format

When reviewing a design, structure the response as:

  1. Assessment — which principles it follows or violates
  2. Analysis — specific feedback per principle
  3. Suggestions — concrete hex recommendations
  4. Priority — what to fix first

Pairs well with kika-design-system — these are the general review lens; that skill is one opinionated system built on them.

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.