agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/browser-inspection-workflow/SKILL.md

browser-inspection-workflow

Skill136 starsChanged 5 months agoMITView on GitHub

Coordinate rendered behavior and state evidence.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to make rendered-browser inspection a default part of shipping frontend work.

    line 8
  2. Distinctive:

    Read Browser Inspection Workflow Guide before claiming the site is ready.

    line 13
  3. Distinctive:

    Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or …

    line 14
  4. Distinctive:

    After fixes, recheck affected rendered states.

    line 16
  5. Very specific:

    If a native fullPage screenshot is blank, sparse, missing lower content, frozen before reveal animation, or inconsistent with the working …

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.