ui-change-e2e
Skill0 starsChanged 2 months agoMITView on GitHub
Require E2E tests when creating, changing, or fixing UI. Add a failing test for bugs, mock API writes, run project test:e2e before done. Use for web UI bug reports, new screens, or route changes.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/automate-before-manual.mdcCursor rule
- .cursor/rules/finish-task-dev-server.mdcCursor rule
- brainstormingSkill
- caveman-commitSkill
- find-skillsSkill
- semantic-versionSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- writing-plansSkill
- ask-before-architectureSkill
- automate-before-manualSkill
- caveman-commitSkill
- diagrams-mermaidSkill
- dont-be-lazySkill
- dont-forgetSkill
- find-jobSkill
- finish-with-dev-serverSkill
- google-calendar-mcpSkill
- init-fmzSkill
- instagram-chrome-postSkill
- project-initSkill
- recapSkill
- semantic-versionSkill
- skills-sh-maintainerSkill
- validate-before-shareSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Prefer data-testid or stable roles over fragile CSS classes.
- Very specific: line 19
Run the project's E2E command before closing (npm run test:e2e, pnpm test:e2e, etc.).
- Distinctive: line 23
Check if a spec exists for that area.
- Distinctive: line 24
Add a test case that reproduces the bug (or extend existing spec).
- Distinctive: line 26
Do not mark the bug fixed without a regression test.
- Very specific: line 35
Run full E2E or at least the affected spec (playwright test path/to/spec.ts).
- Distinctive: line 40
No frontend, no Playwright/Cypress setup, or user explicitly scoped a docs-only change.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 change — E2E required
Applies when the project has a frontend E2E setup (e2e/, playwright.config.*, or path in AGENTS.md).
New or changed screen
- Find or create spec under the project's E2E folder.
- Cover the new or changed behavior.
- Prefer
data-testidor stable roles over fragile CSS classes. - Run the project's E2E command before closing (
npm run test:e2e,pnpm test:e2e, etc.).
Bug fix
- Check if a spec exists for that area.
- Add a test case that reproduces the bug (or extend existing spec).
- Order: failing test → fix → green E2E.
- Do not mark the bug fixed without a regression test.
API writes in E2E
- Mock POST/PATCH/DELETE via
page.route(or projectfixtures/mock-api.ts) unless the project'sAGENTS.mddocuments a safe real-write exception. - Real DB/integration tests belong in
backend/tests/or documented E2E seed users — not production data.
Before done
- Run full E2E or at least the affected spec (
playwright test path/to/spec.ts). - Fix failures — do not report complete with red E2E.
Skip
No frontend, no Playwright/Cypress setup, or user explicitly scoped a docs-only change.
See project AGENTS.md for spec paths, auth helpers, and coverage tables.
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.

