/dev-visual-verdict
Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-visual-verdict --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-visual-verdict
Context preview
The summary Claude sees to decide when to auto-load this skill.
Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
SKILL.md
dev-visual-verdict.SKILL.mdname: dev-visual-verdict
description: Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
Dev Visual Verdict
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Visual regression testing. Capture before/after screenshots of UI components, compare them, and flag unintended visual impact.
Use When
- CSS / styling change that might cascade to other components
- Component refactor where the visual output should remain identical
- Theme change that needs to be verified across the app
Do Not Use When
- Backend-only changes
- Intentional redesigns (use `@canvas-designer` instead)
- Single-component changes with obvious visual outcome
Workflow
1. **Identify scope** — which components could be affected 2. **Capture baseline** — screenshot current state of each affected component 3. **Apply change** — let `@bolt-executor` make the modification 4. **Capture after** — screenshot post-change state 5. **Compare** — flag any visual differences (pixel-level or layout-level) 6. **Verdict** — IDENTICAL / EXPECTED CHANGES / UNEXPECTED REGRESSION
Output
Saved to `workspace/development/verifications/[C]visual-{component}-{date}.md`:
## Visual Verdict — {component}
### Scope
- Components checked: [list]
### Comparison
| Component | Before | After | Diff | Verdict |
|---|---|---|---|---|
| Header |  |  | 0% | IDENTICAL |
| Footer |  |  | 12% | UNEXPECTED |
### Verdict
{IDENTICAL | EXPECTED CHANGES | UNEXPECTED REGRESSION}
### Unexpected Regressions
- Footer color shifted from #1A1A1A to #2A2A2A — investigate cascadePairs With
- `@canvas-designer` (when regression is intentional)
- `@hawk-debugger` (when regression is unintended)
- `@oath-verifier` (final visual verification)
Read more
name: dev-visual-verdict description: Visual regression testing — capture before/after screenshots of UI changes and compare. Use when a UI change might have unintended visual impact across components.
Dev Visual Verdict
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Visual regression testing. Capture before/after screenshots of UI components, compare them, and flag unintended visual impact.
Use When
- CSS / styling change that might cascade to other components
- Component refactor where the visual output should remain identical
- Theme change that needs to be verified across the app
Do Not Use When
- Backend-only changes
- Intentional redesigns (use `@canvas-designer` instead)
- Single-component changes with obvious visual outcome
Workflow
1. **Identify scope** — which components could be affected 2. **Capture baseline** — screenshot current state of each affected component 3. **Apply change** — let `@bolt-executor` make the modification 4. **Capture after** — screenshot post-change state 5. **Compare** — flag any visual differences (pixel-level or layout-level) 6. **Verdict** — IDENTICAL / EXPECTED CHANGES / UNEXPECTED REGRESSION
Output
Saved to `workspace/development/verifications/[C]visual-{component}-{date}.md`:
## Visual Verdict — {component}
### Scope
- Components checked: [list]
### Comparison
| Component | Before | After | Diff | Verdict |
|---|---|---|---|---|
| Header |  |  | 0% | IDENTICAL |
| Footer |  |  | 12% | UNEXPECTED |
### Verdict
{IDENTICAL | EXPECTED CHANGES | UNEXPECTED REGRESSION}
### Unexpected Regressions
- Footer color shifted from #1A1A1A to #2A2A2A — investigate cascadePairs With
- `@canvas-designer` (when regression is intentional)
- `@hawk-debugger` (when regression is unintended)
- `@oath-verifier` (final visual verification)
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

