file-name-wizardlisted

# Filename & Naming Convention Audit ## Instructions Perform systematic audit of all filenames and naming conventions in the codebase to identify inconsistencies, anti-patterns, and violations of naming standards. ### Phase 1: Discovery & Standard Extraction #### Step 1: Find All Files Use Glob to identify all files in the codebase: - Source files (`.ts`, `.tsx`, `.js`, `.jsx`, etc.) - Config files - Documentation files - Test files Create comprehensive todo list of all files to audit. #### Step 2: Extract Naming Standards Read all `CLAUDE.md` files in the repository: - Root `CLAUDE.md` if exists - Directory-specific `CLAUDE.md` files Extract naming conventions: - File naming patterns (kebab-case, PascalCase, etc.) - Directory structure rules - Component naming rules - Utility/helper naming rules - Test file naming rules - Config file naming rules - Constant/enum file naming rules #### Step 3: Identify Implicit Patterns Even without explicit CLAUDE.md rules, identify patterns: - Most common naming convention in each directory - Grouping patterns (e.g., `*.service.ts`, `*.controller.ts`) - Organizational patterns (e.g., `components/`, `utils/`, `lib/`) ### Phase 2: Systematic File Audit For EACH file in the todo list: #### Step 1: Analyze Filename - What is the current filename? - What naming convention does it use? - Is it descriptive and clear? - Does it match its purpose/content? #### Step 2: Check Against Standards Compare to: - Explicit CLAUDE.md rules for