eyes

Capture UI screenshots and compare states using Playwright MCP tools.

21|6|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/mintuz/claude-plugins --skill eyes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eyes
Source: https://github.com/mintuz/claude-plugins/tree/main/plugins/web/skills/eyes
Command: npx skills add https://github.com/mintuz/claude-plugins --skill eyes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture visual feedback for UI elements and coordinate fixes efficiently, reducing time-to-ship for visual defects.

Core Features & Use Cases

  • Structured visual feedback loop: Capture screenshots, compare states, and collect user input to drive precise changes.
  • Playwright MCP tooling: Leverage browser_navigate, browser_take_screenshot, browser_snapshot, and related commands to document and validate UI issues.
  • Collaboration and approval: Present proposed changes to stakeholders and require explicit confirmation before applying edits.

Quick Start

Use the eyes skill to capture a screenshot of the target UI, describe the required changes, and await explicit approval before implementing.

Frequently Asked Questions about eyes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture UI screenshots for visual feedback using Playwright?

You can capture UI screenshots for visual feedback using Playwright MCP tools like browser_navigate and browser_take_screenshot to document issues. This skill automates the capture process, generating visual comparisons to drive precise collaborative fixes across QA stages.

What is a structured visual feedback loop for UI fixes?

A structured visual feedback loop for UI fixes is a workflow that captures screenshots, compares UI states, and collects user input. This process drives precise visual changes by requiring explicit stakeholder approval before applying any edits to the web interface.

Can I use Playwright MCP to automate UI review and bug documentation?

Yes, you can use Playwright MCP to automate UI review and bug documentation. It leverages browser commands like browser_snapshot to navigate and capture web interface states, creating a documented feedback loop to confirm visual changes before deployment.

Does this visual feedback skill require stakeholder confirmation before applying UI fixes?

Yes, this visual feedback skill requires explicit stakeholder confirmation before applying UI fixes. It presents proposed changes based on captured screenshots and awaits approval to ensure coordinated, verified visual improvements across the deployment pipeline.

What is the best way to coordinate collaborative fixes for visual defects?

The best way to coordinate collaborative fixes for visual defects is to use a structured feedback loop with screenshot comparisons. This approach captures user input on UI elements, requiring explicit approval before edits to reduce time-to-ship for visual bugs.