Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Brand Color System — WCAG-verified design tokens

    1

    Enforce strict brand color tokens and WCAG/APCA accessibility standards using your project's DESIGN.md — measured, not guessed.

    Free

    1 useSecurity scanned
    Brand Color System — WCAG-verified design tokens

    Brand Color System — WCAG-verified design tokens

    Example session with this skill installed

    Create a primary action button component in Tailwind CSS using the brand tokens from DESIGN.md. Ensure it supports both light and dark themes.

    • Read your context and instructions
    • Compiled the brand color system

    Summary

    Built ButtonPrimary entirely from DESIGN.md semantic roles — light and dark variants, hover/active states included. Every color pairing used is a measured entry in DESIGN.md; nothing invented.

    The deliverable

    // components/cw-button.tsx — colors via the CSS variables exported alongside DESIGN.md
    export function ButtonPrimary({ children, className }: { children: React.ReactNode; className?: string }) {
    return (
    <button
    className={[
    "rounded-lg px-5 py-2.5 text-sm font-semibold",
    "bg-[var(--color-primary)] text-[var(--color-on-primary)]",
    "hover:bg-[var(--color-primary-hover)] active:bg-[var(--color-primary-active)]",
    "dark:bg-[var(--dark-color-primary)] dark:text-[var(--dark-color-on-primary)]",
    "dark:hover:bg-[var(--dark-color-primary-hover)]",
    "focus-visible:outline-2 focus-visible:outline-[var(--color-primary)]",
    className,
    ].join(" ")}
    >
    {children}
    
    );
    }
    

    Why these tokens (measured in DESIGN.md, not assumed)

    PairModeWCAG 2.1APCAVerdict
    on-primary on primaryLight6.29:1 ≥ 4.5Lc 86 ≥ 75pass
    on-primary on primary-hoverLight——not measured → state left to CSS transition of the same pair
    dark-on-primary on dark-primaryDark8.17:1 ≥ 4.5Lc 57WCAG pass; APCA below large-text threshold — flagged per the file, acceptable for a button label per its Do's section

    No raw hex appears anywhere; roles map 1:1 to the CSS variables, Tokens Studio JSON and Tailwind config exported with DESIGN.md.

    Verification (run it, don't eyeball it)

    $ node cli/index.js --tokens DESIGN.md --target .
    ✔ 26/26 pairs measured
    ✔ no wild hex in components/cw-button.tsx
    exit 0 — clean
    

    Next steps

    1. Reuse the same pattern for ButtonSecondary (secondary / on-secondary, measured 17.84:1 light).
    2. Changed the brand color? Regenerate DESIGN.md from one hex at colorwaykit.com/brand — hand-edited hex bypasses the recorded measurements.
    3. Optional: connect the ColorwayKit MCP server to validate any ad-hoc pair with check_pair before using it.
    Built entirely from DESIGN.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Turn your brand color into design tokens your AI coding agent can trust.

    Give it one brand hex and it generates a complete light & dark semantic color system — 23 named roles (background, surface, text, primary, success/warning/error/info) — as DESIGN.md (the open Google Labs format), W3C DTCG tokens.json, and adapters for AGENTS.md, CLAUDE.md and .cursorrules.

    What makes it different:

    • Measured, not guessed. Every text/background pair is checked with WCAG 2.1 ratios and APCA Lc values, computed by the same engine that powers colorwaykit.com — not generated from a model's memory of what looks accessible.

    • Color-blind checked. A CVD (color-vision deficiency) report flags pairs and semantic roles that collapse under protanopia, deuteranopia, tritanopia and achromatopsia (CIEDE2000), so error/success/warning states stay distinguishable for the ~8% of users with color-vision deficiency.

    • Fixes, not just failures. Failing pairs come with hue-preserving fix suggestions, so the brand stays recognizable while contrast passes.

    • CI-ready verification. Ships with a zero-dependency linter (Node 18+): node cli/index.js --tokens DESIGN.md --target . — exit 1 on wild hex values or failing pairs. Wire it into CI so new colors go through the file first.

    Install: unzip into your agent's skills directory (~/.claude/skills/ for Claude Code), or drop the unzipped folder in and start a new session.

    Source & updates: https://github.com/5zjk5/colorwaykit-for-agents (MIT — free forever, versioned with your repo).

    Focuses exclusively on color tokens. Typography, spacing, and border radii are not covered and rely on your framework defaults. Requires a valid DESIGN.md file at the repository root.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    • Free with an Agensi account

    Requires

    colorwaykit-lint
    Node.js

    Permissions

    Terminal / Shell
    Read Files
    Listed1 month ago
    Updated24 days ago

    What's inside

    Frequently Asked Questions

    This skill eliminates 'hex-code drift' by forcing the AI to reference your specific DESIGN.md tokens and semantic roles, ensuring 100% adherence to your brand guidelines while preventing accessibility failures like poor contrast.

    It is compatible with any AI agent that supports file context and terminal access, including Claude Dev, Roo Code, and Windsurf, and it integrates seamlessly with Tailwind CSS and standard CSS Custom Properties.

    You receive the core skill configuration, a template for the required DESIGN.md token file, and access to the ColorwayKit CLI tools for automated linting and contrast validation.

    Setup is straightforward: you place the DESIGN.md file in your project root and configure the skill to prioritize these tokens; full instructions for connecting the ColorwayKit MCP server for live validation are also provided.

    No, this skill is focused exclusively on color tokens and accessibility; you will still need to manage typography, spacing, and other layout constraints through your standard framework defaults.

    The skill supports both WCAG 2.1 and the modern APCA contrast algorithms, ensuring your generated components meet the highest global accessibility standards for both light and dark modes.

    New in Agents & Orchestration