vibe-tools / rules

We split this good-behaviour.mdc into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 0

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Do not hard code data into code unless specifically requested by me.

   line 6
2. Distinctive:

   If you have an idea on why something is failing, always validate that idea with testing before changing code.

   line 8
3. Distinctive:

   Do not write stub or fake methods.

   line 10
4. Distinctive:

   Do not cheat on tests and checks by adding hard-coded values or assertions.

   line 12
5. Distinctive:

   Do not make statements about functionality working unless you have tested it.

   line 14

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

• Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

  Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

• In this repository8 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • .cursor/rules/changelog.mdcCursor rule
  • .cursor/rules/git-commit.mdcCursor rule
  • .cursor/rules/repo.mdcCursor rule
  • .cursor/rules/testing.mdcCursor rule
  • .cursor/rules/vibe-tools.mdcCursor rule
  • .cursor/rules/yo.mdcCursor rule