Individual skill
browser-inspection-workflow
Coordinate rendered behavior and state evidence.
skills/browser-inspection-workflow/SKILL.md
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
- operations 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 · 1,741 bytesagents/openai.yamlasset · 251 bytesreferences/browser-inspection-workflow-guide.mddoc · 2,367 bytes
Read excerpt
# Browser Inspection Workflow
Use this skill to make rendered-browser inspection a default part of shipping frontend work.
## Workflow
1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
2. Read [Browser Inspection Workflow Guide](references/browser-inspection-workflow-guide.md) before claiming the site is ready.
3. Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
5. After fixes, recheck affected rendered states; repeat broader polish only for an observed defect or unresolved quality risk.
6. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
If a native `fullPage` screenshot is blank, sparse, missing lower content, frozen before reveal animation, or inconsistent with the working scroll experience, do not use it as visual proof. Route the capture through `$visual-regression-lab` and its stitched viewport workflow.