Suggest better variable, function, and class names based on context and conventions.

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, snake case, 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: UPPER SNAKE CASE Private fields: prefixUnderscore or privateField Boolean: is , has , can , should prefixes Python Variables/functions: snake case Classes: PascalCase Constants: UPPER SNAKE CASE Private: prefix underscore Boolean: is , has , can prefixes Java Variables/methods: camelCase Classes/interfaces: PascalCase Constants: UPPER SNAKE CASE 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

naming-analyzer