jeff-skill-typescript-project

Configure Node.js TypeScript projects with strict type checking and Vitest.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/jbaranski/jeff-claude --skill jeff-skill-typescript-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jeff-skill-typescript-project
Source: https://github.com/jbaranski/jeff-claude/tree/main/.claude/skills/jeff-skill-typescript-project
Command: npx skills add https://github.com/jbaranski/jeff-claude --skill jeff-skill-typescript-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure or update Node.js TypeScript projects with opinionated best practices to save time and ensure consistency across repos.

Core Features & Use Cases

  • Enforces strict TypeScript type checking
  • Integrates ESLint, Prettier, and Vitest for quality and tests
  • Provides scaffolding for common project layouts (src, tests, tsconfig, etc.)
  • Applies to new projects, migrations, and standardized tooling across teams

Quick Start

Create a TypeScript project skeleton in a repo with strict tooling as outlined.

Frequently Asked Questions about jeff-skill-typescript-project

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

FAQPage Schema
How do I configure a Node.js TypeScript project with strict type checking and Vitest?

Configure a Node.js TypeScript project by applying opinionated best practices that enforce strict type checking, integrate Vitest for testing, and align with Node.js LTS. This skill scaffolds backend, CLI, and library projects with minimal dependencies and robust scripted build and test workflows.

What is the best way to set up ESLint and Prettier for a new TypeScript project?

The best way to set up ESLint and Prettier is using an opinionated bootstrap that configures them alongside strict TypeScript settings. This ensures code quality and formatting consistency across new repositories and team standardized tooling without manual configuration overhead.

Can I use this TypeScript project setup for migrating an existing Node.js backend?

Yes, you can use this setup to update existing Node.js TypeScript projects. It applies opinionated best practices suitable for migrations, enforcing robust testing with Vitest and strict type checking across backend, CLI, and library project layouts.

Does this opinionated TypeScript bootstrap support frontend frameworks like React?

No, this opinionated TypeScript bootstrap does not target frontend frameworks. It specifically applies to backend, CLI, and library projects requiring strict type checking, minimal dependencies, and Node.js LTS alignment.

How do I scaffold a TypeScript library project with robust testing and minimal dependencies?

Scaffold a TypeScript library project by applying an opinionated configuration that enforces strict type checking, integrates Vitest and ESLint, and aligns with Node.js LTS. This provides a standardized src, tests, and tsconfig layout with minimal dependencies.

Why should I use an opinionated TypeScript project bootstrap instead of manual configuration?

Use an opinionated TypeScript project bootstrap to save time and ensure consistency across repos. It eliminates manual configuration errors by enforcing modern tooling, strict type checking, and standardized test workflows through a single automated setup process.