A skill your agent uses whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting…

Apache-2.0Auto-check passedFrontend & Design

Install Color

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill color -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins color --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/color .claude/skills/color && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
color
GitHub stars
1.3k
Token cost
~3.6k tokens
SKILL.md length
1,631 words
Files
2 (incl. references)
Skills in repo
714
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting…

  • Works in 9 steps: Attention → Grouping → Meaning → …
  • Color decisions matter — picking the brand primary
  • SKILL.md covers Definition (in our own words), Origins and research lineage, The four jobs of color and Number of colors: be restrained, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Color is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting accent hues, supporting dark mode, ensuring colorblind-safe contrast, or auditing an existing UI for color noise. Trigger when stakeholders argue about palette, when WCAG contrast is in scope, when designing for global audiences (where color symbolism varies), or when a UI feels "too colorful" or "too monochrome." Color is one…

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/color-theory-and-systems.md`).

It sits in Frontend & Design, covering Accessibility and Theming and dark mode. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Color decisions matter — picking the brand primary
  • Defining a neutral ramp
  • Designing status semantics (success/warning/error)
  • Choosing chart palettes

Example prompts

  • “too colorful”
  • “too monochrome.”
  • “Universal Principles of Design”
  • “/color”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Attention
  2. Grouping
  3. Meaning
  4. Aesthetics
  5. Pick the brand primary
  6. Define the neutral ramp
  7. Define semantic colors
  8. Test in dark mode
  9. Test for accessibility

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html and css).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Color loads about 3.6k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 155 tokens; SKILL.md has 1,631 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~155
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 1,631 words, ~3,588 tokens.

Download SKILL.mdSave it as .claude/skills/color/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
color
description
Use this skill whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting accent hues, supporting dark mode, ensuring colorblind-safe contrast, or auditing an existing UI for color noise. Trigger when stakeholders argue about palette, when WCAG contrast is in scope, when designing for global audiences (where color symbolism varies), or when a UI feels "too colorful" or "too monochrome." Color is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003).

Color

Color attracts attention, groups related elements, signals meaning, and shapes aesthetic response. Used deliberately, it carries information at a glance and unifies a product. Used carelessly, it adds noise, fails accessibility, and means different things to different audiences. Among visual variables, color is the loudest and the most easily abused.

Definition (in our own words)

Color performs four jobs in design: it draws the eye to elements that matter (attention), it visually unifies elements that belong together (grouping), it carries categorical or semantic information (meaning — green is success, red is danger), and it shapes the aesthetic register of the design (a saturated palette feels energetic; a muted one feels serious). Each color you introduce to a design takes on one or more of these roles; designs that use color promiscuously dilute every role. The discipline is in the restraint: a small palette, used consistently, with each color earning its place.

Origins and research lineage

  • Josef Albers, Interaction of Color (1963). The foundational treatment of perceptual color relationships — how the same color reads differently against different backgrounds. Required reading for anyone designing color systems.
  • Johannes Itten, The Art of Color (1961). The Bauhaus tradition of color theory; introduced the color wheel still used today.
  • Maxwell, Helmholtz, Hering — 19th-century color-perception researchers whose work underlies modern color science (trichromacy, opponent-process theory).
  • Lidwell, Holden & Butler (2003) compactly addressed the design implications under the headings of number of colors, combinations, saturation, and symbolism. The book emphasizes restraint: use color conservatively and never as the only signal.
  • WCAG color-contrast research (W3C, 2008 onward) provides the empirical basis for accessibility-aware color systems — body text needs 4.5:1 luminance contrast minimum.
  • Modern perceptual color spaces (CIELAB, OKLCH) provide tools for building color systems that are perceptually uniform across hues.

The four jobs of color

1. Attention

A saturated, distinct color in a sea of neutrals draws the eye. This is the basis for primary CTAs, error states, and emphasis. The mechanism is preattentive: a single colored item among uncolored items "pops out" within ~200ms.

The economy: attention only works when sparse. A page where every element is colored loses the pop-out advantage entirely.

2. Grouping

Items that share a color read as related. This underlies status systems (all overdue items in red), category coding (all marketing dashboards in blue), and brand identity (all of this product's surfaces share this hue).

Use this for meaningful relationships, not for decoration.

3. Meaning

Color carries semantic content when it's used consistently and conventionally. In Western contexts: red = danger / stop / error; green = go / success; yellow = warning. These conventions are partly cultural (red signals luck in much of East Asia; green is unlucky in some contexts), so global products should pair color with non-color signals.

4. Aesthetics

Color shapes mood. Saturated palettes feel energetic; muted palettes feel calm or serious. Warm colors (yellow, orange, red) feel active; cool colors (blue, green, purple) feel stable. These associations are partly biological (warm colors attract attention faster) and partly cultural.

Number of colors: be restrained

A useful rule: limit your active palette to ~5 colors that the user must recognize.

Brand primary    — 1 hue
Neutrals         — a ramp from dark to light (~9 stops)
Success          — 1 hue (typically green)
Warning          — 1 hue (typically yellow / amber)
Destructive      — 1 hue (typically red)

Beyond this, every additional hue dilutes the system. Charts and data visualizations may need 5–8 categorical colors, but those are exceptions; the interface chrome should stay restrained.

Color combinations: how to compose a palette

Common harmony patterns (from the color wheel):

  • Monochromatic: variations of one hue (different lightness/saturation). Calm, unified.
  • Analogous: hues adjacent on the wheel (blue, blue-green, green). Harmonious, low-tension.
  • Complementary: hues opposite on the wheel (blue + orange). High contrast, high tension.
  • Triadic: three hues equidistant on the wheel. Balanced, vibrant.
  • Quadratic: four hues from a square or rectangle on the wheel. Complex; needs careful weighting.

For UI work, monochromatic + neutrals + a few semantic accents is the workhorse. Complementary and triadic palettes look striking but require more care to balance.

Saturation: the volume knob

Saturation (chromatic intensity) is color's volume knob.

  • Saturated colors demand attention. Use sparingly: primary CTAs, errors, brand moments.
  • Desaturated colors recede. Use abundantly: backgrounds, neutrals, secondary states.

A common UI mistake: saturated colors everywhere. The page becomes loud; nothing stands out. The fix: pull saturation down on most surfaces; reserve full saturation for moments.

Symbolism: cultural variation

Color symbolism is not universal. Examples:

  • Red: danger / stop in Western contexts; luck and prosperity in Chinese contexts; mourning in some African contexts.
  • White: purity in Western weddings; mourning in some Asian funerals.
  • Black: formal / authoritative in Western; mourning broadly; rebellion in subcultures.
  • Green: nature / go in Western; sometimes unlucky or associated with infidelity in specific contexts.
  • Yellow: caution / warmth in Western; sacred in some Asian contexts; cowardice in others.

For global products: don't rely on color symbolism alone. Pair color with text, icons, and position so the meaning carries across audiences.

Color is never the only signal

WCAG 1.4.1 codifies what's also a basic usability principle: color must not be the only means of conveying information. About 8% of men have red-green color blindness; achievement of WCAG 1.4.1 requires that any color signal be paired with a non-color signal.

Practical applications:

  • Form errors: red border + error message + icon, not just red border.
  • Status badges: color + icon + text, not just color.
  • Required fields: asterisk + "(required)" or aria-required, not just red label.
  • Chart series: color + pattern (lines: dashed, dotted) or label, not just color.
  • Selected items: color + checkmark or border, not just color.

This isn't only for color-blind users; it serves anyone in glare, on a printed copy, in low contrast, or with degraded vision.

Color and accessibility (WCAG)

Foreground/background contrast ratios (relative luminance):

Content typeLevel AALevel AAA
Body text (< 18pt regular or < 14pt bold)4.5:17:1
Large text (≥ 18pt regular or ≥ 14pt bold)3:14.5:1
UI components and graphical objects3:1(no AAA)

Common failures:

  • Light grey body text (#999 on white = 2.85:1 — fails).
  • Brand-color body links (#1e90ff on white = 3.4:1 — fails for body, passes for large/UI).
  • Placeholder text in inputs (often <3:1 — fails for the field's accessible name).

Test with a contrast checker (WebAIM, Stark, Chrome DevTools). It's faster than guessing.

Show full SKILL.md (631 more words)Show less

Building a color system

A workable system architecture:

1. Pick the brand primary

One hue. This is the color users will associate with your product. Choose with awareness of category conventions (banking is often blue; food is often warm; tech is often blue or green).

2. Define the neutral ramp

9–11 stops from white to near-black. Tinting the neutrals slightly toward the brand primary (e.g., 4% saturation of the primary hue) makes the whole UI feel cohesive without anyone consciously noticing.

neutral-50    background (lightest)
neutral-100   subtle background, hover
neutral-200   borders, dividers
neutral-300   strong borders
neutral-400   placeholder, icons
neutral-500   muted text
neutral-600   secondary text
neutral-700   primary body text
neutral-800   strong text, headings
neutral-900   highest contrast
3. Define semantic colors

Three to five hues for status:

  • Success (typically green).
  • Warning (typically amber / yellow).
  • Destructive / Error (typically red).
  • Optionally: Info (typically blue, especially if your primary is not blue).

For each, define multiple stops: a tinted background (green-50), a darker text color (green-700), a focus or border color (green-500).

4. Test in dark mode

A palette tuned for light mode often fails in dark mode — saturation and contrast perception inverts. Build dark-mode tokens deliberately, not by simple inversion.

5. Test for accessibility

Every text-on-background pair you ship must clear 4.5:1 (body) or 3:1 (large/UI). Test with a contrast checker; fix what fails.

Worked examples

Example 1: a status badge system
html
<style>
  .badge { display: inline-flex; align-items: center; gap: 4px;
           padding: 2px 8px; border-radius: 9999px;
           font-size: 12px; font-weight: 500; }
  .badge--success { background: hsl(142 70% 95%); color: hsl(142 70% 22%); }
  .badge--warning { background: hsl(38 95% 95%);  color: hsl(38 90% 25%); }
  .badge--error   { background: hsl(0 80% 95%);   color: hsl(0 75% 32%); }
  .badge--neutral { background: hsl(0 0% 96%);    color: hsl(0 0% 30%); }
</style>

<span class="badge badge--success"><CheckIcon aria-hidden /> Paid</span>
<span class="badge badge--warning"><ClockIcon aria-hidden /> Pending</span>
<span class="badge badge--error"><AlertIcon aria-hidden /> Overdue</span>
<span class="badge badge--neutral"><PencilIcon aria-hidden /> Draft</span>

Each badge uses color, icon, and text. Color carries category at a glance; icon and text carry it for color-blind users and for any out-of-context display.

Example 2: a primary action vs. secondary action
html
<button class="btn-primary">Save changes</button>
<button class="btn-secondary">Cancel</button>
css
.btn-primary {
  background: hsl(220 90% 50%);   /* full-saturation brand */
  color: white;
  /* ...padding, radius... */
}
.btn-secondary {
  background: white;
  color: hsl(0 0% 27%);
  border: 1px solid hsl(0 0% 85%); /* neutral, no color emphasis */
}

The primary uses full saturation and the brand hue; the secondary uses neutrals only. The eye picks the primary instantly.

Example 3: a chart palette
css
:root {
  --chart-1: hsl(220 70% 55%);
  --chart-2: hsl(160 60% 45%);
  --chart-3: hsl(40 90% 55%);
  --chart-4: hsl(310 60% 55%);
  --chart-5: hsl(10 70% 55%);
}

Five hues at similar lightness and saturation, distributed around the wheel. Each is distinct from the others and survives most color-blindness simulations. For more series, add patterns (dashed lines, dotted, hatched fills) rather than adding more hues.

Anti-patterns

  • Saturation overload. Every CTA, every chart, every badge at full saturation. Page becomes a noise field.
  • Color-only signals. Red asterisks for required fields with no * or "required" text. Color-blind users miss it.
  • Brand color everywhere. Every link, every heading, every accent in the brand color. Brand stops registering.
  • Light grey body text (#999 on white). Fails AA contrast; fatigues all readers.
  • Inconsistent semantic colors. "Destructive" in one shade of red here, a different shade there. Each instance is a re-learning.
  • Dark-mode by simple inversion. Saturation perception differs; pure inversion produces glare.
  • Color symbolism assumed universal. A red Lunar New Year banner reading as "danger" because the design system equates red with errors.
  • Too many colors. A 12-hue palette where users can't predict what means what.

Heuristics

  1. The grayscale test. Convert to grayscale. Does the design still work? If yes, color is supportive but not load-bearing. If no, you're depending on color too much.
  2. The contrast pass. Every text/background pair, every UI/background pair. AA at minimum.
  3. The colorblind simulation. Chrome DevTools → Rendering → Emulate vision deficiencies. Status systems that lean on red/green collapse here.
  4. The cultural check. For global products, check color symbolism with users in target markets.
  5. The dark-mode test. Switch to dark mode. Does the palette still work? Are contrasts still passing?
  • hierarchy-color-and-tone — color as a hierarchy axis.
  • highlighting — color is the strongest highlighting tool.
  • signal-to-noise-ratio — color discipline is at the core of SNR design.
  • accessibility-perceivable (process) — color decisions are accessibility decisions.
  • expectation-effect (interaction) — color signals shape user expectations.
  • uniform-connectedness — color is one of the strongest grouping signals.
  • interference-effects — mismatched color/meaning (red "go" button) creates Stroop interference.

Sub-aspect skills

  • color-semantic-systems — building status/category color systems that scale and stay consistent.
  • color-accessibility-and-mode — accessibility-aware color, dark mode, and high-contrast support.

Closing

Color is the loudest single dimension a designer commands. The discipline is in the restraint: a small palette, used consistently, with each color earning its place. Designs that respect this restraint feel polished; designs that don't feel noisy. Spend color where it earns the volume.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/color of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/color-theory-and-systems.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Color next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Color compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Color this skillhashgraph-online/awesome-codex-plugins1.3k—~3.6kAutomated safety check: PassApache-2.0
Color Auditrome-os/rome737—~2.7kAutomated safety check: PassMIT
Ant Designkqcoxn/MaaPipelineEditor4081 repos~1.1kAutomated safety check: PassMIT
Better Colorstrycompai/crm11k—~1.9kAutomated safety check: PassMIT
Data-Dense Dashboard Designerplugin87/ux-ui-agent-skills1.6k—~2.6kAutomated safety check: PassMIT
Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill135—~3kAutomated safety check: PassMIT

Similar skills

  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    737 GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Ant Design

    kqcoxn/MaaPipelineEditor

    Decision guide for antd 6.x, Ant Design Pro 5/ProComponents, Ant Design X v2, and the offline @ant-design/cli.

    408 GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Better Colors

    trycompai/crm

    OKLCH color space and color usage for web projects. An agent skill from trycompai/crm.

    11k GitHub stars~1.9k tokensUpdated 28 days ago
    Frontend & DesignAuto-check passed
  • Data-Dense Dashboard Designer

    plugin87/ux-ui-agent-skills

    Lays out dense analytics or trading-terminal screens in banded sections with hand-drawn SVG charts, instead of a wall of identical stat cards.

    1.6k GitHub stars~2.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Material Design 3 UI/UX Guide

    skydashnet/material-design-3-ui-skill

    Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.

    135 GitHub stars~3k tokensUpdated 8 days ago
    Frontend & DesignAuto-check passed
  • UI Design System

    try-works/role-model

    React UI component systems with TailwindCSS + Radix + shadcn/ui.

    118 GitHub stars~5k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Color

What does Color do?

A skill your agent uses whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting…. Color is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill whenever color decisions matter — picking the brand primary, defining a neutral ramp, designing status semantics (success/warning/error), choosing chart palettes, selecting accent hues, supporting dark mode, ensuring colorblind-safe contrast, or auditing an existing UI for color noise.

When should I use Color?

Color fits situations like: color decisions matter — picking the brand primary; defining a neutral ramp; designing status semantics (success/warning/error); choosing chart palettes.

How do I install Color in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill color -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/color in hashgraph-online/awesome-codex-plugins) into .claude/skills/color in your project. Claude Code loads it when a task matches its description.

How do I install Color in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill color -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/color in hashgraph-online/awesome-codex-plugins) into .agents/skills/color in your project. Codex loads it when a task matches its description.

Can I use Color in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill color -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/color, .gemini/skills/color, .github/skills/color and .opencode/skills/color in your project.

What does Color need to run?

SKILL.md names no scripts, command-line tools or credentials: Color is instructions for the agent only.

Does Color access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Color safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Color use?

Color is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Color use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Color?

Skills that share tags, products or a category with Color: Color Audit (rome-os/rome, 737 stars), Ant Design (kqcoxn/MaaPipelineEditor, 408 stars), Better Colors (trycompai/crm, 11k stars) and Data-Dense Dashboard Designer (plugin87/ux-ui-agent-skills, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Color?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.