Nodejs Best Practices

This is a decision framework, not a code generator. It walks you through choosing between Express, Fastify, Hono, or NestJS based on deployment target and team context, then covers error handling patterns, async strategies, and validation library tradeoffs. The framework selection decision tree is genuinely useful if you're tired of defaulting to Express for everything. It emphasizes asking the user for preferences and thinking through architecture choices rather than copy-pasting boilerplate. Covers Node.js 24's native TypeScript support and includes a solid security checklist. Best for developers who want to understand the reasoning behind Node.js patterns, not for someone who just wants working code dropped into their project immediately.

skills.sh installs: 138
GitHub stars: 7.6K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vudovn/antigravity-kit --skill nodejs-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Node.js Best Practices

Principles and decision-making for modern Node.js development. Learn to THINK, not memorize code patterns.

⚠️ How to Use This Skill

This skill teaches decision-making principles, not fixed code to copy.

ASK user for preferences when unclear
Choose framework/pattern based on CONTEXT
Don't default to same solution every time

1. Framework Selection

Decision Tree

What are you building?
│
├── Edge/Serverless (Cloudflare, Vercel)
│   └── Hono (zero-dependency, ultra-fast cold starts)
│
├── High Performance API
│   └── Fastify (~5x req/sec of Express in Fastify's own hello-world benchmark; benchmark your own workload)
│
├── Enterprise/Team familiarity
│   └── NestJS (structured, DI, decorators)
│
├── Legacy/Stable/Maximum ecosystem
│   └── Express (mature, most middleware)
│
└── Full-stack with frontend
    └── Next.js API Routes or tRPC