nodejs-best-practices

Guide Node.js architecture decisions with framework selection and best-practices guidance.

Updated May 12, 2025
One-click install
npx skills add https://github.com/nicoarbelaez/portfolio --skill nodejs-best-practices-nicoarbelaez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nodejs-best-practices
Source: https://github.com/nicoarbelaez/portfolio/tree/main/.agents/skills/nodejs-best-practices
Command: npx skills add https://github.com/nicoarbelaez/portfolio --skill nodejs-best-practices-nicoarbelaez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams standardize and improve Node.js development decisions, reducing architecture drift by providing principled guidance rather than copy-paste patterns.

Core Features & Use Cases

  • Framework selection guidance for projects ranging from edge to enterprise, with trade-off considerations.
  • Async pattern and error-handling guidelines to promote robust and maintainable code.
  • Security and deployment best-practices to prevent common misconfigurations and vulnerabilities.
  • Use cases include designing a new API, refactoring a monolith, or evaluating runtimes and packages for performance and reliability.

Quick Start

Provide your deployment target and constraints, then select the Node.js approach that best fits the current context.

Frequently Asked Questions about nodejs-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Node.js framework for a scalable architecture?

To choose a Node.js framework, apply decision-tree guidance evaluating deployment targets and trade-offs from edge to enterprise, ensuring your selection aligns with scalable architecture requirements and specific project constraints to prevent architecture drift.

What are the best Node.js async patterns for robust error handling?

The best Node.js async patterns utilize layered-architecture guidance and specific error-handling strategies to promote maintainable code, providing validation principles and anti-pattern alerts to prevent uncaught asynchronous exceptions and improve reliability.

Does this Node.js best-practices guidance work for refactoring a monolith?

Yes, this guidance applies to refactoring a monolith by providing principled architecture decisions, runtime recommendations, and security hardening strategies that scale from solo projects to large teams without copy-paste patterns.

What is the best way to apply security hardening in a Node.js application?

The best way to apply security hardening involves following deployment best-practices and validation principles to prevent common misconfigurations and vulnerabilities, utilizing anti-pattern alerts to identify and mitigate potential security risks.

When should I not use specific Node.js architecture anti-patterns?

You should avoid Node.js architecture anti-patterns when standardizing development decisions across large teams, as relying on copy-paste patterns instead of principled guidance causes architecture drift and reduces code maintainability.