care_fe / rules

We split this 02-coding-standards.mdc into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈17

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use TypeScript for all new code

   line 9
2. Distinctive:

   Prefer interfaces over types for object definitions

   line 10
3. Distinctive:

   Use functional components with proper type definitions

   line 11
4. Very specific:

   Avoid using any type; use proper type definitions

   line 12
5. Distinctive:

   Use type inference where possible

   line 13
6. Distinctive:

   Prefer default exports for components

   line 17
7. Very specific:

   Follow the component naming pattern: ComponentName.tsx

   line 18
8. Distinctive:

   Place components in appropriate feature directories

   line 19
9. Distinctive:

   Keep components small and focused

   line 20
10. Distinctive:

    Use Tailwind CSS for styling

    line 23
11. Distinctive:

    Follow mobile-first responsive design

    line 24
12. Distinctive:

    Use Shadcn UI components when available

    line 25
13. Distinctive:

    Use TanStack Query for API data management

    line 28
14. Distinctive:

    Prefer React Context for global state

    line 29
15. Distinctive:

    Use local state for component-specific data

    line 30
16. Very specific:

    Use kebab-case for directories: auth-wizard/

    line 33
17. Very specific:

    Use PascalCase for component files: AuthWizard.tsx

    line 34
18. Very specific:

    Use camelCase for utility files: useAuth.ts

    line 35
19. Distinctive:

    Write tests in Playwright for E2E testing

    line 38
20. Distinctive:

    Follow testing guidelines in https://playwright.dev/docs/writing-tests

    line 39
21. Distinctive:

    Test components in isolation

    line 40
22. Distinctive:

    Write meaningful test descriptions

    line 41

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

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • .github/copilot-instructions.mdCopilot instructions
  • .cursor/rules/01-project-structure.mdcCursor rule
  • .cursor/rules/03-data-fetching.mdcCursor rule
  • .cursor/rules/04-ui-components.mdcCursor rule