agentleFS
nrjdalalnrjdalal/inscope/.agents/skills/ui-verify/SKILL.md

ui-verify

Skill3 starsChanged 36 days agoMITView on GitHub

Verify a frontend or UI change in a real browser. Use after any change to web/next pages, components, or styles, before opening or updating a PR, or when an end-to-end flow needs checking.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Start the dev servers (dev skill).

    line 16
  2. Very specific:

    Responsive: check mobile, tablet, and desktop with agent-browser set viewport <w> <h>, and confirm no horizontal overflow: agent-browser …

    line 32

≈ “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

[!CAUTION] Synced from https://github.com/nrjdalal/zerostarter. Customize this skill or remove this note to stop syncing.

UI Verify

A green type-check and a clean lint prove the code compiles, not that the page renders. Drive it in a real browser before the PR.

1. Run the stack

Start the dev servers (dev skill). Under the default portless dev the base URLs are named and branch-prefixed, so resolve them once: WEB=$(bunx portless get inscope) and API=$(bunx portless get api.inscope) (or PORTLESS=0 bun run dev for the fixed http://localhost:3000 / http://localhost:4000). Done when $WEB/ returns 200 and $API/api/health responds ok.

2. Drive the affected route

Load the agent-browser skill, then open the route you changed and act on it:

agent-browser open "$WEB/<route>"
agent-browser snapshot   # read the page, then click/type/verify

Behind auth, sign in first with the Login (agents) button (shown once AGENT_SIGNIN_ENABLED=true) or the local sign-in (dev skill). For an end-to-end change, or whenever asked, drive the whole flow, not just the screen you touched. Done when you have watched the change render and behave, not merely that the route loaded.

3. Check it holds up

  • Visual: capture before and after at the same viewport (the 1782×972 default, agent-browser set viewport 1782 972; see the agent-browser skill). The "before" is the pre-change state: git stash (or check out the pre-change commit), agent-browser screenshot before.png, then restore your change and agent-browser screenshot after.png.
  • Responsive: check mobile, tablet, and desktop with agent-browser set viewport <w> <h>, and confirm no horizontal overflow: agent-browser eval 'document.documentElement.scrollWidth <= document.documentElement.clientWidth'.
  • Theme: toggle the app's theme control and check light and dark whenever the change touches either.

Done when Visual, Responsive, and Theme are each exercised (or consciously marked N/A) for the surfaces this change touches.

4. Attach evidence to the PR

Attach each screenshot with the GitHub CLI, which uploads it as an asset of the PR; never commit a binary screenshot.

gh pr comment <n> --body-file body.md \
  --attach './before.png#Before: what it shows' --attach './after.png#After: what it shows'

--attach takes <file>#<alt text>, repeats, and needs gh 2.100 or newer. A ![alt](./before.png) in the body is rewritten to the uploaded asset; files the body does not reference are appended. On an older gh, fall back to a temporary host and embed the URL it prints:

curl -sS -F "reqtype=fileupload" -F "time=72h" -F "fileToUpload=@screenshot.png" \
  https://litterbox.catbox.moe/resources/internals/api.php

Done when every screenshot (before+after pairs for a visual change) is on the PR.

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.