typescript-pro

Enforce strict TypeScript rules across large codebases.

11|5|Updated Jan 9, 2026

Search Tags:#typescript #full-stack #eslint #refactor #type-safety #tsconfig

Ready to run

npx skills add https://github.com/rbergman/dark-matter-marketplace --skill typescript-pro-rbergman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typescript-pro
Source: https://github.com/rbergman/dark-matter-marketplace/tree/main/plugins/language-pro/skills/typescript-pro
Command: npx skills add https://github.com/rbergman/dark-matter-marketplace --skill typescript-pro-rbergman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces strict TypeScript discipline across large codebases, enabling teams to maintain rigorous type safety, reliable builds, and scalable architectures.

Core Features & Use Cases

Enforces strict TypeScript rules (no implicit any, no non-null assertions, explicit return types, and safe generics) across projects.
Guides project setup for TypeScript, ESLint, and build tooling, enabling consistent coding standards and faster onboarding.
Use Case: For a multi-service monorepo introducing TypeScript across teams, apply this Skill to audit tsconfig.json, lint configurations, and project structure during feature work, refactors, or debugging type errors.

Quick Start

Install and pin Node with mise (curl https://mise.run | sh; mise use node@22)
Initialize a new project and install essential dev dependencies
Run the project checks (typecheck, lint, and test) with npm run check

Frequently Asked Questions about typescript-pro

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

FAQPage Schema

How do I enforce strict TypeScript rules and eliminate explicit any across my codebase?▼

You can enforce strict TypeScript discipline by applying rules that prohibit implicit any, non-null assertions, and dangling promises. This approach mandates explicit return types, safe generics, and using unknown over any to maintain rigorous type safety across large projects.

What's the best way to configure ESLint and tsconfig for a full-stack TypeScript monorepo?▼

Configuring ESLint and tsconfig for full-stack TypeScript involves defining explicit module boundaries and strict type-safety rules. Auditing these configurations ensures consistent coding standards, reliable builds, and scalable multi-service architectures.

How do I refactor existing TypeScript code to use unknown instead of any?▼

Refactoring TypeScript to use unknown over any requires replacing explicit any types and applying strict type guards. This enforces non-negotiable type safety rules, eliminating unsafe type assertions during feature work and debugging.

Does strict TypeScript discipline work for both new and existing projects?▼

Yes, strict TypeScript discipline applies to both new and existing projects. It guides the review of project structure, lint configurations, and type-driven development, ensuring reliable builds whether you are initializing or refactoring.

Why does my TypeScript build fail when I enable strict mode and no non-null assertions?▼

Enabling strict mode and no non-null assertions causes build failures when code relies on unsafe type assumptions. Resolving these requires adding explicit return types, safe generics, and proper type guards to satisfy strict type-safety rules.

Do I need Node installed to set up a TypeScript project with strict type checking?▼

Yes, you need Node installed to initialize the project and install dev dependencies. The setup process involves pinning Node with a version manager, installing essential tools, and running typecheck, lint, and test checks.