typescript-code-style

Enforce idiomatic TypeScript 5.9+ style with ESM imports and naming conventions.

1|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Jylhis/skills --skill typescript-code-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-code-style
Source: https://github.com/Jylhis/skills/tree/main/skills/typescript-code-style
Command: npx skills add https://github.com/Jylhis/skills --skill typescript-code-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript codebases often drift into inconsistent naming, layout, and import patterns, making maintenance harder. This Skill provides a clear, opinionated set of conventions for TypeScript 5.9+ on Node 22 LTS to keep code cohesive and readable across teams.

Core Features & Use Cases

  • ESM-first layout: Enforce ES module structure and explicit extensions to prevent runtime surprises.
  • Single-responsibility files: Favor one concept per file and avoid barrel files to improve tree-shaking and navigation.
  • Naming conventions: Apply PascalCase for types/classes, camelCase for values/functions, and UPPER_SNAKE for module constants.
  • Imports & modules: Enforce explicit extensions, consistent import order, and minimized re-exports.
  • Use Case: On a large TS project, apply these rules to standardize code across packages and teams.

Quick Start

Apply these TypeScript style rules to your codebase to enforce consistent naming, file layout, and import order.

Frequently Asked Questions about typescript-code-style

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

FAQPage Schema
How do I enforce consistent TypeScript code style across multiple projects?

Enforce idiomatic TypeScript style across projects by applying opinionated conventions for naming, layout, and imports. This standardizes code structure for TS 5.9+ codebases on Node 22 LTS to improve readability and maintainability across teams.

Why should I use explicit .js extensions in ES module imports?

Explicit .js extensions in ES module imports prevent runtime resolution surprises. This style guide enforces an ESM-first layout with explicit extensions to ensure consistent module loading and navigation in TypeScript projects.

What is the best way to organize TypeScript imports and modules?

Organize TypeScript imports by enforcing consistent import order, explicit extensions, and minimized re-exports. The style guide favors single-responsibility files and avoids barrel files to improve tree-shaking and navigation.

Does this TypeScript style guide work with Node 22 LTS?

Yes, this TypeScript style guide is designed for TS 5.9+ codebases running on Node 22 LTS. It imposes specific rules for ES module usage and strong typing conventions suited for this environment.

When should I avoid using barrel files in a TypeScript codebase?

Avoid barrel files in TypeScript codebases to improve tree-shaking and module navigation. This style guide favors single-responsibility files with one concept per file and minimized re-exports over centralized barrel exports.

What naming conventions should I apply for TypeScript types and constants?

Apply PascalCase for types and classes, camelCase for values and functions, and UPPER_SNAKE for module constants. These naming conventions keep TypeScript code cohesive and readable across large projects.