pro-components / rules

We split this codequality.mdc into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈11

  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:

   Always verify information before presenting it.

   line 9
2. Distinctive:

   Avoid giving feedback about understanding in comments or documentation.

   line 18
3. Distinctive:

   Don't suggest whitespace changes.

   line 21
4. Distinctive:

   Don't summarize changes made.

   line 24
5. Distinctive:

   Don't invent changes other than what's explicitly requested.

   line 27
6. Distinctive:

   Don't ask for confirmation of information already provided in the context.

   line 30
7. Distinctive:

   Don't remove unrelated code or functionalities.

   line 33
8. Distinctive:

   Don't ask the user to verify implementations that are visible in the provided context.

   line 39
9. Distinctive:

   Don't suggest updates or changes to files when there are no actual modifications needed.

   line 42
10. Distinctive:

    Always provide links to the real files, not x.md.

    line 45
11. Distinctive:

    Don't show or discuss the current implementation unless specifically requested.

    line 48

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

• Other versions2 projects use a version of this.

  Word for word · 2

  1. ant-design/agentic-ui★ 233100% same
  2. antdigital-ai/agentic-ui★ 233100% same

  Edited · 0

  None found.

  Wrote their own version · 0

  None found.

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• 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 repository4 other files it gives its agents.

  • .cursor/rules/AGENTS.mdAGENTS.md
  • .cursor/rules/clean-code.mdcCursor rule
  • .cursor/rules/react.mdcCursor rule
  • .cursor/rules/test.mdcCursor rule