node-tooling

Enforces Node.js/TypeScript tooling structure and deterministic Vitest unit tests in a pnpm workspace.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill node-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-tooling
Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/node-tooling
Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill node-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle, inconsistent development of Node.js + TypeScript + pnpm tooling by enforcing functional structure, deterministic testing, and version verification so workspace changes don’t break silently.

Core Features & Use Cases

  • Workspace-safe capability checks: Verifies installed Node/pnpm/library versions before relying on features, otherwise records an explicit unknown checklist.
  • Functional architecture guidance: Encourages a clean separation between pure src/domain/ logic (no IO) and thin src/infra/ shells for filesystem/process/network integration.
  • Deterministic, agent-friendly testing: Uses Vitest with clear rules for fixtures, avoids network calls in tests, and supports DOM tests in happy-dom when required.
  • pnpm dependency management discipline: Provides consistent commands for adding deps and adding them to specific workspaces without fabricating versions.

Quick Start

Create or update your Node.js/TypeScript tooling in this workspace by following the skill’s domain/infra structure and Vitest fixture-based testing rules, and verify versions with pnpm and node before using specific capabilities.

Frequently Asked Questions about node-tooling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write deterministic Vitest unit tests for Node.js tooling without network calls?

To write deterministic Vitest unit tests, isolate pure domain logic from infrastructure shells and use local fixtures. This avoids network dependence and prevents flaky tests in your Node.js TypeScript workspace.

What is the best way to manage dependencies in a pnpm workspace for TypeScript packages?

The best way to manage pnpm dependencies is using consistent commands for adding packages to specific workspaces. Verify versions via package.json and lockfiles to prevent silent breaks across the repo.

How do I structure a Node.js TypeScript tooling package to separate domain logic from infrastructure?

Structure your Node.js TypeScript tooling by placing pure logic in src/domain/ with no IO, and thin integration shells in src/infra/. This functional separation ensures testable and maintainable workspace packages.

Can I verify Node and pnpm versions before relying on specific library features in my tooling?

Yes, you can verify Node and pnpm versions before relying on features. If verification fails, the tooling records an explicit unknown checklist to avoid assuming unverified workspace capabilities.

Does Vitest work with happy-dom for testing DOM components in a TypeScript pnpm workspace?

Yes, Vitest supports DOM tests using happy-dom when required. This allows you to test DOM components deterministically within your Node.js TypeScript pnpm workspace without external network dependencies.

Why are my Node.js TypeScript tooling tests flaky across different workspace environments?

Tests become flaky when mixing IO with domain logic or relying on network calls. Enforce functional domain/infra separation and use Vitest fixtures to achieve deterministic, agent-friendly testing outcomes.