wizards-choice — Cursor Rules

• "Use '/docs' as the Knowledge Base": Always refer to '/docs' to understand the context of the project. Do not code anything outside of the context provided in the '/docs' folder. This folder serves as the knowledge base and contains the fundamental rules and guidelines that should always be followed. If something is unclear, check this folder before proceeding with any coding. • "Verify Information": Always verify information from the context before presenting it. Do not make assumptions or speculate without clear evidence. • "For Feature Development": When implementing a new feature, develop a step by step concise TODO task list using the 'todo.md' in project root, strictly follow the steps outlined in 'todo.md'. Every step is listed in sequence, and each must be completed in order. After completing each step, update 'CHANGELOG.md' with the word "Done" and a two-line summary of what steps were taken. This ensures a clear work log, helping maintain transparency and tracking progress effectively. • "File-by-File Changes": Make all changes file by file and give the user the chance to spot mistakes. • "No Apologies": Never use apologies. • "No Understanding Feedback": Avoid giving feedback about understanding in the comments or documentation. • "No Whitespace Suggestions": Don't suggest whitespace changes. • "No Summaries": Do not provide unnecessary summaries of changes made. Only summarize if the user explicitly asks for a brief overview after changes. • "No Inventions": Don't invent changes other than what's explicitly requested. • "No Unnecessary Confirmations": Don't ask for confirmation of information already provided in the context. • "Preserve Existing Code": Don't remove unrelated code or functionalities. Pay attention to preserving existing structures. • "Single Chunk Edits": Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file. • "No Implementation Checks": Don't ask the user to verify implementations that are visible in the provided context. However, if a change affects functionality, provide an automated check or test instead of asking for manual verification. • "No Unnecessary Updates": Don't suggest updates or changes to files when there are no actual modifications needed. • "Provide Real File Links": Always provide links to the real files, not the context-generated file. • "No Current Implementation": Don't discuss the current implementation unless the user asks for it or it is necessary to explain the impact of a requested change. • "Check Context Generated File Content": Remember to check the context-generated file for the current file contents and implementations. • "Use Explicit Variable Names": Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability. • "Follow Consistent Coding Style": Adhere to the existing coding style in the project for consistency. • "Prioritize Performance": When suggesting changes, consider and prioritize code performance where applicable. • "Security-First Approach": Always consider security implications when modifying or suggesting code changes. • "Test Coverage": Suggest or include appropriate unit tests for new or modified code. • "Error Handling": Implement robust error handling and logging where necessary. • "Modular Design": Encourage modular design principles to improve code maintainability and reusability. • "Version Compatibility": When suggesting changes, ensure they are compatible with the project's specific language or framework versions. If a version conflict arises, suggest an alternative. • "Avoid Magic Numbers": Replace hard-coded values with named constants to improve code clarity and maintainability. • "Consider Edge Cases": When implementing logic, always consider and handle potential edge cases. • "Use Assertions": Include assertions wherever possible to validate assumptions and catch potential errors early. • "Testing": I have npm run dev running in the terminal so i can test changes live, so i do not need you to ask to run the server to test changes. I will do that task myself after changes are made and compiled in the dev server. • "No Lazy Solutions": Don't just ignore the problem and supersede it, or take shortcuts because that leaves unused wrong code bloating the codebase complicating further development. Do not create fresh css files to override css errors, find and fix the problem instead. • "Debloating IS Best": Always remove bloat code when you can refactor away unused code or optimize it to be less bloated and inefficient/confusing or messy. • "Diagram Processes": Always use mermaid diagrams to illustrate processes and workflows in the codebase when updating relevant docs. Keep docs/process_maps.md up to date with each user verified completed task.