typescript-conventions

Enforce TypeScript conventions and fix pnpm monorepo module resolution errors.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/eric-sabe/engsys --skill typescript-conventions-eric-sabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-conventions
Source: https://github.com/eric-sabe/engsys/tree/main/stacks/lang/typescript/skills/typescript-conventions
Command: npx skills add https://github.com/eric-sabe/engsys --skill typescript-conventions-eric-sabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent TypeScript code, common pnpm monorepo module resolution errors, and non-compliant patterns that cause build failures or runtime bugs in TS 5.x projects targeting Node 22.

Core Features & Use Cases

  • Standardized Naming & Style: Enforces kebab-case filenames, PascalCase for classes/interfaces/type aliases, and no unnecessary I prefixes for consistent, readable codebases.
  • Type System & Architecture Guardrails: Prevents any usage, promotes discriminated unions, and ensures decoupled module design to reduce technical debt.
  • Monorepo & Build Fixes: Resolves common pnpm workspace gotchas like @smithy/* hoisting for AWS SDK v3 and missing DOM lib configuration for fetch APIs, eliminating avoidable type errors.
  • Use Case: When contributing a new TypeScript service to a pnpm monorepo, use this Skill to ensure your code follows project conventions, passes type checking, and avoids common module resolution pitfalls.

Quick Start

Apply the typescript-conventions skill to review your new user-service.ts file for compliance with project naming, type, and pnpm monorepo standards.

Frequently Asked Questions about typescript-conventions

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

FAQPage Schema
How do I fix pnpm monorepo module resolution errors in TypeScript?

To fix pnpm monorepo module resolution errors in TypeScript, you must resolve common workspace gotchas like @smithy/* hoisting for AWS SDK v3 and configure missing DOM lib for fetch APIs. This eliminates avoidable type errors during your build process.

What are the best TypeScript naming conventions for a large codebase?

Standardized TypeScript naming conventions for a large codebase require kebab-case filenames, PascalCase for classes, interfaces, and type aliases, and avoiding unnecessary I prefixes. This ensures a consistent and readable codebase across all workspace packages.

How do I configure TypeScript for Node 22 and ES2022 targets?

Configuring TypeScript for Node 22 and ES2022 targets involves applying type system best practices, preventing any usage, and promoting discriminated unions. This reduces technical debt and satisfies requirements for standardized secure coding standards.

Why does my AWS SDK v3 build fail type checking in a pnpm workspace?

AWS SDK v3 build type checking fails in a pnpm workspace due to unresolved @smithy/* package hoisting issues. Correcting the DOM lib configuration for fetch APIs and fixing module hoisting eliminates these avoidable TypeScript type errors.

Can I use this Skill to review existing TypeScript files for compliance?

Yes, you can use this Skill to review existing .ts files across all pnpm workspace packages for compliance. It evaluates code writing, type checking, and build configuration against secure coding standards and async error handling patterns.

What type system best practices should I use to reduce TypeScript technical debt?

To reduce TypeScript technical debt, you should prevent any usage, promote discriminated unions, and ensure decoupled module design. Applying these type system guardrails prevents non-compliant patterns that cause build failures or runtime bugs.