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).
In this repository39 other files it gives its agents.
- agent-starter-packSkill
- agent-state-machineSkill
- local-ai-ollamaSkill
- apple-hig-command-paletteSkill
- apple-hig-empty-statesSkill
- apple-hig-feedback-statusSkill
- apple-hig-inspectorsSkill
- apple-hig-macos-window-layoutSkill
- apple-hig-search-filteringSkill
- apple-hig-settingsSkill
- apple-hig-sf-symbolsSkill
- apple-hig-sidebarsSkill
- apple-hig-toolbarsSkill
- apple-hig-typographySkill
- blog-post-publishingSkill
- social-post-kitSkill
- kika-design-systemSkill
- emergency-switch-appSkill
- product-hunt-polish-reviewSkill
- docs-updateSkill
- project-folder-cleanupSkill
- between-runs-auditSkill
- explain-new-projectSkill
- new-project-gateSkill
- old-project-auditSkill
- project-catch-upSkill
- project-workflowSkill
- project-worth-my-timeSkill
- butterfly-effectSkill
- spreadSkill
- tilSkill
- apple-app-intentsSkill
- macos-app-distribution-dmgSkill
- macos-clipboard-pasteboardSkill
- macos-global-shortcutsSkill
- macos-launch-at-loginSkill
- macos-menubar-swiftuiSkill
- macos-notificationsSkill
- macos-permissions-privacySkill
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
- Distinctive: line 21
If everything shouts, nothing stands out.
- Distinctive: line 22
Avoid saturated colors for large areas
- Very specific: line 37
Use #1a1a1a or #121212 instead of #000
- Distinctive: line 46
Don't crowd colors together
- Distinctive: line 50
When reviewing a design, structure the response as:
≈ “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.
Files
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
#1a1a1aor#121212instead of#000 - Use
#FAFAF7or#F5F5F0instead 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:
- Assessment — which principles it follows or violates
- Analysis — specific feedback per principle
- Suggestions — concrete hex recommendations
- 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.
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
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.

