Nodejs Best Practices

This one actually teaches you to think instead of pattern matching. It's built around decision trees for framework selection (Hono vs Fastify vs Express based on deployment target), architecture principles that scale from scripts to enterprise apps, and a security checklist that doesn't assume you know what to worry about. The best part is the explicit "ask the user for preferences" philosophy instead of defaulting to the same stack every time. Use it when you're tired of Claude suggesting Express for edge functions or when you need to justify why you picked one runtime over another. It's opinionated about 2025 tooling but explains the reasoning behind each choice.

skills.sh installs: 558
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --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 Node.js development in 2025. 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 (2025)

Decision Tree

What are you building?
│
├── Edge/Serverless (Cloudflare, Vercel)
│   └── Hono (zero-dependency, ultra-fast cold starts)
│
├── High Performance API
│   └── Fastify (2-3x faster than Express)
│
├── 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