t3-env / rules

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

20 rules. About 0 are common, 16 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈16

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Follow the user's requirements carefully & to the letter.

   line 11
2. Distinctive:

   Write straightforward, readable, and maintainable code.

   line 24
3. Distinctive:

   Use strong typing, avoid 'any'.

   line 25
4. Distinctive:

   Do not use any third party library.

   line 27
5. Very specific:

   Create clearly documented changesets for your introduced changes using bun changeset.

   line 29
6. Distinctive:

   Use descriptive names: verbs & nouns (e.g., getUserData)

   line 41
7. Very specific:

   Prefer the function keyword over arrow functions where their differences doesn't matter.

   line 42
8. Distinctive:

   Document with JSDoc annotations

   line 43
9. Distinctive:

   Prefer custom interfaces over inline types

   line 47
10. Distinctive:

    Use 'readonly' for immutable properties

    line 48
11. Distinctive:

    If an import is only used as a type in the file, use 'import type' instead of 'import'

    line 49
12. Very specific:

    Always validate your changes confirm to the project lint configuration by running bun run lint.

    line 53
13. Very specific:

    Write tests for changes and validate they pass using bun run test.

    line 54
14. Distinctive:

    Check for code duplication

    line 59
15. Distinctive:

    Use the active voice

    line 67
16. Distinctive:

    Use the present tense

    line 68
17. Distinctive:

    Write in a clear and concise manner

    line 69
18. Distinctive:

    Use lists and tables when appropriate

    line 71
19. Distinctive:

    When writing JSDocs, only use TypeDoc compatible tags.

    line 72
20. Distinctive:

    Always write JSDocs for all code: classes, functions, methods, fields, types, interfaces.

    line 73

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