ts-type-naming

Enforce TypeScript interface and type naming conventions with file-location rules.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/lonewolfyx/skills --skill ts-type-naming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ts-type-naming
Source: https://github.com/lonewolfyx/skills/tree/main/skills/ts-type-naming
Command: npx skills add https://github.com/lonewolfyx/skills --skill ts-type-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript interfaces must use an I prefix and PascalCase, while type aliases use camelCase; this skill enforces those conventions and centralizes type declarations to maintain consistency across the codebase.

Core Features & Use Cases

  • Enforces interface naming patterns: I + PascalCase (e.g., IUserInfo, IApiConfig) and type naming: camelCase (e.g., userInfo, apiResponse).
  • Validates file locations for type declarations in general TS projects (root types.ts) or Nuxt projects (shared/types/types.ts), and reports deviations.
  • Suggests or automatically moves/renames declarations to compliant type files and updates references.

Quick Start

Run the TypeScript type naming checker on your repository to identify interface/type naming violations and apply fixes to align them with the rules.

Frequently Asked Questions about ts-type-naming

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

FAQPage Schema
How do I enforce TypeScript interface and type naming conventions in my codebase?

To enforce TypeScript naming conventions, you validate that interfaces use an I prefix with PascalCase and types use camelCase. This identifies declaration violations and applies fixes to rename non-compliant types across the codebase.

How do I centralize TypeScript type definitions in a Nuxt project?

To centralize TypeScript type definitions in a Nuxt project, you validate type declaration file locations against shared/types/types.ts. This reports file location deviations and suggests moving declarations to the compliant target file.

What is the correct naming pattern for TypeScript interfaces and type aliases?

The correct naming pattern for TypeScript interfaces is an I prefix with PascalCase, while type aliases should use camelCase. This convention maintains consistency across type declarations and clarifies declaration types.

Does this TypeScript naming checker support general TS projects or only Nuxt?

This TypeScript naming checker supports both general TS projects and Nuxt projects. It validates file locations for type declarations against root types.ts or Nuxt shared/types/types.ts respectively.

How do I automatically update references when renaming TypeScript types?

To automatically update references when renaming TypeScript types, you run the checker to identify violations and apply fixes. This moves or renames declarations to compliant files and updates all related references.