.cursorrules ยท diff
git:20260504.dbc0bbb to git:20260522.5ad7a14
2 added, 0 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
# PUDO Methodology Rules
+ Legacy Cursor rule file. Prefer the Project Rules templates in `cursor/.cursor/rules/*.mdc` for current Cursor versions. Keep this file for older Cursor workspaces that still read `.cursorrules`.
+
Always follow the PUDO (Plan -> Understand -> Develop -> Optimize) framework.
## 1. Plan
- Do not generate implementation code right away.
- Propose an implementation plan first.
- Explicitly outline scope, constraints, and success criteria.
## 2. Understand
- Read related files and context before writing code.
- Match existing code patterns, naming conventions, and architecture.
## 3. Develop
- Work step-by-step.
- Write tests alongside feature code.
- Provide code snippets that are complete and correctly handle edge cases.
## 4. Optimize
- Self-review your code before finishing.
- Check for performance bottlenecks, dead code, and missing documentation.
Embrace iterative loops: if an approach fails during Develop, pause and re-Plan.