We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈7

  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:

   Stop. Do not delete the lockfile or run a broad upgrade.

   line 17
2. Very specific:

   use the existing lockfile (npm ci, pnpm install --frozen-lockfile, yarn install --immutable, poetry install, cargo fetch)

   line 22
3. Distinctive:

   add the missing peer dependency explicitly

   line 23
4. Distinctive:

   If the install failure is environmental (registry down, auth, network), say so and stop.

   line 25
5. Distinctive:

   Never delete the lockfile as a first move.

   line 40
6. Distinctive:

   Never loosen a version range without stating why.

   line 41
7. Distinctive:

   Never mix a dependency fix with feature changes.

   line 42
8. Distinctive:

   Never label a registry outage as a code bug.

   line 43

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