agentleFS
farukzahrafarukzahra/agent-skills/skills/ui-change-e2e/SKILL.md

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.

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
  1. Very specific:

    Prefer data-testid or stable roles over fragile CSS classes.

    line 18
  2. Very specific:

    Run the project's E2E command before closing (npm run test:e2e, pnpm test:e2e, etc.).

    line 19
  3. Distinctive:

    Check if a spec exists for that area.

    line 23
  4. Distinctive:

    Add a test case that reproduces the bug (or extend existing spec).

    line 24
  5. Distinctive:

    Do not mark the bug fixed without a regression test.

    line 26
  6. Very specific:

    Run full E2E or at least the affected spec (playwright test path/to/spec.ts).

    line 35
  7. Distinctive:

    No frontend, no Playwright/Cypress setup, or user explicitly scoped a docs-only change.

    line 40

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Find or create spec under the project's E2E folder.
  2. Cover the new or changed behavior.
  3. Prefer data-testid or stable roles over fragile CSS classes.
  4. Run the project's E2E command before closing (npm run test:e2e, pnpm test:e2e, etc.).

Bug fix

  1. Check if a spec exists for that area.
  2. Add a test case that reproduces the bug (or extend existing spec).
  3. Order: failing test → fix → green E2E.
  4. Do not mark the bug fixed without a regression test.

API writes in E2E

  • Mock POST/PATCH/DELETE via page.route (or project fixtures/mock-api.ts) unless the project's AGENTS.md documents 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.

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.