Claude Code Naming Conventions FAQs

Question 1

Are plugin names considered API contracts?

Accepted Answer

Yes, once published, renaming plugins or skills is a semver-major change because it affects slash-command invocations, agent permissions, and marketplace references.

Question 2

What is 'namespace stuttering' in Claude Code?

Accepted Answer

Stuttering occurs when the plugin name is repeated in the component name (e.g., cortex:cortex-research). These conventions enforce dropping the prefix to maintain clean, typable /slash-commands.

Question 3

What are the tier prefixes like kb- and dx- used for?

Accepted Answer

Prefixes signal the plugin's purpose: kb- is for Knowledge Banks, dx- for Developer Experience tools, and int- for external service Integrations, helping organize the marketplace and local environments.

Question 4

How do naming conventions affect the Claude context budget?

Accepted Answer

Clear, non-redundant names and descriptions reduce token usage while ensuring Claude accurately routes tasks to the correct tool without needing excessive context overhead.

Question 5

Why does the part of speech matter for skill names?

Accepted Answer

Consistency creates a predictable mental model; commands and action skills should use imperative verbs (e.g., /deploy) while knowledge skills use nouns to help users and the AI differentiate between actions and information.

Claude Code Naming Conventions

Key Features

Use Cases

Claude Code Naming Conventions

Key Features

Use Cases