Node.js AI Coding Rules
Node.js powers millions of backend services, APIs, and CLI tools — and the quality of AI-generated Node.js code depends heavily on the rules you provide. Without guidelines, AI assistants miss async error handling, use blocking I/O, skip proper environment variable validation, and produce unstructured project layouts. Node.js AI rules encode best practices for asynchronous patterns, module organisation, security hardening, logging, and graceful shutdown so tools like Cursor and Copilot generate production-ready server code. AI Rules Hub hosts community-curated rules for Express, Fastify, native Node.js APIs, and modern ESM module conventions.
Why Use AI Rules for Node.js?
- Enforce async/await error handling so unhandled promise rejections never reach production
- Standardise environment variable validation with schemas (e.g., Zod, envalid)
- Require structured logging over raw `console.log` calls
- Define module organisation conventions for controllers, services, and repositories
- Enforce security best practices: input sanitisation, rate limiting, CORS configuration
Best Practices for Node.js AI Coding
Always Handle Async Errors
Rule AI to wrap all async route handlers and service calls with try/catch or to use an error-handling middleware pattern — never allow floating promises.
Validate Environment Variables at Startup
Instruct AI to validate all environment variables at application bootstrap using a schema validator — crashing fast is better than crashing during an API call.
Structured Logging With Context
Enforce structured JSON logging (pino, winston) with request IDs and correlation keys instead of ad-hoc `console.log` statements.
Separation of Concerns in Route Handlers
Route handlers should only parse requests and call service functions — no business logic or database queries inline in the handler.
Common Patterns & Standards
Repository Pattern for Database Access
Isolate all database queries in repository classes/functions so business logic remains testable without a database connection.
Graceful Shutdown Handling
Listen for `SIGTERM`/`SIGINT` signals, close database connections, and drain in-flight requests before exiting — required for container-based deployments.
Centralised Error Classes
Define a hierarchy of custom error classes (`ValidationError`, `NotFoundError`, `AuthError`) that middleware can catch and map to HTTP responses.
ESM Modules Over CommonJS
Standardise on ES module syntax (`import`/`export`) with top-level `await` where needed — rule AI away from `require()` in modern projects.
Top Node.js Rules on AI Rules Hub
Explore Related AI Rules
Share Your Node.js AI Rules
Have rules that improved your Node.js workflow? Submit them to AI Rules Hub and help the community get better results from AI coding assistants.