We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

• 0

  Common

  Most of the 8 edited versions we read keep these.

• 2

  Distinctive

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   When writing unit tests, follow these rules:

   line 8
2. Very specific:

   When writing unit tests for addons, always create a real xterm.js instance instead of mocking it.

   line 10
3. Very specific:

   Prefer assert.ok over assert.notStrictEqual when checking something is undefined or not.

   line 11
4. Distinctive:

   Avoid comments as most tests should be self-documenting.

   line 12

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.