Visual Proof

Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show me what it looks like", check responsive behavior, verify dark mode, or confirm a layout does not break on mobile. Reports honestly when a browser or server is unavailable rather than describing a page it never rendered.

48 stars 6 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add frankxai/claude-skills-library

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add frankxai/claude-skills-library --skill visual-proof
Manual install
git clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/packs/web-excellence/skills/visual-proof ~/.claude/skills/visual-proof

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Visual Proof

Screenshots are the only claim about a page's appearance that cannot be
hallucinated. Capture before you change anything, and after.

If you cannot capture — no server, no Chromium, no network to the deployed URL —
**say so and stop making visual claims.** Describing a page you never rendered
is the single most common way UI work goes wrong undetected.

## The matrix

Six shots per state. Not one, not a single desktop hero crop.

| Width | Stands for |
|---|---|
| 375 | phone — where layouts actually break |
| 768 | tablet / the awkward middle breakpoint |
| 1440 | desktop |

× light and dark, if the site ships both themes.

## Run it

The pack ships a runner. From the repo root:

```bash
# against a local dev server
node .claude/skills/visual-proof/capture.mjs --url http://localhost:3000/ --label before

# ...make the change...
node .claude/skills/visual-proof/capture.mjs --url http://localhost:3000/ --label after

# or against a deployed preview
node .claude/skills/visual-proof/capture.mjs --url https://<preview>.vercel.app/pricing --label after
```

Output lands in `.visual-proof/<label>/<width>-<theme>.png` and the script prints
each path. `.visual-proof/` belongs in `.gitignore` — these are evidence for the
turn, not repo artifacts.

Flags: `--widths 375,768,1440` · `--themes light,dark` · `--full` (full-page
instead of viewport) · `--reduced-motion` (emulates `prefers-reduced-motion:
Read the full skill on GitHub

Details

Skill name
visual-proof
Path
packs/web-excellence/skills/visual-proof/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Visual Proof skill do?

Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show me what it looks like", check responsive behavior, verify dark mode, or confirm a layout does not break on mobile. Reports honestly when a browser or server is unavailable rather than describing a page it never rendered.

How do I install the Visual Proof skill?

Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Visual Proof popular?

It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.

Related skills

Acos Meta

48

frankxai/claude-skills-library

ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.

Software Development

Acos Visual Gen

48

frankxai/claude-skills-library

Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.

Images, Video & Audio

Agent Harness Construction

48

frankxai/claude-skills-library

Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.

AI, LLMs & Agents

Add Puzzle Type

45

pjt222/agent-almanac

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

Testing & QAIn 1 list

TDD

43

0xranx/agentbrief

Red-green-refactor cycle for test-driven development

Testing & QA

Analyze Prime Numbers

45

pjt222/agent-almanac

Analyze prime numbers using primality tests, factorization algorithms, prime distribution analysis, and sieve methods. Covers trial division, Miller-Rabin, Sieve of Eratosthenes, and the Prime Number Theorem. Use when determining whether an integer is prime or composite, finding prime factorizations, counting or listing primes up to a bound, or investigating prime properties within a number-theoretic proof or computation.

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.