who-to-bother-at-on-x / rules

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

47 rules. About 0 are common, 25 are distinctive, and 22 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈25

  Distinctive · estimate

  This author's own choices. Worth a look.

• 22

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Write code that is accessible, performant, type-safe, and maintainable.

   line 23
2. Distinctive:

   Use explicit types for function parameters and return values when they enhance clarity

   line 27
3. Very specific:

   Prefer unknown over any when the type is genuinely unknown

   line 28
4. Very specific:

   Use const assertions (as const) for immutable values and literal types

   line 29
5. Distinctive:

   Use meaningful variable names instead of magic numbers - extract constants with descriptive names

   line 31
6. Distinctive:

   Use arrow functions for callbacks and short functions

   line 35
7. Very specific:

   Prefer for...of loops over .forEach() and indexed for loops

   line 36
8. Very specific:

   Use optional chaining (?.) and nullish coalescing (??) for safer property access

   line 37
9. Distinctive:

   Prefer template literals over string concatenation

   line 38
10. Distinctive:

    Use destructuring for object and array assignments

    line 39
11. Very specific:

    Use const by default, let only when reassignment is needed, never var

    line 40
12. Very specific:

    Always await promises in async functions - don't forget to use the return value

    line 44
13. Very specific:

    Use async/await syntax instead of promise chains for better readability

    line 45
14. Distinctive:

    Don't use async functions as Promise executors

    line 47
15. Distinctive:

    Use function components over class components

    line 51
16. Distinctive:

    Call hooks at the top level only, never conditionally

    line 52
17. Very specific:

    Use the key prop for elements in iterables (prefer unique IDs over array indices)

    line 54
18. Distinctive:

    Don't define components inside other components

    line 56
19. Distinctive:

    Use semantic HTML and ARIA attributes for accessibility:

    line 57
20. Distinctive:

    Use proper heading hierarchy

    line 59
21. Distinctive:

    Add labels for form inputs

    line 60
22. Very specific:

    Use semantic elements (<button>, <nav>, etc.) instead of divs with roles

    line 62
23. Very specific:

    Remove console.log, debugger, and alert statements from production code

    line 66
24. Very specific:

    Use try-catch blocks meaningfully - don't catch errors just to rethrow them

    line 68
25. Distinctive:

    Prefer early returns over nested conditionals for error cases

    line 69
26. Distinctive:

    Keep functions focused and under reasonable cognitive complexity limits

    line 73
27. Distinctive:

    Use early returns to reduce nesting

    line 75
28. Distinctive:

    Prefer simple conditionals over nested ternary operators

    line 76
29. Very specific:

    Add rel="noopener" when using target="_blank" on links

    line 81
30. Very specific:

    Avoid dangerouslySetInnerHTML unless absolutely necessary

    line 82
31. Very specific:

    Don't use eval() or assign directly to document.cookie

    line 83
32. Distinctive:

    Avoid spread syntax in accumulators within loops

    line 88
33. Distinctive:

    Use top-level regex literals instead of creating them in loops

    line 89
34. Distinctive:

    Prefer specific imports over namespace imports

    line 90
35. Distinctive:

    Avoid barrel files (index files that re-export everything)

    line 91
36. Very specific:

    Use proper image components (e.g., Next.js <Image>) over <img> tags

    line 92
37. Very specific:

    Use Next.js <Image> component for images

    line 97
38. Very specific:

    Use next/head or App Router metadata API for head elements

    line 98
39. Distinctive:

    Use Server Components for async data fetching instead of async Client Components

    line 99
40. Very specific:

    Use ref as a prop instead of React.forwardRef

    line 102
41. Very specific:

    Use class and for attributes (not className or htmlFor)

    line 105
42. Very specific:

    Write assertions inside it() or test() blocks

    line 111
43. Distinctive:

    Avoid done callbacks in async tests - use async/await instead

    line 112
44. Very specific:

    Don't use .only or .skip in committed code

    line 113
45. Very specific:

    Keep test suites reasonably flat - avoid excessive describe nesting

    line 114
46. Distinctive:

    Meaningful naming: - Use descriptive names for functions, variables, and types

    line 121
47. Distinctive:

    Documentation: - Add comments for complex logic, but prefer self-documenting code

    line 125

≈ “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 versions10 projects use a version of this.

  Word for word · 10

  1. vercel/streamdown★ 5.7k100% same
  2. TheOrcDev/8bitcn-ui★ 2.1k100% same
  3. vercel-labs/workflow-builder-template★ 1.2k100% same
  4. ChatbotXIO/ChatbotX★ 1.1k100% same
  5. TheOrcDev/better-auth-starter★ 354100% same
  6. vercel-labs/npm.bet★ 66100% same
  7. KeeperHub/keeperhub★ 25100% same
  8. kuluruvineeth/openbeam★ 19100% same
  9. vercel/workflow-builder-starter★ 8100% same
  10. vercel/academy-starters★ 0100% 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 repository3 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • .claude/CLAUDE.mdCLAUDE.md
  • .github/copilot-instructions.mdCopilot instructions