How are custom components handled compared to UI libraries?

The skill differentiates between shadcn/ui components (kebab-case) and custom project components (PascalCase) to align with industry best practices.

Can this skill help with file organization?

Absolutely. By enforcing suffixes like .service.ts and .schema.ts, it helps organize files by their logical role within the application architecture.

What does this skill define as the Single Source of Truth?

This skill acts as the absolute reference point for all naming decisions, overriding general documentation to ensure Claude maintains strict consistency across the project.

Does it support specific frameworks like Next.js?

Yes, it includes predefined naming rules for Next.js core files such as page.tsx, layout.tsx, and route.ts to prevent accidental renaming.

What casing is used for code-level variables?

It mandates PascalCase for types and classes, camelCase for functions and variables, and UPPER_SNAKE_CASE for global constants.

Project Naming Standards

Name: Project Naming Standards
Author: shoma-endo

byshoma-endo

開発者ツール

Standardizes project-wide naming conventions across directories, files, and code structures to ensure a consistent and organized codebase.

概要

The Project Naming Standards skill establishes a Single Source of Truth (SSoT) for all naming conventions within a repository. It provides comprehensive guidelines for directory structures using kebab-case, specialized file naming patterns for Next.js and shadcn/ui, and logical suffixing for hooks, services, and actions. By centralizing these rules, the skill eliminates naming ambiguity, streamlines team collaboration, and ensures that every file and variable adheres to a professional, predictable architecture.

主な機能

Tailored naming rules for Next.js system files and UI components
Domain-specific suffix patterns for hooks, services, and schemas
Standardized casing for React components, types, and variables
Automated SSoT synchronization for project-wide consistency
0 GitHub stars
Strict kebab-case enforcement for all directory names

ユースケース

Establishing a uniform folder structure for new Next.js or React projects
Standardizing naming patterns during large-scale code refactors
Onboarding new developers to ensure immediate adherence to team coding standards

概要

主な機能

Tailored naming rules for Next.js system files and UI components
Domain-specific suffix patterns for hooks, services, and schemas
Standardized casing for React components, types, and variables
Automated SSoT synchronization for project-wide consistency
0 GitHub stars
Strict kebab-case enforcement for all directory names

ユースケース

Establishing a uniform folder structure for new Next.js or React projects
Standardizing naming patterns during large-scale code refactors
Onboarding new developers to ensure immediate adherence to team coding standards