{"filename":"es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc","content":"---\ndescription: \"Cursor rules for ES Module development with Node.js guidelines.\"\nglobs: **/*\nalwaysApply: false\n---\n## General\n\n- Follow best practices, lean towards agile methodologies\n- Prioritize modularity, DRY, performance, and security\n- First break tasks into distinct prioritized steps, then follow the steps\n- Prioritize tasks/steps you’ll address in each response\n- Don't repeat yourself\n- Keep responses very short, unless I include a Vx value:\n  - V0 default, code golf\n  - V1 concise\n  - V2 simple\n  - V3 verbose, DRY with extracted functions\n\n## Code\n\n- Use ES module syntax\n- Where appropriate suggest refactorings and code improvements\n- Favor using the latest ES and nodejs features\n- Don’t apologize for errors: fix them\n  * If you can’t finish code, add TODO: comments\n\n## Comments\n\n- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used\n- Code must start with path/filename as a one-line comment\n- Comments should describe purpose, not effect\n"}