typescript

Standardize TypeScript code with strict typing and node:test coverage.

47|11|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/styrene-lab/omegon --skill typescript-styrene-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/styrene-lab/omegon/tree/main/skills/typescript
Command: npx skills add https://github.com/styrene-lab/omegon --skill typescript-styrene-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write consistent, maintainable TypeScript by enforcing strong typing, predictable async patterns, and safer Node.js module usage.

Core Features & Use Cases

  • Strict typing guidance: Prefer interfaces, narrow unknown values, and avoid any so code stays resilient as it evolves.
  • Tooling and module conventions: Use Node.js built-ins with node: prefixes, ESM .js import specifiers, and separate type-checking for transpiled projects.
  • Testing and code organization: Keep logic modular, write node:test coverage, and follow project-friendly conventions for extension code and utilities.

Quick Start

Ask me to review or write TypeScript code using these conventions so I can produce safer modules, cleaner imports, and better tests.

Frequently Asked Questions about typescript

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

FAQPage Schema
How do I enforce strict typing and avoid any in TypeScript modules?

To enforce strict typing in TypeScript modules, prefer interfaces, explicitly narrow unknown values, and avoid any so code maintains resilience and predictability as it evolves.

What's the best way to configure ESM imports and Node.js built-ins in TypeScript?

The best way to configure ESM imports in TypeScript is using node: prefixes for Node.js built-ins and .js file specifiers to ensure predictable module resolution.

How do I set up node:test coverage for a TypeScript project?

Set up node:test coverage by keeping logic modular, writing tests using the native node:test runner, and validating the project with tsc --noEmit to ensure type safety without emitting files.

Do I need separate type-only imports for runtime-transpiled TypeScript projects?

Yes, you need separate type-only imports for runtime-transpiled TypeScript projects to isolate types from runtime code, ensuring accurate type-checking and cleaner transpilation.

How does tsc --noEmit validation work for TypeScript code quality?

The tsc --noEmit validation runs the TypeScript compiler to check types and catch errors without generating JavaScript output, ensuring strict code quality and type safety before runtime.