Agent skill · Testing & QA

visual-polish-qa

Inspect, test, and refine frontend visual quality before delivery. Use after building or editing websites, landing pages, portfolios, dashboards, games, interactive tools, cinematic sites, luxury sites, or any UI where Codex should run a second polish pass for responsive layout, typography, spacing, hierarchy, motion, accessibility, and browser-rendered correctness.

TheGoat395github.com/TheGoat395GitHub ↗
claude-codecodexcursorMIT
Install
npx skills add TheGoat395/Codex-Skills --skill visual-polish-qa --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/visual-polish-qa/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 115
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Visual Polish QA ## Principle Do not stop when the code compiles. Inspect the rendered result, identify visible weaknesses, improve it, then run checks again. ## Required Loop 1. Start or locate the dev server when the project needs one. 2. Open the site in a browser or capture screenshots when tooling is available. 3. Check desktop and mobile widths. 4. Inspect hero, navigation, major sections, interactive states, forms, media, and footer. 5. Fix obvious visual defects and weak polish. 6. Re-run build/lint/test commands available in the repo. 7. Report what was checked and what could not be checked. ## What To Look For - Text overflow, awkward line breaks, cramped labels, clipped buttons. - Elements overlapping or drifting outside their intended layout. - Hero media that is too dark, blurry, cropped, generic, or disconnected from the subject. - Repetitive card grids and generic spacing. - Typography that lacks hierarchy or scale discipline. - Weak button states, missing focus styles, inert hover states. - Motion that is too fast, too busy, inaccessible, or unrelated to hierarchy. - Mobile layouts that simply stack without composition. - Desktop layouts that stretch content too w

What's inside
Steps it walks through
  1. Principle
  2. Required Loop
  3. What To Look For
  4. Fix Biases
  5. Verification
Ships with 2 files
  • agents/openai.yaml
  • references/polish-checklist.md
More from Codex-Skills
All skills →
About this skill
What does the visual-polish-qa skill do?

Inspect, test, and refine frontend visual quality before delivery. Use after building or editing websites, landing pages, portfolios, dashboards, games, interactive tools, cinematic sites, luxury sites, or any UI where Codex should run a second polish pass for responsive layout, typography, spacing, hierarchy, motion, accessibility, and browser-rendered correctness.

How do I install it?

Run `npx skills add TheGoat395/Codex-Skills --skill visual-polish-qa --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From TheGoat395/Codex-Skills, a repository with 115 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going