Skill Wiki
Ai Palette Convergence
Unconstrained LLM agents converge on: Indigo-600 or Violet-500 for hero backgrounds, Blue-500 for CTAs on white, Slate-700 for body text, and identical Tailwind default tokens across every project — producing 'AI slop' s…
$ prime install @community/fact-ai-palette-convergenceProjection
Always in _index.xml · the agent never has to ask for this.
AiPaletteConvergence [fact] v1.0.0
Language-model agents, when given no color constraints, statistically converge on a narrow default palette derived from Tailwind's built-in color system and popular SaaS templates.
Unconstrained LLM agents converge on: Indigo-600 or Violet-500 for hero backgrounds, Blue-500 for CTAs on white, Slate-700 for body text, and identical Tailwind default tokens across every project — producing 'AI slop' sites that look machine-generated because they share the same safe-but-boring palette.
Loaded when retrieval picks the atom as adjacent / supporting.
AiPaletteConvergence [fact] v1.0.0
Language-model agents, when given no color constraints, statistically converge on a narrow default palette derived from Tailwind's built-in color system and popular SaaS templates.
Unconstrained LLM agents converge on: Indigo-600 or Violet-500 for hero backgrounds, Blue-500 for CTAs on white, Slate-700 for body text, and identical Tailwind default tokens across every project — producing 'AI slop' sites that look machine-generated because they share the same safe-but-boring palette.
Applies To
- any AI-generated frontend build without color system constraints
- prompt-only design workflows
- scaffolded Tailwind projects without custom palette configuration
Counter Conditions
- When the prompt explicitly specifies brand hue angles in OKLCH, convergence is broken
- When a persona constraint is provided (e.g. 'developer tool aesthetic'), the agent may self-select away from violet/indigo
- Human designers reviewing AI output before ship can catch and correct convergence patterns
Loaded when retrieval picks the atom as a focal / direct hit.
AiPaletteConvergence [fact] v1.0.0
Language-model agents, when given no color constraints, statistically converge on a narrow default palette derived from Tailwind's built-in color system and popular SaaS templates.
Unconstrained LLM agents converge on: Indigo-600 or Violet-500 for hero backgrounds, Blue-500 for CTAs on white, Slate-700 for body text, and identical Tailwind default tokens across every project — producing 'AI slop' sites that look machine-generated because they share the same safe-but-boring palette.
Applies To
- any AI-generated frontend build without color system constraints
- prompt-only design workflows
- scaffolded Tailwind projects without custom palette configuration
Counter Conditions
- When the prompt explicitly specifies brand hue angles in OKLCH, convergence is broken
- When a persona constraint is provided (e.g. 'developer tool aesthetic'), the agent may self-select away from violet/indigo
- Human designers reviewing AI output before ship can catch and correct convergence patterns
Sources
Source
- Prime Wiki A/B v4/v5 test data — comparative analysis of Raw vs Prime vs Impeccable builds
- CSS Color Level 4 specification
- Impeccable skill — reference/color-and-contrast.md
Applies To
- any AI-generated frontend build without color system constraints
- prompt-only design workflows
- scaffolded Tailwind projects without custom palette configuration
Counter Conditions
- When the prompt explicitly specifies brand hue angles in OKLCH, convergence is broken
- When a persona constraint is provided (e.g. 'developer tool aesthetic'), the agent may self-select away from violet/indigo
- Human designers reviewing AI output before ship can catch and correct convergence patterns
Source
prime-system/examples/frontend-design/primes/compiled/@community/fact-ai-palette-convergence/atom.yaml