typescript

Standardize TypeScript and JavaScript code with strict types and Zod validation.

Updated Apr 10, 2026

Search Tags:#typescript #javascript #imports #type-safety #coding-standards #naming-conventions #zod-validation

Ready to run

npx skills add https://github.com/erichugy/agentic.skills --skill typescript-erichugy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/erichugy/agentic.skills/tree/main/typescript
Command: npx skills add https://github.com/erichugy/agentic.skills --skill typescript-erichugy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

TypeScript and JavaScript projects often suffer from inconsistent conventions, weak type safety, and varied naming, imports, and validation practices across files. This Skill provides a unified set of conventions to improve readability, maintainability, and reliability.

Core Features & Use Cases

Enforces strict mode in tsconfig and prohibits // @ts-ignore to catch issues early.
Provides naming, type, and import conventions to ensure consistency across the codebase.
Includes guidance on Zod validation, discriminated unions, and explicit return types for safer APIs.

Quick Start

Apply these conventions to every new or refactored TS/JS file to ensure consistency and safety.

Frequently Asked Questions about typescript

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

FAQPage Schema

How do I enforce TypeScript strict mode and stop using ts-ignore in my projects?▼

To enforce TypeScript strict type safety, you must always enable strict mode in tsconfig.json and prohibit using @ts-ignore comments. This catches type issues early during compilation and ensures consistent, safer code across your project.

What are the best TypeScript naming and import conventions for project consistency?▼

The best TypeScript naming and import conventions rely on centralized rules to standardize file naming, type definitions, and import structures across your codebase. Applying these conventions ensures readability, maintainability, and reduces onboarding time for new developers.

How do I standardize TypeScript and JavaScript coding practices to reduce bugs?▼

Standardizing TypeScript and JavaScript coding practices involves applying a unified set of conventions for strict types, naming, imports, and Zod validation. Implementing these project-wide rules reduces bugs and ensures reliability across all files.

When should I avoid type assertions in TypeScript refactoring?▼

You should avoid questionable type assertions in TypeScript refactoring when strict type safety is required. Relying on centralized conventions and explicit return types instead of type assertions prevents hidden type errors and ensures safer APIs.

Does this TypeScript coding standard work for both writing and reviewing code?▼

Yes, these TypeScript coding standards are explicitly designed for writing, reviewing, and refactoring code across TypeScript and JavaScript projects. The conventions enforce strict types, naming, imports, and validation rules consistently.