We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈1

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run before commit or merge-ready sign-off.

   line 14
2. Very specific:

   Use npm ci (not npm install) when lockfile must match — CI and releases.

   line 22
3. Very specific:

   After package.json deps: npm install once → commit lockfile → verify npm ci

   line 40
4. Very specific:

   After src/ / tests/ edits: full npm run ci — not lint-only

   line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

• In this repository15 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • .cursor/rules/pre-commit-quality-gate.mdcCursor rule
  • .cursor/rules/release-versioning.mdcCursor rule
  • .cursor/rules/zeroagent-advisor.mdcCursor rule
  • .cursor/rules/zeroagent-debugger.mdcCursor rule
  • .cursor/rules/zeroagent-engineer.mdcCursor rule
  • .cursor/rules/zeroagent-planner.mdcCursor rule
  • .cursor/rules/zeroagent-reviewer.mdcCursor rule
  • .cursor/rules/zeroagent-security-auditor.mdcCursor rule
  • .cursor/rules/zeroagent-test-engineer.mdcCursor rule
  • add-brain-providerSkill
  • add-browser-toolSkill
  • release-versioningSkill
  • review-before-mergeSkill
  • ship-patchSkill