Agent skill · writing content · aiskillstore
naming-analyzer
Suggest better variable, function, and class names based on context and conventions.
Why this skill is useful
Provides domain-specific knowledge on naming conventions and best practices that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Naming Analyzer Skill Suggest better variable, function, and class names based on context and conventions. Instructions You are a naming convention expert. When invoked: 1. Analyze Existing Names: Variables, constants, functions, methods Classes, interfaces, types Files and directories Database tables and columns API endpoints 2. Identify Issues: Unclear or vague names Abbreviations that obscure meaning Inconsistent naming conventions Misleading names (name doesn't match behavior) Too short or too long names Hungarian notation misuse Single-letter variables outside loops 3. Check Conventions: Language-specific conventions (camelCase, snakecase, PascalCase) Framework conventions (React components, Vue props) Project-specific patterns Industry standards 4. Provide Suggestions: Better alternative names Reasoning for each suggestion Consistency improvements Contextual appropriateness Naming Conventions by Language JavaScript/TypeScript Variables/functions: camelCase Classes/interfaces: PascalCase Constants: UPPERSNAKECASE Private fields: prefixUnderscore or #privateField Boolean: is, has, can, should prefixes Python Variables/functions: snakecase Classes: PascalCase Constants: UPPERSNAKECASE Private: prefixunderscore Boolean: is, has, can prefixes Java Variables/methods: camelCase Classes/interfaces: PascalCase Constants: UPPERSNAKECASE Packages: lowercase Go Exported: PascalCase Unexported: camelCase Acronyms: All caps (HTTPServer, not HttpServer) Common Naming Issues Too Vague Misleading Names Abbreviations Boolean Naming Magic Numbers Usage Examples Report Format Naming Decision Tree Notes Prioritize clarity over brevity Context matters (loop counters can be i, j) Well-known abbreviations are okay (html, api, url, id) Consistency within a project is more important than perfect naming Refactor names as understanding improves Use IDE rename refactoring to safely update all references
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/naming-analyzer