ワンクリックで
node-best-practices
Best practices for Node.js development with TypeScript using type stripping
メニュー
Best practices for Node.js development with TypeScript using type stripping
Personalize a freshly cloned `metaimed-starter` (or compatible type-cascade monorepo) by interviewing the user about project name, primary domain, audience, tone and brand, then rendering AGENT.md, CLAUDE.md, and design/*.md from the answers, generating ENCRYPTION_KEY + JWT_SECRET_KEY, installing dependencies, bringing up docker-compose, applying the initial Prisma migration + triggers, and finally spawning checkpoint agents in sequence (design system → auth vertical → first CRUD domain → deploy infra) with user review between each. Use when the user opens a fresh clone of this starter and asks to "initialize the project", "personalize the starter", "set up the new project", "let's begin", "start building" or any first-day greenfield request. Skip cloning — assume the working directory is already a starter clone.
Technical writer specializing in the Diátaxis documentation framework
Comprehensive best practices for Fastify development
Linting workflows with neostandard and ESLint v9 flat config
Deep Node.js internals expertise including C++ addons, V8, libuv, and build systems
OAuth 2.0/2.1 specification expert with deep RFC knowledge and Fastify integration patterns
| name | node-best-practices |
| description | Best practices for Node.js development with TypeScript using type stripping |
| metadata | {"tags":"node, nodejs, javascript, typescript, type-stripping, backend, server"} |
Use this skill whenever you are dealing with Node.js code to obtain domain-specific knowledge for building robust, performant, and maintainable Node.js applications.
When writing TypeScript for Node.js, use type stripping (Node.js 22.6+) instead of build tools like ts-node or tsx. Type stripping runs TypeScript directly by removing type annotations at runtime without transpilation.
Key requirements for type stripping compatibility:
import type for type-only imports.ts extensions in importsSee rules/typescript.md for complete configuration and examples.
Read individual rule files for detailed explanations and code examples: