agentleFS
Sign inStart free
amitray007amitray007/headroom/.agents/skills/verify-web/SKILL.md

verify-web

Skill83 starsChanged 11 days agoMITView on GitHub

See a Headroom web change on screen with synthetic data before calling it done. Use after changing `apps/web/src`, to capture before and after screenshots for a pull request, or to check a view at phone width, in dark mode or for page errors.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. joi-fairshare/agentic-workflow★ 3same name
    2. jthorare/agentic-workflow★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Wait for content before any capture: wait --fn "document.body.innerText.length > 200".

    line 22
  2. Very specific:

    Check the changed view at 1280 x 800 and 390 x 844, in light and dark, with a short wait 800 after each set media so transitions settle.

    line 23
  3. Distinctive:

    Look at every screenshot yourself.

    line 24
  4. Distinctive:

    No new page error or console error.

    line 32
  5. Very specific:

    Use mise exec -- bun run web:dev against a dev server (mise run dev) only when the change depends on server behaviour that Demo Mode does …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Verify the web app

Tests prove the logic; this proves what the owner will see. Use the static demo build: it answers /api/ inside the page with Demo Mode data, so it needs no server, no sign-in and no real account.

Steps

  1. Build: mise run demo:build writes apps/web/dist-demo.

  2. Serve it with Vite on a free port, in the background, and record the PID:

    cd apps/web && mise exec -- bun x vite preview --outDir dist-demo --port 4399 --strictPort --host 127.0.0.1

    Serve with Vite only. Python's http.server drops some of the parallel module requests, and the page stays blank with no error.

  3. Open it with the browser skill (agent-browser, one named session). Routes are hash routes: #/, #/detailed, #/compare, #/timeline, #/wallet, #/analytics.
  4. Wait for content before any capture: wait --fn "document.body.innerText.length > 200". A capture taken earlier is an empty page.
  5. Check the changed view at 1280 x 800 and 390 x 844, in light and dark, with a short wait 800 after each set media so transitions settle. Read errors --json and console; both must be empty of new entries.
  6. Look at every screenshot yourself. A saved file is not a check.
  7. Close the session and stop the server; confirm the port is free.

For before and after captures, run steps 1 to 6 once in a temporary worktree at the pull request's base (git merge-base HEAD origin/<base branch>) and once on the branch, at the same widths, themes and route, then follow the PR showcase skill.

Done when

  • The changed view renders with demo data at both widths and both themes, and you looked at each capture.
  • No new page error or console error.
  • The browser session is closed and the server is stopped.

Use mise exec -- bun run web:dev against a dev server (mise run dev) only when the change depends on server behaviour that Demo Mode does not imitate. The Mac app is out of scope: the owner tests it.

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.

Check your setup, free