The final result is a function of the initial conditions and the decisions made along the way.
npx skills add https://github.com/ncaq/konoka --skill file-naming-ncaq
Please help me install this Agent Skill. Skill: file-naming Source: https://github.com/ncaq/konoka/tree/main/plugins/web-tasuke/skills/file-naming Command: npx skills add https://github.com/ncaq/konoka --skill file-naming-ncaq
Inconsistent file and directory naming in TypeScript and JavaScript projects creates confusion, slows onboarding, and hinders maintainability.
Start by applying kebab-case for new files and directories, use PascalCase for exported React component filenames when appropriate, and adopt camelCase for hooks to align with common patterns.
High-intent search queries and answers about installing and using this skill.
The best way to enforce consistent file naming is to apply kebab-case for files and directories by default, while using PascalCase for exported React component filenames and camelCase for hooks to align with common JavaScript conventions.
React component filenames should use PascalCase for exported components to match the component name, while kebab-case should be kept for other files to maintain consistency across the project structure and reduce case-related issues across platforms.
To name React hooks files in a JavaScript project, use camelCase to align with common JavaScript conventions, while allowing for project-specific variations if existing codebases require a different approach.
Yes, you can apply kebab-case to existing directories by adopting a straightforward baseline and gradually harmonizing the project structure, which accommodates existing conventions while reducing case-related issues across platforms.
Inconsistent file naming in JavaScript projects slows onboarding and hinders maintainability because varying cases across files and directories create confusion, making it difficult for new developers to locate modules and understand project structure.
danghungtb26Enforce naming and folder structure conventions for React TypeScript admin templates.
benediktmsCheck code against project linter conventions for naming, formatting, and structure.
riftzen-bitEnforce universal coding standards across TypeScript and JavaScript projects.
leaderiopStandardize package port declarations and mappings in project configurations.
