Skip to content

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

browser-inspection-workflow

Verified

Coordinate rendered behavior and state evidence.

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 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.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

Scope and evidence

Coordinate one route/viewport/state evidence matrix shared by QA specialists. Reuse current evidence; recheck affected coverage after relevant changes. Captures require actual visual inspection before quality claims.

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