pattern-analysislisted

# Pattern Analysis ## Purpose Audit the codebase for existing patterns and conventions, then evaluate proposed changes for consistency. ## Scope Constraints - Covers file naming, directory structure, component patterns, data fetching, state management, error handling, and type conventions. - Does not cover test strategy design or coverage targets — hand off to testing-strategy. - Does not cover high-level architectural decisions or system decomposition — hand off to architect department. ## Inputs - Codebase or directory to audit - Proposed changes or new code to evaluate (if applicable) - Specific concerns or areas of focus (if any) - Known tech stack and framework conventions ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Step 1: Scan Structural Patterns - **File naming conventions:** - kebab-case, PascalCase, camelCase, snake_case - Suffix conventions (.utils.ts, .types.ts, .test.ts, .stories.tsx) - **Directory organization:** - Feature-based (feature/components, feature/hooks, feature/utils) - Layer-based (components/, hooks/, utils/, types/) - Hybrid approaches - **Module export patterns:** - Barrel files (index.ts re-exports) - Direct imports - Default vs named exports ### Step 2: Identify Code Patterns - **Component patterns:** - Server vs client components (React Server Components) - Composition patterns (render props, compound com