GenerativeSeoKitBundle / rules

We split this 40-tests-quality.mdc into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are 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.

• 0

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   When changing behavior, prefer adding or updating the nearest relevant test.

   line 17
2. Distinctive:

   test updates close to the changed behavior

   line 23
3. Distinctive:

   Do not introduce new testing frameworks unless explicitly requested.

   line 25
4. Distinctive:

   Do not rewrite unrelated tests.

   line 26

≈ “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 repository15 other files it gives its agents.

  • .github/copilot-instructions.mdCopilot instructions
  • .cursor/rules/00-global.mdcCursor rule
  • .cursor/rules/01-git-commits.mdcCursor rule
  • .cursor/rules/10-php-symfony-bundle.mdcCursor rule
  • .cursor/rules/50-docs-and-release.mdcCursor rule
  • speckit-analyzeSkill
  • speckit-checklistSkill
  • speckit-clarifySkill
  • speckit-constitutionSkill
  • speckit-convergeSkill
  • speckit-implementSkill
  • speckit-planSkill
  • speckit-specifySkill
  • speckit-tasksSkill
  • speckit-taskstoissuesSkill