typescript-code-standards

Configure TypeScript toolchain with strict compiler, ESLint, Jest, and pre-commit settings.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill typescript-code-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-code-standards
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/typescript-code-standards
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill typescript-code-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent TypeScript project setups by enforcing a dependable baseline for compilation, linting, testing, and commit-time quality checks.

Core Features & Use Cases

  • Toolchain-aligned configuration: Provides a canonical tsconfig.json with strict typing defaults and a separate Jest test config.
  • ESLint flat config rules: Establishes deterministic linting (including JSDoc requirements and import ordering) that matches modern ESLint v9+ expectations.
  • Jest quality gate: Defines Jest configuration with coverage collection and strict global 100% thresholds suitable for spec-driven development.

Use case example: You are starting a new TypeScript repo or rescuing an existing one whose linting, type-checking, and test coverage are uneven; apply this standard to quickly converge on one consistent, reviewable configuration.

Quick Start

Ask an AI to “apply the typescript-code-standards standard to this repository by generating/adjusting tsconfig.json, eslint.config.mjs, jest.config.js, package.json scripts, and Husky + lint-staged pre-commit hooks, keeping the team/personal scope rules in mind.”

Frequently Asked Questions about typescript-code-standards

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

FAQPage Schema
How do I configure ESLint flat config with JSDoc and import-order rules in TypeScript?

To configure ESLint flat config with JSDoc and import-order rules, apply a canonical ESLint v9+ setup that establishes deterministic linting matching modern TypeScript expectations. This standardizes linting behavior across new and existing TypeScript projects.

Why does my TypeScript project need Husky and lint-staged pre-commit hooks?

TypeScript projects need Husky and lint-staged pre-commit hooks to enforce commit-time quality checks. This prevents inconsistent code by running automated linting and formatting gates before changes are committed to the repository.

Can I enforce strict 100% Jest coverage thresholds in a TypeScript project?

You can enforce strict 100% Jest coverage thresholds by applying a canonical Jest configuration with coverage collection. This establishes a quality gate suitable for spec-driven TypeScript development.

What's the best way to standardize tsconfig.json strict typing defaults for a new TypeScript repo?

The best way to standardize tsconfig.json strict typing defaults is to apply a canonical compiler configuration. This enforces a dependable baseline for compilation and separates Jest test configuration.

Does this TypeScript toolchain configuration require adjusting existing npm scripts?

Yes, applying this TypeScript toolchain standard involves aligning npm scripts and quality gates. This ensures compilation, linting, testing, and pre-commit tooling integrate properly into your existing workflow.

When do I need to standardize TypeScript project tooling configuration?

You need to standardize TypeScript project tooling configuration when starting a new repo or rescuing an existing one with uneven linting, type-checking, and test coverage, ensuring one consistent, reviewable setup.