Odin Typescript

Use when asked to create a complete Node.js 24 TypeScript 7 command-line project. Not for a Next.js app scaffold: use scaffold-nextjs.

Use when asked to scaffold a Next.js turborepo end to end and verify it. Not for a CLI scaffold: use scaffold-cli. Not for course exercises: use scaffold-exercises.

Use when asked to enforce boundaries, set up deep modules, stop deep imports, mutation-prove rules, or make entry-point packages. Not for remote, credential, publish, deploy, or irreversible changes.

Use when asked to test Fastify applications without network sockets. Not for building the app: use fastify-schema-first-service.

Use when asked to build Node.js stream ETL pipelines for large-file or continuous ingestion without exceeding heap memory. Not for remote, credential, publish, deploy, or irreversible changes.

Use when Node.js segfaults, addon crashes, leaks, event-loop anomalies, thread-pool saturation, V8 deoptimizations, or binding.gyp failures need diagnosis. Not for code edits or service restarts.

Use when asked to implement or fix service termination: SIGTERM or SIGINT, connection draining, health-check signaling. Not for general service scaffolding: use nodejs-service-foundations.

Use when migrating a JavaScript or TypeScript project from ESLint, Prettier, Standard, or mixed legacy lint configuration to Biome 2.5.

Use when a request concerns multi-tenant scaffolding, tenant isolation, domain wiring, or SaaS architecture on Cloudflare or Vercel. Not for single-tenant apps: use scaffold-nextjs or scaffold-cli.

Use when TypeScript needs shaping toward narrow types, unions, exhaustive variants, and strict flags. Not for error repair: use typescript-type-hardening. Not for non-TS domains: use type-driven.

Use when TypeScript has type errors, failing inference, or needs type mechanism repair (generics, infer, mapped, branded). Not for strict flags or proactive shaping: use typescript-best-practices.

Use when asked to set up or harden Node.js service foundations: env validation, logging, typed errors, type stripping, and shutdown wiring. Not for dedicated shutdown: use nodejs-graceful-shutdown.

Use when asked to prepare a Fastify service for production load and exposure. Not for building the app: use fastify-schema-first-service.

Use when building or extending a Fastify application: routes, plugins, hooks, database wiring. Not for testing: use fastify-inject-testing. Not for hardening: use fastify-production-hardening.

Use when asked to diagnose Node.js tests that hang after the runner reports completion. Not for remote, credential, publish, deploy, or irreversible changes.

Use when TypeScript tests use unsafe any or as assertions for partial or intentionally invalid fixtures. Not for production source or manifest edits. Test files only.