Prove a UI change is live, readable and phone-safe

    1

    Covers review gates, protected branches, dirty-tree deploys and why 'CI green' is not 'live'.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Prove a UI change is live, readable and phone-safe

    Example session with this skill installed

    Six text samples in the format produced by references/extract-colors.js (computed colors written for illustration), including a semi-transparent nav link and a white label inside a 95% white panel on a dark bar.
    Command: python3 scripts/wcag_contrast.py --samples contrast_samples.json

    • Read your context and instructions
    • Compiled the prove a ui

    FAIL 3.47:1 (need 4.5) header nav a Pricing
    FAIL 1.08:1 (need 4.5) nav.bottom > div.panel span Home
    FAIL 4.48:1 (need 4.5) main p.muted Updated 3 days ago
    PASS 6.21:1 (need 4.5) main p.muted Updated 3 days ago (fixed)
    PASS 4.48:1 (need 3.0) main h1 Plan your week
    PASS 18.88:1 (need 4.5) button.primary Start free
    TOTAL=6 FAILED=3
    Note: Real run of the contrast script; the color samples were written for illustration, not captured from a specific site.

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

    About this skill

    What it does: a release checklist for frontend changes that turns 'I changed the UI' into evidence. It defines six release states (source edited, verified locally, committed, pushed, deployed, live verified) with the proof each one needs, catches stale dev servers with a sentinel, tests sticky headers, fixed overlays, menus and reveal-on-scroll numerically instead of by screenshot, gates color changes with a contrast script fed by computed colors plus element screenshots, and verifies the custom domain by finding a new string and confirming the old one is gone. Covers review gates, protected branches, dirty-tree deploys and why 'CI green' is not 'live'. Who it is for: developers and agents shipping web UI to production, especially when a non-technical owner relies on the status report. What is inside: SKILL.md workflow and checklist; scripts/wcag_contrast.py (alpha compositing, layered backgrounds, AA/AAA, CI exit code, self-test); references/extract-colors.js (read-only in-page color dump). Limits: you still need a browser or automation tool for the in-page steps; the contrast script does not parse oklch/hsl and says so.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    • Contrast over background images or gradients must be checked visually; the snippet flags them.
    • oklch(), hsl() and color() values must be converted to rgb first.
    • Hosting-specific deploy commands are described generally, not for every platform.
    • It cannot verify a site you have no access to deploy or inspect.

    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 buying a skill.

    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

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed today

    • Free with an Agensi account

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Listedtoday

    What's inside

    Frequently Asked Questions

    Screenshot review routinely misses low-contrast text and cannot prove sticky or overlay behavior. The skill pairs numeric checks with element screenshots.

    The custom domain serves a string unique to the new build and the old string is gone, checked separately from the deployment URL.

    Yes. The steps are framework-neutral; examples use common git and browser commands.

    The contrast script exits with code 1 on any failure, so it can gate a pipeline once you collect samples in a headless browser.

    New in Frontend & Web Apps

    Free