/visual-validation
Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions
Claude Code
$ npx -y skills add alinaqi/maggy --skill visual-validation --agent claude-code
Codex
$ npx skills add alinaqi/maggy --skill visual-validation -a codex -y
Cursor
$ npx skills add alinaqi/maggy --skill visual-validation -a cursor -y
Gemini CLI
$ npx skills add alinaqi/maggy --skill visual-validation -a gemini-cli -y
GitHub Copilot
$ npx skills add alinaqi/maggy --skill visual-validation -a github-copilot -y
OpenCode
$ npx skills add alinaqi/maggy --skill visual-validation -a opencode -y
Windsurf
$ npx skills add alinaqi/maggy --skill visual-validation -a windsurf -y
SKILL.md
visual-validation.SKILL.mdname: visual-validation
description: Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions
when-to-use: When a UI or static-asset change needs visual verification before shipping
user-invocable: false
effort: medium
Visual Validation — Autonomous Screenshot Verification
Philosophy
Every UI change should be visually verified before it ships. Peekaboo captures pixel-accurate screenshots. The system compares before/after and flags visual regressions. No manual "looks good to me" — the machine verifies what the machine built.
Autonomous Flow
static/* files modified (detected by auto-review-hook or E2E testkit)
↓
peekaboo image --mode screen → ~/.maggy/visual-verify/after-{ts}.png
↓
Compare with latest baseline (previous after-*.png)
↓
AI evaluation: Gemini Flash analyzes screenshot for visual regressions
↓
Report: CLEAN or REGRESSION_DETECTED with specific issuesQuick Commands
# Install
brew install steipete/tap/peekaboo
# Capture full system screenshot
peekaboo image --mode screen --retina --path /tmp/screen.png
# Capture specific window
peekaboo image --mode window --app "Google Chrome" --path /tmp/window.png
# Verify Maggy dashboard after code change
peekaboo image --mode window --app "Google Chrome" --path ~/.maggy/visual-verify/after-$(date -u +%Y%m%d-%H%M%S).png
# Compare two screenshots
ls -la ~/.maggy/visual-verify/after-*.png # review before/after pairs
Autonomous Verification Flow (Claude Code)
# After making any static/ file change, Claude should:
1. git add maggy/maggy/static/ && git diff --stat HEAD # check what changed
2. Restart Maggy: lsof -ti :8080 | xargs kill && python3 -m maggy.main &
3. Wait for health: curl -s http://localhost:8080/api/health
4. Capture screenshot: peekaboo image --mode screen --path ~/.maggy/visual-verify/after-$(date -u +%Y%m%d-%H%M%S).png
5. Compare with latest baseline in ~/.maggy/visual-verify/
6. AI evaluation: ~/bin/gemini-api --flash "Analyze this screenshot for visual regressions"
7. Report findings
Maggy Dashboard Verification
# One-shot verification
curl -s http://localhost:8080/api/health && \
peekaboo image --mode screen --path ~/.maggy/visual-verify/verify.png && \
echo "✓ Dashboard verified — screenshot at ~/.maggy/visual-verify/verify.png"
Integration Points
Auto-Review Hook (already wired)
- Detects `static/` changes in git diff
- Auto-captures Peekaboo screenshot
- Saves before/after pairs in `~/.maggy/visual-verify/`
E2E Testkit Plugin
- Visual regression testing as part of `POST /api/testkit/run`
- Compares screenshots against baselines
- Flags pixel differences above threshold
Build-in-Public Plugin
- Peekaboo screenshots replace AI-generated images
- Real product captures for LinkedIn/X posts
When to Use
| Scenario | Command | |----------|---------| | After static/ change | `peekaboo image --mode screen --path ~/.maggy/visual-verify/after.png` | | Before committing UI change | Run verification flow above | | Reviewing dashboard | Screenshot + AI analysis | | Build-in-public post | Auto-captured by plugin | | Cross-browser check | `peekaboo image --mode window --app "Safari"` |
Read more
name: visual-validation description: Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions when-to-use: When a UI or static-asset change needs visual verification before shipping user-invocable: false effort: medium
Visual Validation — Autonomous Screenshot Verification
Philosophy
Every UI change should be visually verified before it ships. Peekaboo captures pixel-accurate screenshots. The system compares before/after and flags visual regressions. No manual "looks good to me" — the machine verifies what the machine built.
Autonomous Flow
static/* files modified (detected by auto-review-hook or E2E testkit)
↓
peekaboo image --mode screen → ~/.maggy/visual-verify/after-{ts}.png
↓
Compare with latest baseline (previous after-*.png)
↓
AI evaluation: Gemini Flash analyzes screenshot for visual regressions
↓
Report: CLEAN or REGRESSION_DETECTED with specific issuesQuick Commands
# Install brew install steipete/tap/peekaboo # Capture full system screenshot peekaboo image --mode screen --retina --path /tmp/screen.png # Capture specific window peekaboo image --mode window --app "Google Chrome" --path /tmp/window.png # Verify Maggy dashboard after code change peekaboo image --mode window --app "Google Chrome" --path ~/.maggy/visual-verify/after-$(date -u +%Y%m%d-%H%M%S).png # Compare two screenshots ls -la ~/.maggy/visual-verify/after-*.png # review before/after pairs
Autonomous Verification Flow (Claude Code)
# After making any static/ file change, Claude should: 1. git add maggy/maggy/static/ && git diff --stat HEAD # check what changed 2. Restart Maggy: lsof -ti :8080 | xargs kill && python3 -m maggy.main & 3. Wait for health: curl -s http://localhost:8080/api/health 4. Capture screenshot: peekaboo image --mode screen --path ~/.maggy/visual-verify/after-$(date -u +%Y%m%d-%H%M%S).png 5. Compare with latest baseline in ~/.maggy/visual-verify/ 6. AI evaluation: ~/bin/gemini-api --flash "Analyze this screenshot for visual regressions" 7. Report findings
Maggy Dashboard Verification
# One-shot verification curl -s http://localhost:8080/api/health && \ peekaboo image --mode screen --path ~/.maggy/visual-verify/verify.png && \ echo "✓ Dashboard verified — screenshot at ~/.maggy/visual-verify/verify.png"
Integration Points
Auto-Review Hook (already wired)
- Detects `static/` changes in git diff
- Auto-captures Peekaboo screenshot
- Saves before/after pairs in `~/.maggy/visual-verify/`
E2E Testkit Plugin
- Visual regression testing as part of `POST /api/testkit/run`
- Compares screenshots against baselines
- Flags pixel differences above threshold
Build-in-Public Plugin
- Peekaboo screenshots replace AI-generated images
- Real product captures for LinkedIn/X posts
When to Use
| Scenario | Command | |----------|---------| | After static/ change | `peekaboo image --mode screen --path ~/.maggy/visual-verify/after.png` | | Before committing UI change | Run verification flow above | | Reviewing dashboard | Screenshot + AI analysis | | Build-in-public post | Auto-captured by plugin | | Cross-browser check | `peekaboo image --mode window --app "Safari"` |
Turn Claude Code into a self-reviewing, test-enforced engineering system that remembers context across sessions — then route work across 13 models from a single dashboard.
Other skills on maggy.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about visual-validation.
- Which coding agents can use visual-validation?
- visual-validation installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

