How do I install the Typescript Best Practices skill?

Run npx skillmds@latest add hoangnguyen0403/typescript-best-practices-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Typescript Best Practices safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Typescript Best Practices?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Typescript Best Practices free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Typescript Best Practices?

HoangNguyen0403 (@hoangnguyen0403) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Typescript Best Practices by hoangnguyen0403

Name: Typescript Best Practices
Rating: 4.2 (5 reviews)
Author: HoangNguyen0403

Typescript Best Practices

Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)

HoangNguyen0403 Updated Sep 9, 2026 542 repo stars

File contents

TypeScript Best Practices

Priority: P1 (OPERATIONAL)

Implementation Guidelines

Naming: Use PascalCase for Classes/Types/Interfaces, camelCase for variables/functions, and UPPER_SNAKE for static constants.
Functions: Use arrow functions for callbacks/logic; function declaration for top-level exports. Always type public API returns.
Modules: Use Named exports ONLY to enable better refactoring/auto-imports.
Async: Use async/await with Promise.all() for parallel execution. Implement try-catch for error handling; type catch(e) as unknown and narrow before use. Avoid .then().catch() chains.
Classes: Explicitly use private, protected, and public modifiers. Favor composition over inheritance and dependency injection with constructor injection and interfaces over singletons for testability.
Type Safety: Use never for exhaustiveness checks in switch-cases.
Optional: Use optional chaining (?.) and nullish coalescing (??) over manual checks.
Imports: Enforce external packages → internal modules → relative imports order automatically via eslint-plugin-import. Use import type for interfaces/types to ensure better tree-shaking and zero runtime overhead.
Validation: Use Zod or Tsoa for runtime boundary validation.

Anti-Patterns

No Default Exports: Use named exports.
No Implicit Returns: Specify return types.
No Unused Variables: Enable noUnusedLocals.
No require: Use ES6 import.
No Empty Interfaces: Use type or non-empty interface.
No any: Use unknown or a specific type.
No Unsafe Mocks: Cast with jest.Mocked<T> or as unknown as T.
No eslint-disable: Fix root cause; never suppress warnings.

References

See references/examples.md for Immutable Interfaces, Exhaustiveness Checking, Assertion Functions, DI Patterns, and Import Organization.

---name: typescript-best-practices-2description: Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)--- # TypeScript Best Practices ## **Priority: P1 (OPERATIONAL)** ## Implementation Guidelines - **Naming**: Use **`PascalCase`** for Classes/Types/Interfaces, **`camelCase`** for variables/functions, and **`UPPER_SNAKE`** for static constants. - **Functions**: Use **`arrow functions`** for callbacks/logic; **`function declaration`** for top-level exports. Always type **`public API`** returns. - **Modules**: Use **`Named exports`** ONLY to enable better refactoring/auto-imports. - **Async**: Use **`async/await`** with **`Promise.all()`** for parallel execution. Implement **`try-catch`** for error handling; type **`catch(e) as unknown`** and narrow before use. Avoid **`.then().catch()`** chains. - **Classes**: Explicitly use **`private`**, **`protected`**, and **`public`** modifiers. Favor **`composition`** over inheritance and **`dependency injection`** with **`constructor injection`** and interfaces over singletons for testability. - **Type Safety**: Use **`never`** for exhaustiveness checks in switch-cases. - **Optional**: Use **`optional chaining`** (`?.`) and **`nullish coalescing`** (`??`) over manual checks. - **Imports**: Enforce **`external packages → internal modules → relative imports`** order automatically via **`eslint-plugin-import`**. Use **`import type`** for interfaces/types to ensure better tree-shaking and zero runtime overhead. - **Validation**: Use **`Zod`** or **`Tsoa`** for runtime boundary validation. ## Anti-Patterns - **No Default Exports**: Use named exports. - **No Implicit Returns**: Specify return types. - **No Unused Variables**: Enable `noUnusedLocals`. - **No `require`**: Use ES6 `import`. - **No Empty Interfaces**: Use `type` or non-empty interface. - **No `any`**: Use `unknown` or a specific type. - **No Unsafe Mocks**: Cast with `jest.Mocked<T>` or `as unknown as T`. - **No eslint-disable**: Fix root cause; never suppress warnings. ## References See [references/examples.md](references/examples.md) for Immutable Interfaces, Exhaustiveness Checking, Assertion Functions, DI Patterns, and Import Organization.

Frequently asked questions