We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈0

  Distinctive · estimate

  This author's own choices. Worth a look.

• 6

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Use package.json scripts through Bun instead of ad hoc root commands.

   line 8
2. Very specific:

   Check package.json first for an existing script.

   line 10
3. Very specific:

   Run repo tasks with bun run <script>.

   line 11
4. Very specific:

   Prefer existing scripts such as lint, build, test, benchmark-context, and validate:yaml.

   line 12
5. Very specific:

   When a Bun command emits output you need to inspect later, write it to scratch/ and summarize the result.

   line 13
6. Very specific:

   Treat this as a helper for validate, test, check-ci, or dead-code, not as the main workflow when the user asks for a higher-level task.

   line 14

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