Intelligent Naming Advisor

Problem

Naming variables, functions, classes, projects, or products is less about finding a word and more about judgment: Does the name carry the right meaning? Does it match the language convention? Is it readable? Is it ambiguous? Prompting “name this” without context often yields generic results like foo, temp1, or dataHelper, with little sense of the actual domain or constraints.

How It Works

namer extracts five elements from the request: naming target, core semantics, usage context, constraints, and naming convention. If fewer than three elements are available, it asks for clarification instead of guessing. It then selects a style based on the context, for example:
- JavaScript/TypeScript: camelCase, PascalCase
- Python / Go / Rust: snake_case or camelCase
- Projects, APIs, and paths: kebab-case, snake_case, or short word combinations

Each suggestion includes the name, style, reasoning, and best-fit context, so the output is not just a string.

Boundaries

It is a naming assistant, not a safe renaming tool, trademark search service, or legal compliance checker. It prefers English by default, avoids meaningless names and nonstandard abbreviations, and still leaves reserved-word conflicts, sensitive terms, and trademark risk to human review.