ui-validation
Skill0 starsChanged 2 months agoMITView on GitHub
Validate user-facing web changes by running the real application, exercising affected journeys, inspecting browser failures and rendered states, and recording exact evidence.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vikisingh23/neuraforge-aitheir own version, first seen May 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vikisingh23/neuraforge-ai★ 4same 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- independent-reviewSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-nextjsSkill
- stack-phoenix-liveviewSkill
- stack-rustSkill
- stack-svelteSkill
- systematic-debuggingSkill
- technical-writingSkill
- unslopSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
- Distinctive: line 8
Never report that a UI is validated merely because it compiled or unit tests passed.
- Distinctive: line 12
Read the applicable AGENTS.md.
- Distinctive: line 16
Start only the services required by the affected journey.
- Distinctive: line 17
Wait for an explicit readiness/health condition rather than guessing from elapsed time.
- Distinctive: line 21
When the current ChatGPT/Codex surface provides Browser access, open the running application there.
- Distinctive: line 31
Do not approve clipped, overlapping, unreachable, or horizontally overflowing UI.
- Distinctive: line 35
Run the repository's existing E2E/browser tests.
- Very specific: line 37
When the project already uses Playwright or equivalent tooling, retain useful screenshots/traces on failure and inspect console/network …
- Distinctive: line 41
When a defect is found:
- Distinctive: line 62
Never replace missing validation with "looks good".
≈ “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.
Files
UI validation
Never report that a UI is validated merely because it compiled or unit tests passed.
Prepare
- Read the applicable
AGENTS.md. - Determine the repository-native build, start, readiness, and browser-test commands.
- Record the exact candidate SHA.
- Build the application.
- Start only the services required by the affected journey.
- Wait for an explicit readiness/health condition rather than guessing from elapsed time.
Browser pass
When the current ChatGPT/Codex surface provides Browser access, open the running application there. Otherwise use the project's existing browser automation or another supported local browser workflow.
Exercise the affected journey from a known starting state and inspect relevant:
- success, loading, empty, error, and recovery states;
- keyboard/focus behavior when interactive controls changed;
- browser console warnings/errors;
- failed or unexpected network requests;
- responsive layouts at project-defined breakpoints or representative narrow/desktop/wide states.
Do not approve clipped, overlapping, unreachable, or horizontally overflowing UI.
Automated pass
Run the repository's existing E2E/browser tests.
When the project already uses Playwright or equivalent tooling, retain useful screenshots/traces on failure and inspect console/network evidence. Do not add Node.js or a browser framework solely because this skill mentions them.
Fix loop
When a defect is found:
- record precise reproduction steps;
- return production-code fixes to the owning writer;
- validate the new exact SHA;
- rerun the failed checks;
- repeat until required checks pass or report the blocker.
Report
State:
- exact SHA;
- build/start/readiness commands;
- URLs and user journeys exercised;
- viewport/responsive states;
- automated test commands/results;
- console/network findings;
- screenshot/trace/evidence paths where produced;
- anything not tested.
Never replace missing validation with "looks good".
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.