We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈3

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Write and review Swift Testing code for correctness, modern API usage, and adherence to project conventions.

   line 14
2. Distinctive:

   Do not rewrite existing XCTest to Swift Testing unless requested.

   line 20
3. Very specific:

   Ensure tests follow core conventions using references/core-rules.md.

   line 24
4. Very specific:

   Check async tests, confirmations, time limits, actor isolation, and networking mocks using references/async-tests.md.

   line 26
5. Very specific:

   Ensure new features like raw identifiers, exit tests, and attachments are used correctly using references/new-features.md.

   line 27
6. Very specific:

   If migrating from XCTest, follow references/migrating-from-xctest.md.

   line 28
7. Distinctive:

   If doing partial work, load only the relevant reference files.

   line 30

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