claudeskills.page

14 skills · 7 categories

Claude Code skills for Node.js

Node.js skills for production servers: Express, Fastify, NestJS and Hono services, background workers, streams and backpressure, graceful shutdown, and profiling the event loop when latency climbs.

Install all 14 Browse the list

Start with these

  1. 1

    Node.js Profiling

    Flamegraphs and event loop lag, not guesses

    Claude reproduces the slowdown with a load test, classifies it as CPU-bound, event-loop blocking, I/O wait or GC pressure using event loop utilization and lag percentiles, then captures the matching profile with Node's built-in flags. It reads flamegraphs by self time, fixes the specific hot path, and reports before and after p99 latency from the identical load run.

  2. 2

    Bun Runtime

    Adopt Bun one role at a time, with proof

    Claude treats Bun as four separate tools and adopts the low-risk ones first: package manager, then test runner, then bundler, then runtime. It commits the text lockfile, freezes it in CI, audits blocked install scripts, writes Bun.serve handlers with graceful shutdown and raised idle timeouts, and proves Node compatibility with the real suite and a staging image before anything ships.

  3. 3

    Express on Node

    Express 5 services that fail loudly and shut down cleanly

    Claude structures Express apps around a testable app factory, orders middleware deliberately, validates bodies with Zod, and sends every failure through one problem+json error handler. It knows the Express 4 to 5 routing and async changes, tunes keep-alive against load balancer timeouts, and wires SIGTERM handling so deploys stop dropping in-flight requests.

All 14 Node.js skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

Frontend 1

No. 054

htmx Hypermedia

Server-rendered fragments instead of a SPA

Claude builds htmx features the hypermedia way: a working full-page version first, then fragments rendered from the same template blocks, real URLs with pushed history, and server-driven events through HX-Trigger. It knows the htmx 2 changes that bite — unswapped 4xx responses, 204 meaning no swap, redirects that land inside the target — and checks every endpoint with and without HX-Request.

htmx-hypermedia 209 lines

Backend & APIs 5

No. 079

Bun Runtime

Adopt Bun one role at a time, with proof

Claude treats Bun as four separate tools and adopts the low-risk ones first: package manager, then test runner, then bundler, then runtime. It commits the text lockfile, freezes it in CI, audits blocked install scripts, writes Bun.serve handlers with graceful shutdown and raised idle timeouts, and proves Node compatibility with the real suite and a staging image before anything ships.

bun-runtime 223 lines
No. 082

Express on Node

Express 5 services that fail loudly and shut down cleanly

Claude structures Express apps around a testable app factory, orders middleware deliberately, validates bodies with Zod, and sends every failure through one problem+json error handler. It knows the Express 4 to 5 routing and async changes, tunes keep-alive against load balancer timeouts, and wires SIGTERM handling so deploys stop dropping in-flight requests.

express-node 196 lines
No. 088

Hono on the Edge

One typed API for Workers, Bun, Deno and Node

Claude writes Hono apps against Web standard APIs so they run on Workers, Bun, Deno or Node, with Bindings and Variables typed from the start. Inputs pass through Zod or Standard Schema validators, errors flow through one onError handler, and routes are chained so the exported AppType gives the frontend a fully typed hc client without hand-written fetch wrappers.

hono-edge 201 lines
No. 090

NestJS Modules

Clear module boundaries and enhancers in the right place

Claude organizes NestJS code into feature modules with small export lists, uses injection tokens instead of interfaces that vanish at runtime, and avoids request scope unless it is truly needed. Auth goes in guards, validation in a global ValidationPipe, mapping in interceptors, and tests override providers through the testing module so e2e runs use the same global config as production.

nestjs-modules 172 lines
No. 099

tRPC APIs

Typesafe procedures with auth that narrows context

Claude builds tRPC routers with a cheap typed context, protected and role-based base procedures that narrow ctx.user, Zod validation on input and output, and per-object ownership checks inside each procedure. The client imports only the router type, uses the v11 TanStack Query integration for queries and invalidation, and createCaller tests prove that the unauthorized and not-found paths hold.

trpc-apis 280 lines

Testing 1

No. 141

Testcontainers

Real databases in tests, started once and reset fast

Claude replaces database mocks and H2 stand-ins with the production engine in a container, started once per run rather than per test. It runs the real migrations, picks rollback, truncation, template databases or snapshots for isolation, gives each parallel worker its own database, and sets up GitHub Actions or GitLab Docker-in-Docker so the suite passes cold, shuffled and in parallel.

testcontainers 202 lines · 2 files

Cloud Platforms 3

No. 179

Azure Functions

Current models, managed identity and handled poison queues

Claude builds function apps on the current programming model for each language, migrating off in-process .NET and function.json-era code before the support cutoff. It picks a hosting plan from latency and networking needs, connects triggers through managed identity and Key Vault references, tunes host.json per trigger, and makes sure failing messages land in a monitored poison or dead-letter queue.

azure-functions 204 lines
No. 182

Cloudflare Workers

Right storage per binding, typed env, one-command rollback

Claude configures Workers with explicit compatibility dates, generated binding types and per-environment bindings, then picks KV, D1, R2, Durable Objects or Queues from the access pattern rather than habit. Code stays inside CPU and memory limits, tests run in the real Workers runtime via Vitest, and releases go out as versions with traffic splitting and a known rollback.

cloudflare-workers 203 lines
No. 190

Vercel Deploys

Reproducible builds, scoped env vars, instant rollback

Claude reproduces Vercel builds locally with vercel pull and vercel build before guessing, scopes env vars per Production, Preview and branch, and remembers that changes need a redeploy. Functions run on the Node.js runtime near the database with sensible maxDuration, previews stay protected, monorepo builds skip unaffected apps, and production moves by promotion with a known rollback.

vercel-deploys 158 lines

Security 1

No. 286

Security Headers

Strict CSP shipped without breaking production

Claude ships a nonce-based CSP with strict-dynamic through a Report-Only phase instead of pasting a policy that breaks checkout. It configures HSTS in safe steps, replaces X-Frame-Options with frame-ancestors, fixes CORS that reflects origins with credentials, and knows the nginx and Next.js traps. A bundled checker grades any URL you own and fails CI on regressions.

security-headers 190 lines · 2 files

Performance 2

No. 303

Node.js Profiling

Flamegraphs and event loop lag, not guesses

Claude reproduces the slowdown with a load test, classifies it as CPU-bound, event-loop blocking, I/O wait or GC pressure using event loop utilization and lag percentiles, then captures the matching profile with Node's built-in flags. It reads flamegraphs by self time, fixes the specific hot path, and reports before and after p99 latency from the identical load run.

node-profiling 183 lines
No. 301

Memory Leak Hunting

From growing heap to the exact retaining reference

Claude separates real leaks from warming caches by repeating one action with forced GC, then uses the three-snapshot comparison to find object types that grow per round. It follows the retainer chain to the first reference your code owns, such as a listener, timer, unbounded Map or uncleaned effect, fixes it, and reruns the same loop to show flat memory.

memory-leak-hunting 159 lines · 2 files

Integrations 1

No. 404

Discord Bots

Slash-command bots that never miss the 3-second window

Claude builds discord.js v14 bots with only the intents they use, a separate deploy script for slash commands, and handlers that defer before slow work so Unknown interaction errors stop. Buttons and selects encode record IDs in customId so they survive restarts and shards, and serverless endpoints verify Ed25519 signatures before answering PING.

discord-bots 238 lines

Install

Every Node.js skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- node-profiling bun-runtime express-node hono-edge nestjs-modules memory-leak-hunting discord-bots htmx-hypermedia trpc-apis testcontainers azure-functions cloudflare-workers vercel-deploys security-headers

Node.js skills FAQ

What is the best Claude Code skill for Node.js?

Start with Node.js Profiling: Flamegraphs and event loop lag, not guesses. Then add Bun Runtime and Express on Node, which cover the next most common Node.js requests.

How do I install all 14 Node.js skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- node-profiling bun-runtime express-node hono-edge nestjs-modules memory-leak-hunting discord-bots htmx-hypermedia trpc-apis testcontainers azure-functions cloudflare-workers vercel-deploys security-headers. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these Node.js skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

Related technologies

esc