Agent skill

Visual Acceptance Review

by Jason904 in Jason904/ui-skill-lab

This skill should be used after spec-compliance-review and before visual-diff-fix.

MITAuto-check passedTesting & QA

Install Visual Acceptance Review

skills CLI
$ npx skills add Jason904/ui-skill-lab --skill visual-acceptance-review -a claude-code

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

GitHub CLI
$ gh skill install Jason904/ui-skill-lab visual-acceptance-review --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/Jason904/ui-skill-lab.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/visual-acceptance-review .claude/skills/visual-acceptance-review && 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
visual-acceptance-review
GitHub stars
144
Token cost
~1.1k tokens
SKILL.md length
356 words
Files
16 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used after spec-compliance-review and before visual-diff-fix.

  • Works in 10 steps: reference.png → actual browser screenshot → visual-analysis.md / UI Type… → …
  • Tasks that involve Visual regression testing
  • SKILL.md covers Trigger Conditions, Required Inputs, Preflight Gates and Source of Truth, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Visual Acceptance Review is an agent skill from Jason904/ui-skill-lab. This skill should be used after spec-compliance-review and before visual-diff-fix. It captures or analyzes actual browser screenshots and compares them against the reference design, responsive spec, visual tokens, layout spec, component tree, UI type, layout paradigm, and asset strategy. It outputs structured visual diff reports and fix-tasks without modifying code.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `README.md`, `examples/acceptance-summary.example.md` and `examples/blocked-report.example.md`).

It sits in Testing & QA, covering Visual regression testing and Regulatory compliance. The repository describes itself as: AI-driven UI development skill pipeline — test lab for Codex skills covering PRD-to-pixel workflow. The licence is MIT.

When your agent uses it

  • Tasks that involve Visual regression testing
  • Tasks that involve Regulatory compliance

Example prompts

  • “/visual-acceptance-review”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. reference.png
  2. actual browser screenshot
  3. visual-analysis.md / UI Type Classification
  4. layout-spec.md / Layout Paradigm
  5. implementation-risks.md / Asset Strategy
  6. component-tree.md
  7. tokens.json
  8. responsive-spec.md
  9. 05_design_system/
  10. browser health logs

What it can do on your machine

Read from SKILL.md and the folder at commit a71b4e2. 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.

    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

Visual Acceptance Review loads about 1.1k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 356 words of instructions outside code blocks.

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

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 Jason904/ui-skill-lab at commit a71b4e2, republished under its MIT licence (© Jason904). 356 words, ~1,073 tokens.

Download SKILL.mdSave it as .claude/skills/visual-acceptance-review/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.
name
visual-acceptance-review
description
This skill should be used after spec-compliance-review and before visual-diff-fix. It captures or analyzes actual browser screenshots and compares them against the reference design, responsive spec, visual tokens, layout spec, component tree, UI type, layout paradigm, and asset strategy. It outputs structured visual diff reports and fix-tasks without modifying code.
argument-hint
[dev-server-url-or-actual-screenshot]

Version: 2.0.0

visual-acceptance-review

Validate real browser rendering against the approved visual contract.

This skill performs screenshot-based visual acceptance and produces structured fix tasks.

It does not modify code. It does not redesign UI. It does not replace spec-compliance-review.

Trigger Conditions

Use this skill when:

  • implementation exists
  • spec-compliance-review has passed or user requests diagnostic-only review
  • a dev server URL is available
  • Playwright or screenshot capability is available
  • user asks to compare implementation against reference image
  • user asks for visual acceptance report or visual diff tasks

Required Inputs

  • reference.png
  • dev server URL or actual screenshot
  • UI workflow files under ui/03_visual_spec/
  • visual spec review files under ui/04_visual_spec_review/
  • design system files under ui/05_design_system/

Recommended:

  • spec compliance outputs under ui/06_spec_review/
  • package.json
  • playwright.config.*

Preflight Gates

Stop if:

  • ui/04_visual_spec_review/spec-review-report.md says Fail
  • ui/06_spec_review/compliance-report.md says Fail, unless user explicitly requests diagnostic-only mode
  • no screenshot capability exists and no actual screenshot is provided

Source of Truth

  1. reference.png
  2. actual browser screenshot
  3. visual-analysis.md / UI Type Classification
  4. layout-spec.md / Layout Paradigm
  5. implementation-risks.md / Asset Strategy
  6. component-tree.md
  7. tokens.json
  8. responsive-spec.md
  9. 05_design_system/
  10. browser health logs

Main Workflow

  1. Run preflight gates.
  2. Capture or load screenshots.
  3. Compare overall visual match.
  4. Validate UI Type, Layout Paradigm, and Asset Strategy.
  5. Compare regions using layout-spec.md.
  6. Compare components using component-tree.md.
  7. Compare colors, typography, spacing, and density.
  8. Validate responsive screenshots against responsive-spec.md.
  9. Capture browser health issues.
  10. Generate reports and fix-tasks.json.
Show full SKILL.md (121 more words)Show less

Hard Rules

  • Do not modify code.
  • Do not modify visual spec files.
  • Do not modify design system files.
  • Do not modify OpenSpec files.
  • Do not redesign UI.
  • Do not claim pixel-precision if no script-backed comparison exists.
  • Do not compare mobile/tablet directly against desktop reference.png.
  • Do not allow actual rendering to change UI Type, Layout Paradigm, or Asset Strategy.
  • Do not treat passing tests as visual acceptance.
  • Do not treat internal spec consistency as visual acceptance.
  • If a photorealistic/panorama/scene-led main visual is missing or redrawn with CSS/SVG/chart/map, mark as Fail.

Output

Write:

text
07_validation/visual_acceptance/
  screenshots/
    reference.png
    actual-desktop-hd.png
    actual-desktop.png
    actual-tablet.png
    actual-mobile.png
  comparison-report.md
  acceptance-summary.md
  fix-tasks.json
  region-diffs/
    overview.md
    layout.md
    components.md
    colors.md
    typography.md
    spacing.md
    responsive.md
    asset-strategy.md
    browser-health.md
  console-errors.log
  network-errors.log
  blocked-report.md

blocked-report.md is only required when preflight blocks the review.

Supporting Files

Read these references directly:

  • references/acceptance-workflow.md
  • references/preflight-gates.md
  • references/screenshot-rules.md
  • references/comparison-rules.md
  • references/ui-type-asset-validation.md
  • references/confidence-rules.md
  • references/fix-task-schema.md
  • references/external-reviewer-usage.md
  • references/output-files.md

Examples:

  • examples/acceptance-summary.example.md
  • examples/comparison-report.example.md
  • examples/region-diff.example.md
  • examples/fix-tasks.example.json
  • examples/blocked-report.example.md

© Jason904, MIT. 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 15 other files (references) in skills/visual-acceptance-review of Jason904/ui-skill-lab.

  • SKILL.md
  • README.md
  • examples/acceptance-summary.example.md
  • examples/blocked-report.example.md
  • examples/comparison-report.example.md
  • examples/fix-tasks.example.json
  • examples/region-diff.example.md
  • references/acceptance-workflow.md
  • references/comparison-rules.md
  • references/confidence-rules.md
  • references/external-reviewer-usage.md
  • references/fix-task-schema.md
  • references/output-files.md
  • references/preflight-gates.md
  • references/screenshot-rules.md
  • references/ui-type-asset-validation.md

Open the folder on GitHubat commit a71b4e2

Compare with similar skills

Visual Acceptance Review 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.

Visual Acceptance Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Visual Acceptance Review this skillJason904/ui-skill-lab144—~1.1kAutomated safety check: PassMIT
Fin Guru ChecklistAojdevStudio/Finance-Guru322—~382Automated safety check: PassAGPL-3.0
Review Local UI Screenshotsxiaocang/easydict_win32104—~1.1kAutomated safety check: PassGPL-3.0
Handsontable Visual Test Demoshandsontable/handsontable22k—~1.3kAutomated safety check: PassCustom licence
Kc Screenshotimran31415/kube-coder388—~870Automated safety check: NotesMIT
Visual QAliangdabiao/Godogen126—~1.4kAutomated safety check: PassMIT

Similar skills

  • Fin Guru Checklist

    AojdevStudio/Finance-Guru

    Run a pass or fail checklist from fin-guru/checklists/ against a deliverable, such as the margin strategy, dividend framework, or cash-flow policy checklist.

    322 GitHub stars~382 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Review Local UI Screenshots

    xiaocang/easydict_win32

    Review Easydict UI automation screenshot artifacts already present in local artifacts/ui-screenshots, screenshots, or a user-provided artifact directory.

    104 GitHub stars~1.1k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Handsontable Visual Test Demos

    handsontable/handsontable

    Explains how to add or change the demo pages that Handsontable's visual regression suite photographs, including per-feature routes in the js demo and the shared grid.

    22k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Kc Screenshot

    imran31415/kube-coder

    Capture desktop + mobile, dark + light screenshots of the kube-coder dashboard SPA for visual QA of a UI change.

    388 GitHub stars~870 tokensUpdated 2 days ago
    Testing & QAAuto-check: notes
  • Visual QA

    liangdabiao/Godogen

    Visual quality assurance — analyze game screenshots for defects, compare against reference, check motion in frame sequences.

    126 GitHub stars~1.4k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Meticulous Fix

    FlintSH/Flare

    Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given.

    135 GitHub stars~2.3k tokensUpdated 5 days ago
    Testing & QAAuto-check passed

More from Jason904/ui-skill-lab

All 8 skills in this repo
  • Image2 Prompt Pack

    Jason904/ui-skill-lab

    This skill should be used when the user asks to convert a PRD, OpenSpec change, or product idea into a structured GPT Image 2 UI prompt pack for generating high-fidelity flat UI reference images.

    144 GitHub stars~1k tokensUpdated 3 mo ago
    Auto-check passed
  • Visual To Spec

    Jason904/ui-skill-lab

    A skill your agent uses when a user provides a reference UI screenshot and asks to extract visual specs, generate design tokens, create a component tree, or produce a frontend implementation…

    144 GitHub stars~1.6k tokensUpdated 3 mo ago
    Auto-check passed
  • UI UX Pro Max Skill

    Jason904/ui-skill-lab

    A skill your agent uses for UI/UX design intelligence in Codex: planning, building, reviewing, improving, or implementing web/mobile interfaces, landing pages, dashboards, design systems…

    144 GitHub stars~865 tokensUpdated 3 mo ago
    Auto-check passed
  • Design System Governor

    Jason904/ui-skill-lab

    This skill should be used after visual-spec-review passes and before OpenSpec UI update or frontend implementation.

    144 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Spec Compliance Review

    Jason904/ui-skill-lab

    This skill should be used after Codex implements a UI change and before visual acceptance review.

    144 GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check passed
  • Visual Diff Fix

    Jason904/ui-skill-lab

    This skill should be used after visual-acceptance-review has generated fix-tasks.json.

    144 GitHub stars~978 tokensUpdated 3 mo ago
    Auto-check passed

Questions about Visual Acceptance Review

What does Visual Acceptance Review do?

This skill should be used after spec-compliance-review and before visual-diff-fix. Visual Acceptance Review is an agent skill from Jason904/ui-skill-lab. This skill should be used after spec-compliance-review and before visual-diff-fix.

When should I use Visual Acceptance Review?

Visual Acceptance Review fits situations like: tasks that involve Visual regression testing; tasks that involve Regulatory compliance.

How do I install Visual Acceptance Review in Claude Code?

Run `npx skills add Jason904/ui-skill-lab --skill visual-acceptance-review -a claude-code`. Or copy the skill folder (skills/visual-acceptance-review in Jason904/ui-skill-lab) into .claude/skills/visual-acceptance-review in your project. Claude Code loads it when a task matches its description.

How do I install Visual Acceptance Review in Codex?

Run `npx skills add Jason904/ui-skill-lab --skill visual-acceptance-review -a codex`. Or copy the skill folder (skills/visual-acceptance-review in Jason904/ui-skill-lab) into .agents/skills/visual-acceptance-review in your project. Codex loads it when a task matches its description.

Can I use Visual Acceptance Review 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 Jason904/ui-skill-lab --skill visual-acceptance-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visual-acceptance-review, .gemini/skills/visual-acceptance-review, .github/skills/visual-acceptance-review and .opencode/skills/visual-acceptance-review in your project.

What does Visual Acceptance Review need to run?

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

Does Visual Acceptance Review 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 Visual Acceptance Review 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 Visual Acceptance Review use?

Visual Acceptance Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Visual Acceptance Review use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Visual Acceptance Review?

Skills that share tags, products or a category with Visual Acceptance Review: Fin Guru Checklist (AojdevStudio/Finance-Guru, 322 stars), Review Local UI Screenshots (xiaocang/easydict_win32, 104 stars), Handsontable Visual Test Demos (handsontable/handsontable, 22k stars) and Kc Screenshot (imran31415/kube-coder, 388 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Visual Acceptance Review?

Jason904 (a GitHub user) maintains it in Jason904/ui-skill-lab, which has 144 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on June 29, 2026.

Source: Jason904/ui-skill-lab on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.