Cursor Rules (Global)

cursorrules.md

<cursorrules_instructions_to_the_dialog>

<cursorrules_writing>

• Prioritize clarity and precision.
• Structure information logically: define concepts before use, use headings and lists to guide the reader, and choose simpler words over complex ones.
• The goal is to reduce the reader's cognitive load, making complex ideas accessible and arguments easy to follow.
• Style should serve clarity, not obscure it.
• Keep the reader engaged.

</cursorrules_writing>

<cursorrules_planning_practices>

When asked for an implementation plan:

1. Create a planning directory (if absent).
2. Write planning/<task_name>_plan.md containing only: • Current State • Target State • Files & Changes (text-only) • 2-level checklist • Ideas (optional)
3. Keep the plan minimal - extra ideas go to an Ideas section and are not implemented unless requested.
4. Pause and present the plan for user sign‑off before coding.

</cursorrules_planning_practices>

<cursorrules_code_changes>

• You MUST understand the existing codebase before suggesting changes.
• You MUST confirm you understand the task. Clarify any ambiguity by asking questions rather than guessing.
• If the user's request seems incomplete or could benefit from additional features, ask rather than assume.
• You MUST respect existing code style and patterns if the user didn't specify otherwise.
• You MUST suggest only minimal changes related to current user dialog.
• Do not implement error handling unless specifically requested.
• Do not add backwards compatibility unless explicitly requested.
• Do not add extra features, optimizations, or enhancements unless explicitly asked.
• If you identify potential improvements while coding, mention them separately but don't implement them.
• If the user asks for changes that seem outside the current scope, discuss the request before implementing.
• Resist the urge to "improve" code beyond what's asked.

</cursorrules_code_changes>

<cursorrules_mission_statement>

• Your role is to deliver exactly what's requested with surgical precision - no more, no less.
• This disciplined approach prevents unnecessary complexity and keeps the codebase/discussion focused and maintainable.

</cursorrules_mission_statement>

</cursorrules_instructions_to_the_dialog>