browser-verify
Skill1 starsChanged 41 days agoMITView on GitHub
Verify web UI in a real browser with repro steps. Use when validating frontends, fixing UI bugs, or running smoke/e2e checks.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- mahumadad/quarrytheir own version, first seen Nov 8, 2026
- LiriRaid/waymarktheir own version, first seen Oct 27, 2026
- AndyForest/SoupNettheir own version, first seen Oct 26, 2026
- feelthefusion/skill-starter-kittheir own version, first seen Oct 13, 2026
- chrisalehman/bionictheir own version, first seen Oct 13, 2026
- Mr-Quin/danmaku-anywheretheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- Mr-Quin/danmaku-anywhere★ 550same name
- AndyForest/SoupNet★ 11same name
- chrisalehman/bionic★ 9same name
- LiriRaid/waymark★ 2same name
- BlakeHastings/claude-code-artifacts★ 1same name
- Evan-Kim2028/agent-skills★ 1same name
- mahumadad/quarry★ 1same name
- feelthefusion/skill-starter-kit★ 0same name
- Koshux/agentic-sdlc-scaffold★ 0same 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 repository49 other files it gives its agents.
- accessibilitySkill
- address-feedbackSkill
- agent-disciplineSkill
- agent-handoffSkill
- api-designSkill
- architecture-decisionSkill
- brainstormSkill
- code-reviewSkill
- containerizeSkill
- context-efficientSkill
- create-prSkill
- database-changesSkill
- debug-systematicSkill
- dependency-upgradeSkill
- docs-groundedSkill
- error-handlingSkill
- explore-codebaseSkill
- fix-ciSkill
- frontend-designSkill
- git-commitSkill
- git-worktreeSkill
- incident-triageSkill
- incremental-slicesSkill
- legacy-changeSkill
- migrate-codeSkill
- minimal-diffSkill
- observabilitySkill
- parallel-workSkill
- performance-auditSkill
- plan-before-codeSkill
- python-qualitySkill
- react-componentsSkill
- refactor-safeSkill
- release-notesSkill
- security-reviewSkill
- setup-ciSkill
- shell-safetySkill
- ship-checklistSkill
- simplify-codeSkill
- skill-authoringSkill
- skill-routerSkill
- spec-drivenSkill
- tddSkill
- threat-modelSkill
- triage-issuesSkill
- typescript-strictSkill
- verify-workSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 10
Start or locate the local/dev URL and auth state needed.
- Distinctive: line 15
Add or update an automated e2e/smoke test when the path is critical and stable.
- Very specific: line 30
Prefer stable selectors (role/label/text) over brittle CSS chains.
- Distinctive: line 31
Do not rely on wall-clock sleeps.
- Distinctive: line 32
Keep e2e coverage thin; push detail to lower-level tests.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser Verify
Process
- Start or locate the local/dev URL and auth state needed.
- Define the user path to verify (entry → action → expected UI/state).
- Exercise the path in a real browser (Playwright/Cypress/DevTools/MCP browser tools as available).
- Capture evidence: console errors, network failures, screenshots when useful.
- Fix issues at the source; re-run the same path.
- Add or update an automated e2e/smoke test when the path is critical and stable.
Record
URL: ...
Steps:
1. ...
Expected: ...
Actual: ...
Console/network: ...Rules
- Prefer stable selectors (role/label/text) over brittle CSS chains.
- Do not rely on wall-clock sleeps; wait for conditions.
- Keep e2e coverage thin; push detail to lower-level tests.
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
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.