How do I install the Mynode skill?

Run npx skillmds@latest add sunfmin/mynode in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mynode safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mynode?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mynode free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mynode?

sunfmin (@sunfmin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mynode by sunfmin — Agent Skill

Name: Mynode
Author: sunfmin

Mynode

Mandatory Node.js, TypeScript, and pnpm project conventions — ESM, tsconfig, tooling, and code style. MUST be invoked before writing, modifying, or scaffolding any TypeScript code in a project with package.json and tsconfig.json. Contains binding rules that override default patterns for exports, imports, tooling choices, and configuration.

sunfmin de1b704 5 files · 11.3 KB Updated Sep 17, 2026

File contents

Node.js / TypeScript / pnpm Conventions

These are opinionated defaults for Node.js projects using TypeScript and pnpm. Apply them when writing new code or making configuration decisions. In existing projects, read the current conventions first — if the project disagrees with a rule below, follow the project unless it is clearly legacy.

Tooling

Concern	Choice	Never
Package manager	pnpm	npm, yarn
Module system	ESM (`"type": "module"`)	CommonJS (unless project already is)
Test runner	Vitest	Jest, mocha
TS execution (dev)	tsx	ts-node
Bundler (apps)	Vite	webpack, CRA
Bundler (libs)	tsup	raw tsc emit, rollup config
Lint	ESLint (flat config, `eslint.config.ts`)	.eslintrc legacy format
Format	Prettier	editor-only formatting
Node version	`packageManager` field + `.nvmrc`	unmanaged

pnpm rules

Install with pnpm add, run with pnpm run, execute with pnpm dlx (not npx).
Monorepo internal deps use workspace:*.
Always commit pnpm-lock.yaml. Never edit it by hand.
.npmrc defaults — strict-peer-dependencies=false, auto-install-peers=true.
Never set shamefully-hoist=true. If a tool breaks, add a targeted public-hoist-pattern[]=name.
Set "packageManager": "pnpm@<version>" in package.json.

tsconfig stance

For new projects and new packages. See references/tsconfig.md for full snippets.

strict: true — always.
moduleResolution: "bundler" — no .js extensions in imports.
verbatimModuleSyntax: true — forces explicit import type.
module: "ESNext", target: "ES2022".
noUncheckedIndexedAccess: true — new projects only, do not retrofit.
noEmit: true for apps (Vite handles emit); declaration: true for libs.

Code style

See references/code-style.md for examples.

Named exports only. Default exports only when a framework mandates them (Next.js pages, etc.).
import type { Foo } for type-only imports.
Prefer satisfies over as for type narrowing.
Use as const for literal config objects.
unknown over any. Using any requires a justification comment.
No enum. Use as const objects + union types.
No barrel files (index.ts re-exports). Import from specific module paths.
Arrow functions for callbacks; function declarations for exported public APIs.
File naming — kebab-case.ts for modules, PascalCase.tsx for React components.

Escape hatch

If the existing project uses CJS, Jest, npm, or any conflicting convention — match the project. Do not migrate or refactor existing patterns unless explicitly asked. These rules govern new decisions.

---name: mynodedescription: Mandatory Node.js, TypeScript, and pnpm project conventions — ESM, tsconfig, tooling, and code style. MUST be invoked before writing, modifying, or scaffolding any TypeScript code in a project with package.json and tsconfig.json. Contains binding rules that override default patterns for exports, imports, tooling choices, and configuration.---# Node.js / TypeScript / pnpm ConventionsThese are opinionated defaults for Node.js projects using TypeScript and pnpm. Apply them when writing new code or making configuration decisions. In existing projects, read the current conventions first — if the project disagrees with a rule below, follow the project unless it is clearly legacy.## Tooling| Concern | Choice | Never ||---------|--------|-------|| Package manager | pnpm | npm, yarn || Module system | ESM (`"type": "module"`) | CommonJS (unless project already is) || Test runner | Vitest | Jest, mocha || TS execution (dev) | tsx | ts-node || Bundler (apps) | Vite | webpack, CRA || Bundler (libs) | tsup | raw tsc emit, rollup config || Lint | ESLint (flat config, `eslint.config.ts`) | .eslintrc legacy format || Format | Prettier | editor-only formatting || Node version | `packageManager` field + `.nvmrc` | unmanaged |## pnpm rules- Install with `pnpm add`, run with `pnpm run`, execute with `pnpm dlx` (not npx).- Monorepo internal deps use `workspace:*`.- Always commit `pnpm-lock.yaml`. Never edit it by hand.- `.npmrc` defaults — `strict-peer-dependencies=false`, `auto-install-peers=true`.- Never set `shamefully-hoist=true`. If a tool breaks, add a targeted `public-hoist-pattern[]=name`.- Set `"packageManager": "pnpm@<version>"` in package.json.## tsconfig stanceFor new projects and new packages. See [references/tsconfig.md](references/tsconfig.md) for full snippets.- `strict: true` — always.- `moduleResolution: "bundler"` — no `.js` extensions in imports.- `verbatimModuleSyntax: true` — forces explicit `import type`.- `module: "ESNext"`, `target: "ES2022"`.- `noUncheckedIndexedAccess: true` — new projects only, do not retrofit.- `noEmit: true` for apps (Vite handles emit); `declaration: true` for libs.## Code styleSee [references/code-style.md](references/code-style.md) for examples.- Named exports only. Default exports only when a framework mandates them (Next.js pages, etc.).- `import type { Foo }` for type-only imports.- Prefer `satisfies` over `as` for type narrowing.- Use `as const` for literal config objects.- `unknown` over `any`. Using `any` requires a justification comment.- No `enum`. Use `as const` objects + union types.- No barrel files (`index.ts` re-exports). Import from specific module paths.- Arrow functions for callbacks; `function` declarations for exported public APIs.- File naming — `kebab-case.ts` for modules, `PascalCase.tsx` for React components.## Escape hatchIf the existing project uses CJS, Jest, npm, or any conflicting convention — match the project. Do not migrate or refactor existing patterns unless explicitly asked. These rules govern *new* decisions.

Frequently asked questions