Individual skill

visual-polish-qa

0upvotes

Refine rendered finish at accepted viewports.

skills/visual-polish-qa/SKILL.md

Read pinned source

Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d

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 6, 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): 137
Repository last updated: Oct 22, 2026
License: MIT

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

accessibility Repository topic
codex Repository topic
codex-skills Repository topic
frontend Repository topic
motion Repository topic
nextjs Repository topic
react Repository topic
tailwind Repository topic
web-design Repository topic
agent-skills Repository topic
design 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,511 bytes
agents/openai.yamlasset · 234 bytes
references/polish-checklist.mddoc · 1,392 bytes

Read excerpt


# Visual Polish QA

## Principle

Inspect affected rendered output after implementation. Fix observed weaknesses within authorization and recheck affected behavior; stop when acceptance is met. An analysis-only review reports findings without edits.

## 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 the accepted target viewports; route a systematic breakpoint problem to `responsive-visual-polish-qa`.
4. Inspect hero, navigation, major sections, interactive states, forms, media, and footer.
5. Fix obvious visual defects and weak polish.
6. Run relevant required checks; repeat or broaden only after changes, failures or an unresolved risk.