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

1. Distinctive:

   Run the repo's end-to-end test entrypoint and summarize the outcome tersely.

   line 8
2. Distinctive:

   Use a generous timeout because this script builds the app, installs E2E dependencies, installs Playwright browsers if needed, and then runs …

   line 14
3. Very specific:

   If everything passes, reply with one line: ✅ E2E: all passed (N tests, XXs)

   line 18
4. Distinctive:

   If the build step fails, stop there and return:

   line 19
5. Distinctive:

   If tests run and some fail, return:

   line 22
6. Distinctive:

   only 3-5 relevant log lines per failure

   line 27
7. Distinctive:

   Do not include the full Playwright progress log.

   line 28
8. Distinctive:

   Do not rerun failing tests unless explicitly asked.

   line 29
9. Distinctive:

   Do not speculate about the cause beyond what the captured output shows.

   line 30
10. Distinctive:

    Treat environment/setup failures separately from test failures.

    line 34

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