lang-ts

Standardizing TypeScript code style involves applying the Google TypeScript Style Guide alongside strict compiler settings, Prettier formatting, and typescript-eslint linting to enforce consistent naming, structure, and type safety.

Configuring strict typing and reliable tests requires enabling strict mode, explicit return types, and discriminated unions, paired with testing tools like Vitest or Jest. This Skill outlines these type-safe design conventions and tooling directions for setup.

This Skill works for both new TypeScript services and existing codebases. You can use it when starting a new service, reviewing team conventions, or aligning an existing project with safer patterns like using unknown instead of any.

Using unknown instead of any in TypeScript enforces type safety by requiring type checking before performing operations on the variable. This practice is promoted by this Skill to keep code readable, type-safe, and easier to maintain across projects.

For TypeScript development, this Skill recommends using Vitest or Jest as testing tools, combined with Prettier for formatting and typescript-eslint for linting, ensuring reliable tests and consistent code standards.

You need to apply TypeScript code standards when you want code to stay readable, type-safe, and easier to maintain across projects. This is useful when starting a new TypeScript service, reviewing team conventions, or aligning an existing codebase.