Menu
Node.js gotchas and decision criteria. Covers async pitfalls, Express/NestJS patterns, and common mistakes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | nodejs-expert |
| description | Node.js gotchas and decision criteria. Covers async pitfalls, Express/NestJS patterns, and common mistakes. |
| autoInvoke | false |
| priority | high |
| triggers | ["nodejs","express","nestjs","fastify"] |
| paths | ["**/*.js","**/*.ts","package.json","server.*","app.*"] |
| allowed-tools | Read, Grep, Glob, Edit, Write |
| user-invocable | false |
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Use Context7 for Express/NestJS/Fastify docs.
decisions[4]{choice,use_when}:
Express vs NestJS vs Fastify,"Express: simple APIs. NestJS: enterprise/DI/decorators. Fastify: high perf"
Prisma vs TypeORM vs Drizzle,"Prisma: best DX/types. TypeORM: Active Record pattern. Drizzle: SQL-like + lightweight"
Zod vs Joi vs class-validator,"Zod: TS-first inference. Joi: runtime schemas. class-validator: NestJS decorators"
JWT vs session,"JWT: stateless/microservices. Session: monolith/server-rendered"
forEach + async: does NOT await. Use for...of or Promise.all(items.map(async ...))(err, req, res, next) — even if unused, or Express ignores itprocess.on('unhandledRejection')asyncHandler wrapper: wrap Express route handlers to catch async errors → next(err)req.body is undefined without express.json() middleware — common setup missprocess.env.PORT is string — parse with parseInt() or Number() before comparison@Injectable() with @Module({ providers: [...] }) — forgetting module registration = runtime errordrain event on writable streams for large data__dirname not available in ESM — use import.meta.dirname (Node 21+) or fileURLToPath(import.meta.url)CRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Without this, tasks route to wrong agents and use wrong models, degrading quality and wasting tokens.
5 techniques for different problem types. Use when stuck or facing complex challenges.
Structured thinking process for complex analysis. Supports revision, branching, and dynamic adjustment.
Angular 17+ gotchas and decision criteria. Covers signals vs observables, standalone patterns, and common pitfalls Claude gets wrong.
Designs RESTful APIs with endpoint naming, versioning strategies (URL path, header-based), pagination (offset and cursor), error response schemas, and OpenAPI conventions. Use when the user asks about REST API design, creating endpoints, URL structure, API versioning, status codes, Swagger, or OpenAPI specs.
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.