naming-analyzer

Topics in the source

• Naming Analyzer Skill
• Instructions
• Naming Conventions by Language
• JavaScript/TypeScript
• Python
• Java
• Go
• Common Naming Issues

Suggest better variable, function, and class names based on context and conventions. 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 Variables/functions: camelCase Classes/interfaces: PascalCase Constants: UPPERSNAKECASE Private fields: prefixUnderscore or #privateField Boolean: is, has, can, should prefixes Variables/functions: snakecase Classes: PascalCase Constants: UPPERSNAKECASE Private: prefixunderscore Boolean: is, has, can prefixes Variables/methods: camelCase Cl

This is an excerpt. Refer to the complete source and its current requirements.