agentleFS
thrillmadethrillmade/agent-skills/skills/palette-relationships/SKILL.md

palette-relationships

Skill3 starsChanged 9 days agoMITView on GitHub

Use when proposing a palette around a single seed hue and needing to pick which relationship model (monochromatic / analogous / complementary / split-complementary / triadic / tetradic / compound) fits the brief. Names the hue-angle math for each, when each is appropriate (analogous for restraint; triadic for vibrance; complementary for tension), and the role assignment heuristic.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Spread check: every hue is within the relationship's declared offset from the seed.

    line 70

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

Palette relationships

When a designer hands an agent a single starting hue and asks for "the rest of the palette," the choice is which relationship model to apply. Each model is a hue-angle pattern with a different emotional and functional register. Knowing the patterns is most of the job.

When to use

  • A designer or agent has a starting hue and needs additional hues to fill a palette.
  • Proposing a palette for a brief that uses words like "balanced," "vibrant," "calm," "tense," "restrained," "dynamic."
  • Reviewing a palette proposal — name the implicit relationship and check whether the brief asked for it.

When NOT to use

  • The palette is already specified (all hues given). Use chroma-harmonization to balance them, not this skill.
  • The brief is for a single-hue system (just stops of one palette). No relationship to pick.

The relationships

Hue angle math is on the OKLCH 0–360° wheel, anchored at the seed hue H₀.

RelationshipHuesUse whenHue math
Monochromatic1calm, single-brand voice, editorialH₀ (vary L and C across stops)
Analogous2–5restrained, coherent, "family"H₀ ± 15°, H₀ ± 30°
Complementary2tension, before/after, success/danger pairingH₀, H₀ + 180°
Split-complementary3softer tension than complementary, more usableH₀, H₀ + 150°, H₀ + 210°
Triadic3vibrant, balanced, distinct primary/secondary/tertiaryH₀, H₀ + 120°, H₀ + 240°
Tetradic — square4bold, energetic, four equal rolesH₀, H₀ + 90°, H₀ + 180°, H₀ + 270°
Tetradic — rectangle4dynamic but balanced, two complement pairsH₀, H₀ + 60°, H₀ + 180°, H₀ + 240°
Compound (analogous + complement)3–4warm core + cool accent (or vice versa)H₀ ± 30°, H₀ + 180°

For matching briefs to relationships:

  • "calm, monochrome editorial" → monochromatic
  • "restrained, family-feel" → analogous
  • "tension, success vs danger" → complementary
  • "vibrant, distinct roles" → triadic
  • "dynamic and balanced" → tetradic-rectangle (the square is harder to balance at usable chromas)
  • "warm with one cool accent" → compound

Role assignment after picking the relationship

The number of hues dictates the role count, but not the assignment. A triadic palette has three hues; which becomes primary, secondary, tertiary is a design decision driven by intent.

Default heuristic (60/30/10 + accent):

  • 60% — primary = the seed hue (H₀). The dominant brand voice.
  • 30% — secondary = the relationship hue closest to the seed in temperature.
  • 10% — tertiary / accent = the relationship hue furthest from the seed.

For complementary pairs, the seed is primary; the complement is danger or info depending on hue (warm → danger, cool → info).

Pitfalls

  • Square tetrads at usable chromas often read garish — chartreuse (90°) and magenta (270°) next to the seed and its complement tend to fight. Prefer rectangle tetrads (60° / 120° offsets) when the brief is "balanced."
  • Analogous past 60° total spread starts to read as triadic — keep analogous ranges tight.
  • Complementary pairs work for two hues only — padding to four forces a near-duplicate and breaks the relationship.

Verification

After picking hues:

  1. Spread check: every hue is within the relationship's declared offset from the seed.
  2. Distinguishability check: at the palette's typical contrast stop (e.g. 500), neighboring hues are visually distinguishable (rule of thumb: ≥ 20° apart at the same L and C).
  3. Brief match: the relationship matches the brief's adjective (calm / vibrant / tense / dynamic). If not, pick a different relationship.

Cross-references

  • Routed here by: designing-a-design-system — the L1 dispatcher for building or extending a system.
  • REQUIRED BACKGROUND: oklch-color-space — hues are OKLCH angles; the relationship math operates on those.
  • For palette balance after picking hues: chroma-harmonization — cap chroma at the cross-hue minimum.
  • For contrast targets across stops: apca-contrast.

Sources

  • Adobe Color wheel — the canonical interactive picker for relationships.
  • Coolors palette generator — applies the same relationship taxonomy.
  • Itten's color wheel theory (foundational; predates digital tools but supplies the taxonomy).

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.