Home › All rules › Community › Es Module Nodejs Guidelines Cursor Rules
Es Module Nodejs Guidelines Cursor Rules
Cursor rules for ES Module development with Node.js guidelines.
CursorNode.js / TypeScriptCommunity (CC0)
How to use
Save this as .cursor/rules/es-module-nodejs-guidelines-cursorrules-prompt-fil.mdc in your project, commit it, and Cursor will load it. Review it first: community files can be opinionated or out of date.
Note: Review and test before use. Provided as is, without warranty. See Terms.
.cursor/rules/es-module-nodejs-guidelines-cursorrules-prompt-fil.mdcDownload ---
description: "Cursor rules for ES Module development with Node.js guidelines."
globs: **/*
alwaysApply: false
---
## General
- Follow best practices, lean towards agile methodologies
- Prioritize modularity, DRY, performance, and security
- First break tasks into distinct prioritized steps, then follow the steps
- Prioritize tasks/steps you’ll address in each response
- Don't repeat yourself
- Keep responses very short, unless I include a Vx value:
- V0 default, code golf
- V1 concise
- V2 simple
- V3 verbose, DRY with extracted functions
## Code
- Use ES module syntax
- Where appropriate suggest refactorings and code improvements
- Favor using the latest ES and nodejs features
- Don’t apologize for errors: fix them
* If you can’t finish code, add TODO: comments
## Comments
- Comments should be created where the operation isn't clear from the code, or where uncommon libraries are used
- Code must start with path/filename as a one-line comment
- Comments should describe purpose, not effect