Individual skill

visual-playtest

Visually inspect a local or deployed site/app in a real browser and report concrete layout, responsive, or design regressions. Use when asked to visually check UI changes, reproduce a screenshot issue, compare a page with a reference, or playtest representative visual states. Do not use for code-only review or open-ended design ideation.

visual-playtest/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 196
Repository last updated: Nov 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

design Derived category
design-interface Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 2,908 bytes
agents/openai.yamlasset · 258 bytes
references/app-interactions.mddoc · 1,379 bytes
references/media-workflows.mddoc · 1,876 bytes

Read excerpt


# Visual Playtest

Use the applicable browser-control skill. Match the effort to the request: a
static page review is not a full product certification.

For Chrome, follow [resilient-computer-use](../resilient-computer-use/SKILL.md#chrome-default-bind-to-a-tab): use a dedicated tab bound by stable ID for actions, screenshots, viewport changes, and console inspection. The user and other Codex chats may keep using Chrome concurrently; coordinate shared focus before any native desktop fallback.

## Choose the scope

Identify the few states that can materially change the result: named pages,
viewport ranges, theme, scroll position, navigation state, and persistent or
fixed UI. Reproduce the user's reported combination before exploring adjacent
states.