From d0bcee6cc42c2699f2ea2838f1beb3f2c68fbf16 Mon Sep 17 00:00:00 2001 From: lzy Date: Tue, 29 Sep 2026 18:03:57 +0800 Subject: [PATCH] docs: clarify server-specific tool naming --- CLAUDE.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index ad30b915a8..9c6369dfb0 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -65,8 +65,12 @@ uv run ruff check . - Zod schemas for tool input validation - 2-space indentation, trailing commas in multi-line objects - camelCase for variables/functions, PascalCase for types/classes, UPPER_CASE for constants -- kebab-case for file names and registered tools/prompts/resources -- Verb-first tool names (e.g., `get-file-info`, not `file-info`) +- kebab-case for file names; for registered tools, prompts, and resources, follow + the existing public convention of the server you are changing (for example, + snake_case in `filesystem` and `memory`, kebab-case in `everything`) +- Never rename a published tool, prompt, or resource only to change its casing +- Prefer verb-first tool names in the server's existing style (for example, + `get_file_info` in `filesystem` or `get-annotated-message` in `everything`) - Imports grouped: external first, then internal ### Python