invoicely / rules

We split this nextjs-cursor-rule.mdc into the rules it gives an agent

20 rules. About 0 are common, 18 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈18

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Write concise, technical TypeScript code with accurate examples.

   line 9
2. Distinctive:

   Use functional and declarative programming patterns.

   line 10
3. Distinctive:

   Prefer iteration and modularization over code duplication.

   line 11
4. Distinctive:

   Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).

   line 12
5. Distinctive:

   Follow seprate export const component name like don't "export const Button = () => {}" make it do like "const Button = () => {} export { …

   line 14
6. Distinctive:

   Don't use default exports.

   line 15
7. Very specific:

   use name.client.tsx for file having "use client" or its a client component so add (.client.tsx) in end of file name.

   line 18
8. Distinctive:

   Use lowercase with dashes for directories (e.g., components/auth-wizard).

   line 19
9. Distinctive:

   Use TypeScript for all code.

   line 24
10. Distinctive:

    Avoid enums; use maps instead.

    line 25
11. Distinctive:

    Use functional components with TypeScript interfaces.

    line 26
12. Distinctive:

    Use the "function" keyword for pure functions.

    line 29
13. Distinctive:

    Avoid unnecessary curly braces in conditionals.

    line 30
14. Distinctive:

    Use Shadcn UI, Radix, and Tailwind for components and styling.

    line 34
15. Distinctive:

    Use dynamic loading for non-critical components.

    line 40
16. Distinctive:

    Use 'nuqs' for URL search parameter state management.

    line 44
17. Distinctive:

    Use only for Web API access in small components.

    line 48
18. Distinctive:

    Avoid for data fetching or state management.

    line 49
19. Distinctive:

    use <type>(required scope any related to commit file): single title for commit without description

    line 52
20. Very specific:

    Follow Next.js docs for Data Fetching, Rendering, and Routing.

    line 55

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

  • .agents/skills/composition-patterns/AGENTS.mdAGENTS.md
  • .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
  • .agents/skills/react-hook-form/AGENTS.mdAGENTS.md
  • .agents/skills/zod/AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • accessibilitySkill
  • bash-defensive-patternsSkill
  • better-auth-best-practicesSkill
  • vercel-composition-patternsSkill
  • drizzle-ormSkill
  • email-and-password-best-practicesSkill
  • frontend-designSkill
  • neon-postgresSkill
  • next-best-practicesSkill
  • next-cache-componentsSkill
  • next-upgradeSkill
  • nodejs-backend-patternsSkill
  • nodejs-best-practicesSkill
  • organization-best-practicesSkill
  • vercel-react-best-practicesSkill
  • react-hook-formSkill
  • seoSkill
  • shadcnSkill
  • tailwind-css-patternsSkill
  • tailwind-v4-shadcnSkill
  • turborepoSkill
  • two-factor-authentication-best-practicesSkill
  • typescript-advanced-typesSkill
  • ai-sdkSkill
  • zodSkill