eye-of-the-beholder

Reviews screenshots of layouts, color systems, and animations against observational design criteria.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill eye-of-the-beholder-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eye-of-the-beholder
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/eye-of-the-beholder/skills/eye-of-the-beholder
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill eye-of-the-beholder-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents write CSS and only look at the rendered result once, confirming what they intended rather than observing what is actually on screen. This Skill replaces confirmatory checking with a disciplined observation loop: screenshot after every layout change, describe what you see before reading the code, then fix and repeat. ## Core Features & Use Cases - Complaint-to-axis translation: Maps vague user feedback ("too busy", "it jumps", "looks cheap") to concrete visual axes like density, layout stability, spacing, color contrast, z-stacking, and animation timing. - Structured observation protocol: Provides ordered inspection questions covering edge tracing, rhythm, odd-one-out detection, icon/viewBox clipping, optical centering, and WCAG contrast math with explicit ratio thresholds. - Credibility and token audits: Detects vibe-coded design tells (gradients, status dots, nested cards) and audits color token systems for bypass patterns, undefined tokens, and insufficient luminance deltas. - Use Case: A user says a dashboard "feels cramped". The Skill translates this to the space axis, measures padding against the 2.5x body-font threshold, identifies collapsed internal rhythm, and verifies each fix with a fresh screenshot. ## Quick Start Take a screenshot of the current page and review it with the eye-of-the-beholder skill, describing what you observe before changing any CSS.

Frequently Asked Questions about eye-of-the-beholder

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

FAQPage Schema
How do I review a UI screenshot for layout problems?▼

Screenshot after every layout change, then describe what you see before reading the CSS. Scan clockwise from top edge, name the nearest element at each edge, check rhythm between repeating elements, and express every measurement as a ratio against a threshold such as 2.5x body-font padding.

How to check WCAG color contrast ratios for text?▼

Compute relative luminance per channel with the WCAG 2.1 formula, then divide the lighter luminance plus 0.05 by the darker plus 0.05. Body text needs 4.5:1 for AA, large text and UI components need 3:1, and adjacent surfaces need at least a 1.07x luminance ratio.

Why does my SVG icon look clipped at the edges?▼

SVG defaults to overflow hidden, so any path extending outside the viewBox is silently clipped. For stroke-based icons add half the stroke-width to the path bounds, then fix by enlarging the viewBox or shrinking the path rather than using overflow visible.

Why is an element hidden behind another element in my UI?▼

The element is usually occluded in the z-axis, not mispositioned. Check sibling source order in stack containers, modifier chain order, and material layers like backdrop-filter or glass effects that promote themselves above overlays, then reorder or add a compositing boundary before touching offsets.

What are the signs of AI-generated or vibe-coded UI design?▼

Common tells include purple gradients, decorative glow, emoji as icons, cards nested in cards, meaningless status dots, and colored accent ribbons that encode nothing. Credible products group with typography and whitespace, reserve color for meaning on text, and use monospace for data values.

When should visual review happen during front-end development?▼

Review is a continuous working method, not a final step. After writing each block of layout CSS or a transition, capture a screenshot or recording, observe it against the inspection questions, compare with intention, fix, and repeat until the rendered result matches the design intent.