Source profileQuality 91/100

compozy/compozy/.agents/skills/better-colors/SKILL.md

better-colors

OKLCH color space and color usage for web projects. Convert hex/rgb/hsl to oklch, generate palettes, check contrast, handle gamut boundaries, theme with Tailwind v4, and apply color with meaning. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, semantic color tokens, hue drift, chroma, dark mode colors, accent color, color meaning, light and dark appearance, increased contrast.

Source repository stars
2,672
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSourceFAQ

Decision brief

What it does: where it fits

OKLCH is a perceptually uniform color space where lightness, chroma, and hue are useful design controls. Use it when the project already uses OKLCH, when creating a new color system, or when the user asks for conversion or palette work. Otherwise preserve the project's establish…

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/compozy/compozy --skill ".agents/skills/better-colors"
    Safe inspection promptEditorial

    Inspect the Agent Skill "better-colors" from https://github.com/compozy/compozy/blob/19b8ae06c03954205295478f982c32f3658ca94e/.agents/skills/better-colors/SKILL.md at commit 19b8ae06c03954205295478f982c32f3658ca94e. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Review Output Format

      Use this format only when the user asks for a standalone color review. When better-interface orchestrates the review, provide domain evidence and findings to that skill and let its output format, severity scale, consolidation rules, cap, and verdict take precedence.

      Severity: HIGH makes content unreadable or assigns a misleading semantic color; MEDIUM creates a noticeable theme, gamut, or consistency failure; LOW is isolated polish.Location: cite path/to/file:line. If the artifact has no source files, cite the exact screen and component instead.Before / After: show the current value or token and the exact replacement.
    2. 02

      Verification and Verdict

      1. Verification: list the exact checks run and their observed results, including contrast measurements, gamut checks, and both light and dark appearances when applicable. If a check was not run, state what still needs verification. 2. Verdict: Block if any HIGH finding remains,…

      Verification: list the exact checks run and their observed results, including contrast measurements, gamut checks, and both light and dark appearances when applicable. If a check was not run, state what still needs veri…Verdict: Block if any HIGH finding remains, Needs changes if only MEDIUM or LOW findings remain, and Approve only when no actionable findings remain.1. Verification: list the exact checks run and their observed results, including contrast measurements, gamut checks, and both light and dark appearances when applicable. If a check was not run, state what still needs v…
    3. 03

      Quick Reference

      Review the “Quick Reference” section in the pinned source before continuing.

      Review and apply the “Quick Reference” source section.
    4. 04

      Core Principles

      Use three decimal places for L and C and up to three for H. Drop trailing zeros and format -0 as 0. OKLCH is Baseline 2023; when support requirements are unusually broad, check the target project's browser matrix instead of relying on a fixed global-coverage percentage.

      Respect the existing system. Do not convert notation merely because this skill was loaded. Reuse the project's semantic tokens and authoring format unless the task includes a color-system migration.Perceptual uniformity. Equal L steps = equal brightness. oklch(0.5 ...) is visually mid. HSL's lightness: 50% varies wildly by hue.Stable hue. HSL blue shifts toward purple as lightness changes. OKLCH hue stays constant across the full lightness range.
    5. 05

      1. Use a Perceptual Color Space

      Respect the existing system. Do not convert notation merely because this skill was loaded. Reuse the project's semantic tokens and authoring format unless the task includes a color-system migration.

      Respect the existing system. Do not convert notation merely because this skill was loaded. Reuse the project's semantic tokens and authoring format unless the task includes a color-system migration.Perceptual uniformity. Equal L steps = equal brightness. oklch(0.5 ...) is visually mid. HSL's lightness: 50% varies wildly by hue.Stable hue. HSL blue shifts toward purple as lightness changes. OKLCH hue stays constant across the full lightness range.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score91/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars2,672SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    compozy/compozy
    Skill path
    .agents/skills/better-colors/SKILL.md
    Commit
    19b8ae06c03954205295478f982c32f3658ca94e
    License
    MIT
    Collected
    2026-08-25
    Default branch
    main
    View the original SKILL.md

    OKLCH Colors

    OKLCH is a perceptually uniform color space where lightness, chroma, and hue are useful design controls. Use it when the project already uses OKLCH, when creating a new color system, or when the user asks for conversion or palette work. Otherwise preserve the project's established tokens and notation: a consistent hex or RGB token system is better than introducing a second color representation for an isolated fix. To explore interactively, visit oklch.fyi.

    Quick Reference

    CategoryWhen to useReference
    ConversionHex/rgb/hsl to oklchcolor-conversion.md
    PalettesGenerate scales, multi-hue, dark modepalette-generation.md
    ContrastAPCA/WCAG checks, reporting failures, fixing on requestaccessibility-contrast.md
    Gamut & TailwindP3 fallbacks, @theme scales, gamut clampinggamut-and-tailwind.md
    UsageSemantic tokens, one meaning per color, primary-action emphasis, appearance variantscolor-usage.md

    Core Principles

    1. Use a Perceptual Color Space

    • Respect the existing system. Do not convert notation merely because this skill was loaded. Reuse the project's semantic tokens and authoring format unless the task includes a color-system migration.
    • Perceptual uniformity. Equal L steps = equal brightness. oklch(0.5 ...) is visually mid. HSL's lightness: 50% varies wildly by hue.
    • Stable hue. HSL blue shifts toward purple as lightness changes. OKLCH hue stays constant across the full lightness range.
    • Independent chroma. Chroma is an absolute measure of colorfulness that doesn't depend on lightness. HSL saturation does.
    • Finite gamut. Not every oklch value maps to a displayable sRGB color. High-chroma values at certain hues will clip; gamut awareness is required.

    2. Write and Format OKLCH Consistently

    oklch(L C H)
oklch(L C H / alpha)
    ChannelRangeDescription
    L (Lightness)0–10 = black, 1 = white. Perceptually uniform.
    C (Chroma)0–~0.4Colorfulness. 0 = gray. Max depends on L and H.
    H (Hue)0–360Hue angle in degrees.
    alpha0–1Optional transparency. Slash syntax.
    oklch(0.637 0.237 25.331)
oklch(0.8 0.05 200 / 0.5)

    Use three decimal places for L and C and up to three for H. Drop trailing zeros and format -0 as 0. OKLCH is Baseline 2023; when support requirements are unusually broad, check the target project's browser matrix instead of relying on a fixed global-coverage percentage.

    3. Measure Contrast, Gamut, and Palette Behavior

    RuleValue
    Light/dark boundaryL > 0.73 = light background → dark text; below it, light text still scores higher
    Lightness gap (light bg)Foreground L < 0.35 when background L > 0.9
    Lightness gap (dark bg)Foreground L > 0.9 when background L < 0.25
    Hue drift threshold> 10° spread across palette steps = visible drift
    APCA body text|Lc| >= 75 minimum, >= 90 preferred
    APCA non-body text|Lc| >= 60 minimum
    WCAG 2 normal text4.5:1 AA, 7:1 AAA
    Contrast fix (only when asked)Adjust L first; preserve C and H when possible, then remeasure the rendered pair

    Common Mistakes

    IssueFix
    Raw color bypasses the project's semantic token systemReuse or add the correct role token in the project's existing notation
    Isolated OKLCH value introduced into a hex/RGB codebasePreserve the established notation unless the task includes a color-system migration
    HSL palette ramp with hue driftRebuild with constant oklch hue
    Failing contrast (check foreground vs its background using APCA)Report the pair, its measured Lc and the threshold it misses; change colors only when asked (then adjust L, keep C and H)
    High chroma without gamut checkClamp to max chroma for the L/H in sRGB
    Same absolute C across different huesUse same C% (percentage of max) for consistent vividness
    P3 color without sRGB fallbackAdd @media (color-gamut: p3) pattern
    Dark mode created by mechanically reversing the light paletteUse the light palette as a starting point, then tune chroma and lightness and recheck every foreground/background pair
    Hex in Tailwind v4 @themeConvert to oklch values
    Alpha with comma syntaxUse slash: oklch(L C H / alpha)
    Same hue means two different things (link color reused decoratively)One color, one meaning; give the second use a neutral
    Semantic token used outside its role (separator as text)Add a token for the missing role; never borrow by value
    Several colored control backgrounds in one viewFill only the single primary action; secondaries stay neutral
    Palette verified only in light modeRecheck every foreground/background pair in both appearances

    Review Output Format

    Use this format only when the user asks for a standalone color review. When better-interface orchestrates the review, provide domain evidence and findings to that skill and let its output format, severity scale, consolidation rules, cap, and verdict take precedence.

    Present the standalone review in two parts.

    Findings

    Group all confirmed findings by principle. Use a markdown table with Severity, Location, Before, After, and Why columns. Never use separate "Before:" / "After:" lines.

    • Severity: HIGH makes content unreadable or assigns a misleading semantic color; MEDIUM creates a noticeable theme, gamut, or consistency failure; LOW is isolated polish.
    • Location: cite path/to/file:line. If the artifact has no source files, cite the exact screen and component instead.
    • Before / After: show the current value or token and the exact replacement.
    • Why: name the violated principle and include measured contrast or gamut evidence when relevant.

    Consolidate a repeated systemic issue into one row and list every affected location. Omit principles with no findings.

    SeverityLocationBeforeAfterWhy
    MEDIUMsrc/theme.css:18color: #3b82f6color: oklch(0.623 0.188 259.815)New project colors use OKLCH tokens
    MEDIUMsrc/palette.ts:31Same absolute C across huesSame C% of each hue's maximum chromaEqual chroma values do not appear equally vivid across hues
    HIGHsrc/theme.css:52P3 color with no fallbackAdd an sRGB fallback before @media (color-gamut: p3)The color fails on non-P3 displays

    Verification and Verdict

    After the findings:

    1. Verification: list the exact checks run and their observed results, including contrast measurements, gamut checks, and both light and dark appearances when applicable. If a check was not run, state what still needs verification.
    2. Verdict: Block if any HIGH finding remains, Needs changes if only MEDIUM or LOW findings remain, and Approve only when no actionable findings remain.

    When there are no findings, omit the table, state "No actionable color findings", report verification, and end with Approve.

    Frequently asked questions

    What to verify before installation and use

    What does the better-colors source document cover?

    OKLCH is a perceptually uniform color space where lightness, chroma, and hue are useful design controls. Use it when the project already uses OKLCH, when creating a new color system, or when the user asks for conversion or palette work. Otherwise preserve the project's establish…

    How do I install better-colors?

    The source record exposes this install command: npx skills add https://github.com/compozy/compozy --skill ".agents/skills/better-colors". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10045,511

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-08-240 platforms
    Computed 10045,511

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    2026-08-240 platforms
    Computed 10014,671

    prowler-cloud/prowler

    postgresql-indexing

    PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

    2026-08-240 platforms
    Computed 100147

    oaustegard/claude-skills

    featuring

    Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre

    2026-08-251 platforms