How does it handle boolean variables?

The skill encourages semantic prefixes such as 'is', 'has', 'can', 'should', 'will', and 'did' to make boolean logic more descriptive.

Which naming conventions does this skill follow?

It follows industry standards: camelCase for variables/functions, PascalCase for classes/types, UPPER_SNAKE for constants, and kebab-case for filenames.

When should I trigger this skill?

You can trigger it when writing new code, reviewing existing naming patterns, or specifically asking about naming conventions in your project.

Does it support common programming abbreviations?

Yes, it includes a whitelist of common abbreviations like 'ctx' for Context and 'req/res' for Request/Response, while discouraging ambiguous single-letter variables.

TypeScript Naming Standards

Name: TypeScript Naming Standards
Author: 15195999826

by15195999826

Herramientas para Desarrolladores

Enforces consistent TypeScript naming conventions for variables, types, and files to ensure clean and maintainable codebases.

Acerca de

The TypeScript Naming Standards skill helps developers maintain high code quality by applying industry-standard naming patterns across projects. It provides instant guidance on appropriate case styles such as camelCase for variables, PascalCase for types, and kebab-case for files. By integrating semantic boolean prefixing and specific constant declaration rules, this skill ensures that your code remains readable and professional, making it an essential tool during both initial development and the code review process.

Características Principales

Distinguishes between compile-time constants and runtime calculations
0 GitHub stars
Enforces PascalCase for classes, interfaces, and types
Guides kebab-case naming for TypeScript files and directories
Standardizes camelCase for variables and function names
Provides semantic boolean prefixing (is, has, can, should)

Casos de Uso

Establishing a unified style guide for a new TypeScript project
Providing automated naming suggestions during the code review process
Refactoring legacy codebases to improve readability and consistency

Acerca de

Características Principales

Distinguishes between compile-time constants and runtime calculations
0 GitHub stars
Enforces PascalCase for classes, interfaces, and types
Guides kebab-case naming for TypeScript files and directories
Standardizes camelCase for variables and function names
Provides semantic boolean prefixing (is, has, can, should)

Casos de Uso

Establishing a unified style guide for a new TypeScript project
Providing automated naming suggestions during the code review process
Refactoring legacy codebases to improve readability and consistency