typescript

Enforce strict TypeScript practices with ESLint, Jest, and CI quality gates.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill typescript-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/lciacci/tessera/tree/main/skills/typescript
Command: npx skills add https://github.com/lciacci/tessera --skill typescript-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents common TypeScript defects and inconsistent engineering practices by enforcing strict typing, disciplined project structure, linting, testing, and quality checks.

Core Features & Use Cases

  • Strict Type Safety: Configure TypeScript to catch implicit any values, nullability issues, unused code, missing returns, and inconsistent casing.
  • Quality Tooling: Establish ESLint, Jest, Prettier, GitHub Actions, and pre-commit checks for consistent validation throughout development.
  • Robust Type Patterns: Use discriminated unions, branded identifiers, const assertions, runtime validation with Zod, and explicit error handling.
  • Use Case: Apply this Skill when building or reviewing a TypeScript service so its domain logic, infrastructure boundaries, tests, and CI quality gates remain maintainable and reliable.

Quick Start

Ask the TypeScript skill to configure strict mode, ESLint, Jest, and CI checks for the current TypeScript project.

Frequently Asked Questions about typescript

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

FAQPage Schema
How do I configure strict TypeScript to prevent implicit any and nullability errors?

To configure strict TypeScript, enable strict compiler settings to catch implicit any values, nullability issues, unused code, and missing returns. This enforces type safety and prevents common type errors across your application code.

What's the best way to set up ESLint and Jest quality gates for a TypeScript project?

The best way to set up quality gates is configuring typed ESLint rules, Jest tests with coverage validation, and automated pre-commit or GitHub Actions checks to ensure consistent validation throughout development.

How do I validate runtime types in TypeScript using Zod?

To validate runtime types in TypeScript, use Zod for runtime validation alongside robust type patterns like discriminated unions, branded identifiers, and const assertions to ensure type safety and explicit error handling.

Does this strict TypeScript configuration work with TSX application code and infrastructure layers?

Yes, this strict TypeScript configuration applies to TSX application code, configuration files, unit tests, and infrastructure layers, ensuring domain logic and infrastructure boundaries remain maintainable and reliable.

Why should I use strict mode and pre-commit checks for TypeScript development?

You should use strict mode and pre-commit checks to prevent inconsistent structure and untested code. This disciplined approach stops common TypeScript defects by enforcing quality validation before code changes are committed.