Home / Cursor rules / Node Express
Node Express
Node.js and Express.js best practices for backend development
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/node-express.mdc -o .cursor/rules/node-express.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/node-express.mdcContext cost: ≈543 tokens when used.
Rules file
--- description: "Node.js and Express.js best practices for backend development" globs: **/*.js, **/*.ts, src/**/*.ts alwaysApply: false --- # Node.js and Express.js Best Practices ## Project Structure - Use proper directory structure - Implement proper module organization - Use proper middleware organization - Keep routes organized by domain - Implement proper error handling - Use proper configuration management ## Express Setup - Use proper middleware setup - Implement proper routing - Use proper error handling - Configure proper security middleware - Implement proper validation - Use proper static file serving ## API Design - Use proper REST principles - Implement proper versioning - Use proper request validation - Handle errors properly - Implement proper response formats - Document APIs properly ## Database Integration - Use proper ORM/ODM - Implement proper migrations - Use proper connection pooling - Implement proper transactions - Use proper query optimization - Handle database errors properly ## Authentication - Implement proper JWT handling - Use proper password hashing - Implement proper session management - Use proper OAuth integration - Implement proper role-based access - Handle auth errors properly ## Security - Use proper CORS setup - Implement proper rate limiting - Use proper security headers - Implement proper input validation - Use proper encryption - Handle security vulnerabilities ## Performance - Use proper caching - Implement proper async operations - Use proper connection pooling - Implement proper logging - Use proper monitoring - Handle high traffic properly ## Testing - Write proper unit tests - Implement proper integration tests - Use proper test runners - Implement proper mocking - Test error scenarios - Use proper test coverage ## Deployment - Use proper Docker setup - Implement proper CI/CD - Use proper environment variables - Configure proper logging - Implement proper monitoring - Handle deployment errors ## Best Practices - Follow Node.js best practices - Use proper async/await - Implement proper error handling - Use proper logging - Handle process signals properly - Document code properly
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan