skills.rest
TechyMT
TechyMTCOMMUNITY
Explore all skills by this author →
Website𝕏@techymtGitHub

naming-conventions

Enforces naming conventions for files and identifiers in TypeScript and React projects.

5|Updated Apr 1, 2026
Search Tags:#typescript#conventions#tools#naming#constants#code-style#react-hooks
One-click install
npx skills add https://github.com/TechyMT/claude-code-superpowers --skill naming-conventions-techymt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming-conventions
Source: https://github.com/TechyMT/claude-code-superpowers/tree/main/skills/naming-conventions
Command: npx skills add https://github.com/TechyMT/claude-code-superpowers --skill naming-conventions-techymt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large codebases become hard to navigate when files and identifiers are named inconsistently, causing contributors to waste time locating implementations and understanding intent. This Skill codifies naming rules that let readers infer a file or symbol's role without opening it, improving discoverability and onboarding.

Core Features & Use Cases

  • Guides file naming for Tools, commands, hooks, components, utilities, and types so filenames convey role and UI responsibilities.
  • Defines identifier styles: PascalCase for types and classes, camelCase verbs for functions, is/has prefixes for booleans, on[Event] for callbacks, UPPER_SNAKE_CASE for constants, and kebab-case for command directories.
  • Use it when adding a new Tool, renaming utilities to match project conventions, or reviewing pull requests to enforce a predictable naming surface.

Quick Start

Use the naming-conventions guidance to rename new and existing files and identifiers so they follow Tool suffixes, PascalCase types, camelCase verbs, is/has booleans, on-prefixed callbacks, and UPPER_SNAKE_CASE constants.

Frequently Asked Questions about naming-conventions

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

FAQPage Schema
What naming conventions should I use for TypeScript and React files?▼

File naming conventions for TypeScript and React projects require filenames to convey their role, using specific suffixes for Tools, commands, hooks, components, utilities, and type definitions to improve codebase discoverability and maintainability.

How do I name React hooks and callbacks consistently?▼

To name React hooks and callbacks consistently, apply camelCase verbs for hook functions and use the on[Event] prefix for callback props to clearly signal event handling behavior across your UI components.

Can I use these code style rules to review pull requests?▼

Yes, you can use these code style rules to review pull requests by checking new and renamed files against the required Tool suffixes, PascalCase types, camelCase verbs, is/has booleans, and UPPER_SNAKE_CASE constants for a predictable naming surface.

When do I need UPPER_SNAKE_CASE and is/has prefixes in TypeScript?▼

You need UPPER_SNAKE_CASE for defining constants and is/has prefixes for boolean variables in TypeScript when you want filenames and identifiers to convey their role and type without needing to open the file.

Why does inconsistent file naming make codebases hard to navigate?▼

Inconsistent file naming makes codebases hard to navigate because contributors waste time locating implementations and understanding intent, whereas codified naming rules let readers infer a file or symbol's role immediately.

Related Skills

Explore More Software Engineering Skills→
carson-sweetcarson-sweet
6

SweetClaude Setup

Detect project type and initialize standardized directory structures and configuration files.

Community
Advanced
matteocervellimatteocervelli
25

python-quality-checker

Validate Python code formatting, typing, linting, and security issues.

Community
Advanced
ncaqncaq
3

file-naming

The final result is a function of the initial conditions and the decisions made along the way.

Community
Intermediate
ysyecustysyecust
40

coding-standards

Enforce universal coding standards across TypeScript, JavaScript, React, and Node.js projects.

Community
Basic