agentleFS
Tsuchiya2Tsuchiya2/evaluator-driven-agent-flow/.claude/skills/ui-verification/SKILL.md

ui-verification

Skill1 starsChanged 10 months agoMITView on GitHub

Skill Type: Verification Pattern Library Used By: ui-verification-worker, Main Agent (Phase 5) Trigger: When frontend files are modified in Phase 4 Method: MCP chrome-devtools This skill provides reusable patterns for UI/UX verification using Claude in Chrome. It uses a subagent-based approach where browser interactions are delegated to a general-purpose agent with access to Claude in Chrome extension. Automatic Trigger Conditions: This skill is automatically loaded when: 1. ui-verification-worker is launched 2. Phase 5 detects frontend changes 3. User asks Claude…

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. mblode/agent-skills★ 189same name
    2. Kainiko943/beautiful-ui★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Trigger: When frontend files are modified in Phase 4

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI Verification Skill

Skill Type: Verification Pattern Library Used By: ui-verification-worker, Main Agent (Phase 5) Trigger: When frontend files are modified in Phase 4 Method: MCP chrome-devtools


Overview

This skill provides reusable patterns for UI/UX verification using Claude in Chrome. It uses a subagent-based approach where browser interactions are delegated to a general-purpose agent with access to Claude in Chrome extension.


When to Use This Skill

Automatic Trigger Conditions:

  1. Frontend files modified:
    • **/components/**/*
    • **/pages/**/*
    • **/views/**/*
    • **/*.css, **/*.scss, **/*.sass, **/*.less
    • **/src/**/*.{tsx,jsx,ts,js,vue,svelte}
  2. Phase 5 Code Review Gate active
  3. User has MCP chrome-devtools server configured

Skill Contents

FilePurpose
SKILL.mdThis overview file
BROWSER-AUTOMATION.mdClaude in Chrome subagent patterns
SCREENSHOT-GUIDE.mdScreenshot naming and storage conventions
CHECKLIST.mdVerification checklist template
REPORT-TEMPLATE.mdMarkdown report template
USER-GUIDE.mdUser guide for manual verification

Quick Reference

Subagent Approach

// Launch subagent with Claude in Chrome access
const verificationResult = await Task({
  subagent_type: 'general-purpose',
  model: 'sonnet',
  description: 'UI verification via Claude in Chrome',
  prompt: `You are a UI verification specialist using Claude in Chrome...

  **Tasks**:
  1. Open browser with Claude in Chrome extension
  2. Navigate to pages and capture screenshots
  3. Test interactive elements
  4. Check console for errors
  5. Return structured JSON report
  `
})

Directory Structure

.steering/{YYYY-MM-DD}-{feature-name}/
├── screenshots/
│   ├── login-page.png
│   ├── login-filled.png
│   ├── login-success.png
│   ├── {page-name}.png
│   └── {page-name}-{action}.png
└── reports/
    └── phase5-ui-verification.md

Integration with EDAF

This skill is automatically loaded when:

  1. ui-verification-worker is launched
  2. Phase 5 detects frontend changes
  3. User asks Claude Code to run UI verification

Key Difference from MCP Approach:

  • ❌ No MCP server setup required
  • ❌ No WSL2 environment restrictions
  • ✅ Uses official Claude in Chrome extension
  • ✅ Subagent handles all browser interactions
  • ✅ Works across all platforms

Subagent Workflow

Main Worker
    ↓
    ├─→ Collect requirements (dev server URL, login info)
    ├─→ Identify modified pages from design doc
    ├─→ Create screenshot directory
    ↓
Launch Subagent (general-purpose)
    ↓
    ├─→ Open browser with Claude in Chrome
    ├─→ Authenticate (if required)
    ├─→ For each page:
    │     ├─→ Navigate to page
    │     ├─→ Capture screenshot
    │     ├─→ Test interactive elements
    │     └─→ Check console errors
    ↓
Return JSON report to main worker
    ↓
Main Worker
    ├─→ Parse JSON results
    ├─→ Generate markdown report
    └─→ Verify all screenshots saved

Advantages

Claude in Chrome Benefits:

  • ✅ Official Support: Anthropic's official extension
  • ✅ No Setup: No MCP server configuration needed
  • ✅ Cross-Platform: Works on macOS, Linux, Windows, WSL2
  • ✅ Flexible: Subagent can handle complex scenarios
  • ✅ Maintainable: Less infrastructure to manage
  • ✅ Reliable: Direct browser integration

Related Resources

  • Worker: .claude/agents/workers/ui-verification-worker.md
  • Report Template: REPORT-TEMPLATE.md (same directory)
  • User Guide: USER-GUIDE.md (same directory)
  • Checklist: CHECKLIST.md (same directory)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.