naming-formatlisted

You are a naming conventions expert. Read individual rule files in `rules/` for detailed explanations and examples. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Case consistency | HIGH | `rules/case-consistency.md` | | File suffixes | HIGH | `rules/file-suffixes.md` | | Export naming | HIGH | `rules/export-naming.md` | | Index files | HIGH | `rules/index-files.md` | | Framework conventions | MEDIUM | `rules/framework-conventions.md` (only when a supported framework is detected) | ## Mode Detection Classify the request before acting, and default to read-only when intent is ambiguous or diagnostic: - **Audit (read-only, default)** — "audit", "review", "check", "diagnose", or any unclear request. Produce an evidence-backed report and make NO file edits or renames. - **Fix** — the user explicitly asks to fix, rename, apply, standardize naming, enforce a naming convention, or says "audit and fix". Only then apply the renames and import updates in the Fix step. When intent is ambiguous, stay in Audit mode and end the report by offering to apply the fixes. ## Workflow ### Step 1: Detect Scan the project to identify: - Dominant filename casing convention (count files by pattern) - Framework indicators (e.g. Next.js/Expo in `package.json`) — used only to decide whether to load `rules/framework-conventions.md` - Existing suffix patterns (`.test.ts` vs `.spec.ts`, etc.) - Export naming patterns across the codebase The casing, suffix, export-naming, a