Skill guide

Rendered UI inspection

Inspect visible browser screens for layout, readability, usability, and observable interaction problems.

Assess composition, character, meaningful content, and observable behavior against the intended use and experience. Identify achieved qualities that corrections should preserve. Treat a failure of a central experiential requirement according to its consequences. Exercise temporal behavior before judging it; screenshot observations cannot establish semantics, focus, or runtime behavior.

Package version 0.1.0-beta.6

Included with Faye UI System Engineer

When to use

Use this to review a finished screen, compare design variants, or check an implementation across sizes and states.

What to provide

  • A running page, screenshots, or before-and-after captures.
  • The intended use and experience, relevant viewports, expected behavior, and any areas of concern.

Expected results

  • Location-specific observations with evidence, consequence-based priority, and qualities to preserve.
  • Prioritized improvements and a clear account of which states and interactions were inspected.

Example requests

Try this request

Codex
Codex request
$ui-inspection Inspect this skill guide at 390, 768, and 1440 pixels. Check reading order, examples, source disclosures, keyboard focus, and horizontal overflow.
Grok
Grok request
/ui-inspection Inspect this skill guide at 390, 768, and 1440 pixels. Check reading order, examples, source disclosures, keyboard focus, and horizontal overflow.
Antigravity
Antigravity request
/ui-inspection Inspect this skill guide at 390, 768, and 1440 pixels. Check reading order, examples, source disclosures, keyboard focus, and horizontal overflow.

Requirements and limits

Before you start

  • Screenshots support visual inspection; a controllable browser is needed for interaction checks.
  • Provide the relevant state or a way to reach it when it is not visible initially.

Scope and limitations

  • Inspection does not edit the UI unless changes are requested.
  • A screenshot cannot prove semantics, focus movement, or hidden runtime state.
  • The optional independent reviewer is not assumed to be automatically available.
Technical source

The hosted file belongs to the package version shown on this page.

plugins/faye-ui-system-engineer/skills/ui-inspection

Open source file