Cursor Rule: General

1---
2description: General rules for all propmts
3globs: *
4alwaysApply: true
5---
6# General Development Rules
7 
8## Core Working Principles
9 
10Your responses will always be in the user's preferred language, while code and technical content will be written in English or the project's language.
11 
12Code and files will always be written in JavaScript, never TypeScript, unless the user explicitly requests it.
13 
14Always follow user requirements exactly as specified.
15 
16Think step by step: describe the plan in pseudocode or plain language before writing code.
17 
18Confirm your approach before writing code for complex or ambiguous tasks.
19 
20Code must be complete and production-ready, with no TODOs, placeholders, or missing pieces.
21 
22Use clear, descriptive names. Follow camelCase for variables and functions, PascalCase for components and classes.
23 
24Prioritize readable and maintainable code over premature optimization.
25 
26Minimize prose and explanations. Focus on delivering working code.
27 
28Name new files in kebab-case (user-profile.js, api-client.js).
29 
30Use `const` by default. Use `let` only when reassignment is necessary. Never use `var`.
31 
32User-facing content must be localized appropriately for the project's target audience.
33 
34## Best Practices
35 
36Apply DRY (Don't Repeat Yourself) principles. Extract repeated logic into reusable functions or components.
37 
38Minimize unnecessary variables. Calculate values inline when they're only used once.
39 
40Break large components into smaller, focused, reusable components.
41 
42Always anticipate execution errors and user errors (layer 8). Implement proper error handling and validation.
43 
44Incorporate security measures in both frontend and backend code.
45 
46If you don't know the answer to something, say so clearly. Don't guess or make assumptions.
47 
48## Package Management
49 
50Always use Bun as the preferred package manager for installing dependencies and running scripts.
51 
52Never use npm, pnpm, npx, yarn, or other package managers unless explicitly requested by the user or required by project constraints.
53 
54Examples:
55- `bun install <package>` instead of `npm install <package>`
56- `bun run dev` instead of `npm run dev`
57- `bunx <command>` instead of `npx <command>`
58 
59## Accessibility
60 
61Implement accessibility features in all user interfaces:
62- Use `tabindex` for keyboard navigation
63- Add `aria-label` and `aria-describedby` for screen readers
64- Implement `onKeyDown` handlers alongside `onClick` for interactive elements
65- Use semantic HTML elements
66- Ensure sufficient color contrast
67// … truncated