typescript

Configure strict TypeScript compiler settings and monorepo project references.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kittne/codex-skills-by-codex --skill typescript-kittne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/kittne/codex-skills-by-codex/tree/main/typescript
Command: npx skills add https://github.com/kittne/codex-skills-by-codex --skill typescript-kittne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Build, review, and operate production TypeScript codebases with strict typing, stable module boundaries, modern Node.js resolution, and reliable build/test workflows. Use for tsconfig design, monorepo project references, API contract typing, runtime validation boundaries, refactors, and CI hardening.

Core Features & Use Cases

  • Strict compiler defaults and shared tsconfig inheritance to ensure consistency.
  • Separate domain types, transport types, and generated types to keep boundaries clear and maintainable.
  • Monorepo project references to constrain the type graph and improve build performance.
  • Practical guidance for runtime validation and API surface stability.

Quick Start

Configure a strict TypeScript baseline and validate a monorepo with project references.

Frequently Asked Questions about typescript

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

FAQPage Schema
How do I configure TypeScript project references for a monorepo?

TypeScript project references constrain the type graph and improve build performance by linking multi-package repositories. You configure tsconfig files to establish module boundaries, ensuring stable API surfaces and reliable builds across separate domain packages.

What is the best way to enforce strict TypeScript typing across multiple packages?

Strict TypeScript typing across multiple packages is enforced by applying strict compiler defaults and shared tsconfig inheritance. This baseline ensures consistency, aligns lint rules and tests, and maintains API stability across teams.

Why does module resolution fail in my Node.js monorepo build?

Module resolution failures in Node.js monorepos often stem from misaligned compilerOptions. Applying modern Node.js resolution settings and project references establishes clear module boundaries to prevent unstable type graph errors.

Can I separate domain types and transport types in a TypeScript codebase?

You can separate domain types, transport types, and generated types to keep boundaries clear and maintainable. This separation enforces API contract typing stability and aligns runtime validation boundaries within your TypeScript codebase.

Do I need to align CI processes with tsconfig settings for typecheck safety?

Aligning CI processes with tsconfig settings is required to enforce typecheck safety. Aligning compilerOptions, lint rules, and tests within your CI workflows guarantees consistency and prevents unstable builds across development teams.

When should I not use TypeScript project references?

TypeScript project references may be unnecessary for single-package repositories without complex module boundaries. If your codebase does not require a constrained type graph or multi-package build performance improvements, standard tsconfig setups suffice.