Loading…
Audit a project's theme, design tokens, and colour accessibility — WCAG contrast across every theme, focus indicators, and design-system hygiene (hardcoded colours bypassing tokens, orphan/unwired tokens, theme parity drift, diluted text utilities) — then fix what's broken and prove it with a rendered-DOM sweep. Use this whenever the user mentions a theme audit, design tokens, colour contrast, WCAG or a11y for colour, dark mode parity, "is my palette accessible", CSS variables organization, hardcoded colours, or asks to review/clean up/reorganize a design system's colours — and also when they ask to check accessibility of a site's look, fix unreadable or washed-out text, make focus states visible, or audit a theme they just built, even if they never say "tokens" or "contrast".
audit-theme-tokens is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Theme & design-token audit Two questions, answered with measurements rather than impressions: 1. **Is it legible?** Does every token pair clear its WCAG thres. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding audit-theme-tokens to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install ersanyamarya/nisha-portfolioReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Theme & design-token audit Two questions, answered with measurements rather than impressions: 1. **Is it legible?** Does every token pair clear its WCAG threshold, in every theme