AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Color Theory

skill-flitzrrr-frontend-design-skills-color-theory · by flitzrrr

Color models, palettes, contrast, color psychology, color harmonies, and dark mode for web projects. Defines the 60-30-10 rule, semantic color coding, design tokens, and WCAG contrast requirements.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-flitzrrr-frontend-design-skills-color-theory

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-flitzrrr-frontend-design-skills-color-theory)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Color Theory? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Color Theory

> Systematic color design -- from strategic color selection to accessible dark mode.

Scope

Use this skill when: You are defining color schemes, building palettes, checking contrasts, designing dark mode, establishing semantic colors, creating design tokens for colors, or auditing existing color concepts for quality.

Principles

1. Colors Are Communication -- Not Decoration

Every color conveys a message. Color selection is a strategic decision.

2. Fewer Colors -- Stronger Impact

2-4 colors are sufficient for 95% of all projects. Primary color + accent color + neutral tones.

3. Contrast Is Mandatory

Without sufficient contrast, colors are ineffective. Contrast determines readability, hierarchy, and accessibility.

4. Consistency Across All Channels

Colors must appear identical everywhere. This requires a defined color system with named tokens.

5. Color for Function, Not Just Mood

Colors indicate status (red = error, green = success), signal interactivity, and mark relationships.

Rules

Building a Color Scheme

  • DO: Minimal scheme: 1 primary color + 1 accent color + 3-5 neutral tones.
  • DO: Create gradations of each color in 9-11 steps (50-950).
  • DO: Define semantic colors: success (green), warning (orange), error (red), info (blue).
  • DO: Use color harmonies as a starting point: complementary, analogous, or triadic.
  • DON'T: Use randomly chosen colors. Each one needs justification (brand, function, emotion).
  • DON'T: Use more than 5 chromatic colors (excluding neutral tones).

Color Models & Formats

  • DO: Work internally with HSL (more intuitive for systematic gradations).
  • DO: Use oklch() in modern CSS for perceptually uniform gradations.
  • DON'T: Use CMYK on the web. CMYK is for print.

Contrast & Readability

  • DO: Normal text (= 24px / >= 18.66px bold): at least 3:1 (WCAG AA).
  • DO: UI components (icons, borders, focus): at least 3:1.
  • DO: Simulate and test for color vision deficiency (protanopia, deuteranopia, tritanopia).
  • DON'T: Use color as the ONLY differentiator. Always provide a second signal (icon, text, shape).
  • DON'T: Use light pastel tones on white backgrounds for text or interactive elements.

Color Psychology & Impact

  • DO: Choose the primary color to match the industry:
  • Blue: Trust (finance, tech, healthcare)
  • Green: Nature, growth (organic, sustainability)
  • Red: Energy, urgency (food, sales)
  • Black: Premium (luxury, fashion)
  • Orange/Yellow: Optimism (startups, education)
  • Purple: Creativity (creative industries, wellness)
  • DO: Consider cultural differences for international projects.
  • DON'T: Work against industry expectations without a deliberate differentiation strategy.

Dark Mode

  • DO: Design dark mode as an independent color scheme, not an inversion.
  • DO: Use muted primary colors (less saturation, medium brightness).
  • DO: Background: dark gray (#121212 to #1E1E1E), NOT pure black (#000).
  • DO: Text: #E0E0E0 instead of #FFFFFF.
  • DON'T: Use saturated bright colors on dark backgrounds -- they "glow."

Design Tokens

  • DO: Two-tier system: primitive tokens (--blue-500) + semantic tokens (--color-primary).
  • DO: Use exclusively semantic tokens in components.
  • DON'T: Use HEX values directly in component CSS.

Patterns

Detailed pattern descriptions: see references/patterns.md

60-30-10 Rule

60% dominant color (background) + 30% secondary (cards, navigation) + 10% accent (CTAs, highlights).

Monochromatic Scheme

One color in 5-7 gradations. Accent through a single contrasting color for CTAs.

Complementary Contrast

Two opposing colors. Never equally weighted -- one dominates (60-30-10).

Semantic Color Coding

Green = success, red = error, orange = warning, blue = information. These associations are established cross-culturally and are NOT reinterpretable.

Anti-Patterns

Rainbow Design

Too many colors without a system. Solution: 60-30-10 rule. Max. 5 chromatic colors.

Color as the Only Signal

Red = error without icon or text. Solution: Always provide a redundant signal alongside color.

Blindly Adopting Trend Colors

Trend color as primary without fit. Solution: Use trends as inspiration, brand values as the decision basis.

Ignoring Contrast Violations

"Looks fine to me" instead of objective verification. Solution: Check every combination with a tool (WebAIM, Chrome DevTools).

Dark Mode as Inversion

Swapping black and white. Solution: Independent scheme with adjusted saturation and brightness.

Checklist

  • [ ] Color scheme defined: primary + accent + neutrals + semantic?
  • [ ] Max. 5 chromatic colors?
  • [ ] 60-30-10 rule applied?
  • [ ] All text-background combinations WCAG AA (4.5:1 normal, 3:1 large)?
  • [ ] UI component contrast at least 3:1?
  • [ ] Color vision deficiency tested?
  • [ ] Color never used as the only signal?
  • [ ] Design tokens defined (primitive + semantic)?
  • [ ] No HEX values directly in components?
  • [ ] Dark mode as an independent scheme?
  • [ ] Dark mode background #121212-#1E1E1E (not #000)?
  • [ ] Color psychology appropriate for the industry?

Cross-References

  • ui-design -- Color as a hierarchy tool in layout
  • web-typography -- Text color and contrast ratios
  • accessibility -- WCAG contrast requirements in detail
  • branding-identity -- Color as brand identity
  • visual-direction -- Current color trends
  • design-trends -- Color trends from award-winning websites

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.