Skip to content

TheGoat395/Codex-Skills / skills/browser-inspection-workflow

browser-inspection-workflow

Verified

Coordinate rendered behavior and state evidence.

FileKindSize
SKILL.mdskill md1.7 KB
agents/openai.yamlconfig251 B
references/browser-inspection-workflow-guide.mdmarkdown2.3 KB

references/browser-inspection-workflow-guide.md

View on GitHub
# Browser Inspection Workflow Guide

## Purpose

- Make rendered-browser inspection a default part of shipping frontend work.

## Discovery Questions

- What URL or local server should be inspected?
- Which pages, modals, menus, forms, media, and interactions are critical?
- What browser/device sizes matter?
- Which errors are known versus new?

## Implementation Rules

- Inspect rendered output after substantial UI changes.
- Check console and failed requests.
- Test links/buttons/forms, not just static appearance.
- Use screenshots for visual claims.
- Warm lazy and reveal-heavy pages by scrolling through them before final captures.
- Reject native full-page screenshots that disagree with settled viewport behavior; use the stitched workflow in `$visual-regression-lab`.
- Report what was not inspectable.

## Useful Patterns

- Local dev server plus Playwright/Chrome inspection.
- Desktop and mobile smoke path through homepage, nav, CTA, form.
- Console/network capture before final answer.
- Screenshot proof for hero, mid-page, and mobile menu.
- Settled viewport stitching for Framer, WebGL, lazy media, pinned scenes, or scroll-reveal pages when one-shot full-page capture fails.

## Anti-Patterns

- Final says polished without opening the site.
- Console errors ignored.
- Only source code reviewed.
- Mobile nav or form never clicked.

## QA Checklist

- Open page, wait for assets, inspect console/network.
- Interact with nav, CTAs, forms, and media.
- Capture screenshots at key viewports.
- Fix or report visible defects.

## Acceptance Criteria

- Rendered browser behavior matches the intended design.
- Console/network issues are fixed or documented.
- The final report reflects actual inspection.

## Scoped execution

Apply the [shared web contract](../../website-operating-rules/references/scoped-web-contract.md) once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

## Official Source Anchors

- Playwright screenshots: https://playwright.dev/docs/screenshots
- Playwright visual comparisons: https://playwright.dev/docs/test-snapshots
- Playwright emulation: https://playwright.dev/docs/emulation
- web.dev Web Vitals: https://web.dev/articles/vitals
- MDN Performance API: https://developer.mozilla.org/en-US/docs/Web/API/Performance_API
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall