Code Naming Conventions

Operational naming rules for agentic coding assistants. Apply them as decision rules when generating, reviewing, or renaming identifiers.

Prefer the project's casing and established domain vocabulary, but do not copy semantically wrong names. Read CONVENTIONS.md only when examples or nuance are needed.

Basics

• Use English.
• Follow the language/project casing convention.
• Treat accepted acronyms/domain abbreviations as normal words: userId, apiUrl, httpClient, UserDto.
• Avoid ad hoc contractions and unclear abbreviations: use buttonText, not btnTxt.
• Make names short, intuitive, and descriptive.
• Avoid duplicated context: inside MenuItem, use handleClick, not handleMenuItemClick.
• Name values by how they are consumed: prefer isDisabled for <Button disabled={isDisabled} />.

Variables