Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6---
7description: Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
8globs: 
9---
10 
11## Constants Over Magic Numbers
12- Replace hard-coded values with named constants
13- Use descriptive constant names that explain the value's purpose
14- Keep constants at the top of the file or in a dedicated constants file
15 
16## Meaningful Names
17- Variables, functions, and classes should reveal their purpose
18- Names should explain why something exists and how it's used
19- Avoid abbreviations unless they're universally understood
20 
21## Smart Comments
22- Don't comment on what the code does - make the code self-documenting
23- Use comments to explain why something is done a certain way
24- Document APIs, complex algorithms, and non-obvious side effects
25 
26## Single Responsibility
27- Each function should do exactly one thing
28- Functions should be small and focused
29- If a function needs a comment to explain what it does, it should be split
30 
31## DRY (Don't Repeat Yourself)
32- Extract repeated code into reusable functions
33- Share common logic through proper abstraction
34- Maintain single sources of truth
35 
36## Clean Structure
37- Keep related code together
38- Organize code in a logical hierarchy
39- Use consistent file and folder naming conventions
40 
41## Encapsulation
42- Hide implementation details
43- Expose clear interfaces
44- Move nested conditionals into well-named functions
45 
46## Code Quality Maintenance
47- Refactor continuously
48- Fix technical debt early
49- Leave code cleaner than you found it
50 
51## Verify Information
52Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
53 
54## File-by-File Changes
55Make changes file by file and give me a chance to spot mistakes.
56 
57## No Apologies
58Never use apologies.
59 
60## No Understanding Feedback
61Avoid giving feedback about understanding in comments or documentation.
62 
63## No Whitespace Suggestions
64Don't suggest whitespace changes.
65 
66## No Summaries
67Don't summarize changes made.
68 
69## No Inventions
70Don't invent changes other than what's explicitly requested.
71 
72## No Unnecessary Confirmations
73Don't ask for confirmation of information already provided in the context.
74 
75## Preserve Existing Code
76Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
77 
78## Single Chunk Edits
79Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
80 
81## No Implementation Checks
82Don't ask the user to verify implementations that are visible in the provided context.
83 
84## No Unnecessary Updates
85Don't suggest updates or changes to files when there are no actual modifications needed.
86 
87## Provide Real File Links
88Always provide links to the real files, not x.md.
89 
90## No Current Implementation
91Don't show or discuss the current implementation unless specifically requested.