We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  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:

   Use this skill when a repo in the workspace fails to install, start, preview, or report health correctly.

   line 8
2. Very specific:

   Check .workspace/project.json for explicit overrides before changing inference logic.

   line 14
3. Distinctive:

   Verify runtime commands directly in the repo only after reading the tracked metadata and logs.

   line 15
4. Distinctive:

   Do not hard-code one package manager across all repos.

   line 26
5. Distinctive:

   Do not switch a repo into a proxy or mapped-host preview mode unless it solves a real problem.

   line 27

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