file-naming

file-naming is a skill for Claude Code from ncaq/konoka. It costs 25 tokens per session (720 once invoked), scanned A, original, Apache-2.0.

A naming guide for files and folders in TypeScript and JavaScript projects. It recommends kebab-case, with documented exceptions for React components and custom hooks.

In plain words
What is it for?
Use it when creating files or directories, especially modules, React component files, and custom hook files.
Why use it?
It prevents inconsistent names and avoids case-related problems between operating systems such as Windows and macOS.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the web-tasuke plugin — 17 skills shipped together

Good fit Use it when creating files or directories, especially modules, React component files, and custom hook files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ncaq/konoka/file-naming
View source ↗ ncaq/konoka
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ncaq/konoka --skill file-naming
Clone the repo
git clone --depth 1 https://github.com/ncaq/konoka

Made for: Claude Code.

Or install web-tasuke, the plugin that ships this one along with the rest of its 17 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for file-naming

README.md
[![agentmods](https://agentmods.dev/badge/skills/ncaq/konoka/file-naming/github.svg)](https://agentmods.dev/skills/ncaq/konoka/file-naming)
Your own site
<a href="https://agentmods.dev/skills/ncaq/konoka/file-naming"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/file-naming/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for file-naming

Your own site · 80×15
<a href="https://agentmods.dev/skills/ncaq/konoka/file-naming"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/file-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 720 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00720
Opus 5 $0.00013 $0.00360
Sonnet 5 $0.00005 $0.00144
Haiku 4.5 $0.00003 $0.00072

Measured 3d ago against content hash c26c151be3f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

file-naming scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/web-tasuke/skills/file-naming/SKILL.md · 86 lines

What it actually says

ファイル名とディレクトリ名の規約

基本ルール

ディレクトリ名やファイル名はkebab-caseを使います。

src/
  api/
    customer-query.ts

kebab-caseを基本とする理由は以下の通りです。

URLやnpmパッケージ名などweb標準のエコシステムではkebab-caseが一般的です。 それに従ってTypeScript/JavaScriptのプロジェクトでもkebab-caseが広く採用されています。

ファイルシステムの大文字小文字の扱いがOS間で異なります。 macOSやWindowsはデフォルトでcase-insensitiveなので、 UserList.tsxuserList.tsxを区別できません。 kebab-caseならこの問題が発生しません。

Reactコンポーネントファイル

Reactコンポーネントをエクスポートするファイルは、 同じ名前のPascalCaseを使っても構いません。

メインの利用目的と一致しているため、 対応関係が分かりやすくなります。

React公式もチュートリアルでそのような名前を使うこともあります。

src/
  components/
    SearchDialog.tsx    # SearchDialogコンポーネントをエクスポート
    UserList.tsx        # UserListコンポーネントをエクスポート

しかし全てをkebab-caseに統一するのも問題ありません。

ReactのカスタムHooksファイル

単一のReactのカスタムHooksをexportするファイルは、 同じ名前のcamelCaseを使っても構いません。

関数名とファイル名が一致するため、 対応関係が分かりやすくなります。

React公式もチュートリアルで使っています。

eslint-plugin-react-hooksはファイル名ではなく関数名のuseプレフィックスでHooksを検出するので、 ファイル名は自由ですが、 一致させた方がわかりやすいでしょう。

src/
  hooks/
    useAuth.ts          # useAuth関数をエクスポート
    useLocalStorage.ts  # useLocalStorage関数をエクスポート

しかし全てをkebab-caseに統一するのも問題ありません。

通常のTypeScript/JavaScriptモジュール

kebab-caseを使うことを推奨します。

単一のexportのモジュールでも、 のちのち複数のexportが発生する可能性が割とあるので、 kebab-caseを使うことを推奨します。

プロジェクト内での一貫性

プロジェクト内で既に採用されている規約がある場合はそちらに従ってください。

プロジェクト内で混在している場合は、 新規ファイルでは一貫した命名規則を採用して、 既存ファイルは変更のついでに徐々に統一していくのが現実的です。

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 86 lines · 25 tokens per session scan A c26c151be3f9

Subscribe to this mod's changes

file-naming is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 720 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

Related

Other skills, from other repositories

bun-bundler

This skill should be used when the user asks about "bun build", "Bun.build", "bundling with Bun", "code splitting", "tree shaking", "minification", "sourcemaps", "bundle optimization", "esbuild alternative", "building for production", "bundling TypeScript", "bundling for browser", "bundling for Node", or…

secondsky/claude-skills · 90 tokens

frontend-ai-guide

Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.

shinpr/claude-code-workflows · 41 tokens

better-auth

Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.

secondsky/claude-skills · 53 tokens

typescript-rules

React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

shinpr/claude-code-workflows · 39 tokens

bun-hot-reloading

Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.

secondsky/claude-skills · 42 tokens

tanstack-form-composition

Migrate a React @tanstack/react-form codebase from the prop-drilled useForm + erased-form-type pattern to the official createFormHook composition API (useAppForm / withForm / field.X). Use when a project threads a form object (often cast to an any-erased type like ReactFormExtendedApi ) through field-wrapper…

suxrobGM/jobpilot · 158 tokens