We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

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

   Check reliability: no hard sleeps.

   line 7
2. Distinctive:

   Check isolation: each test sets up and cleans up its own data.

   line 8
3. Distinctive:

   Check design: Page Object or Screenplay used sensibly, with no assertions buried in page objects unless that is a team convention.

   line 9
4. Distinctive:

   Check assertions: each test checks a meaningful outcome, not just "no exception".

   line 10
5. Distinctive:

   Check config and security: no hard-coded credentials or URLs (use env/config).

   line 11
6. Distinctive:

   Check CI fit: sharding/tags, retries limited and reported, artifacts uploaded.

   line 12

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