pattern-recognitionlisted

# Pattern Recognition Skill Standards for identifying and applying existing codebase patterns to maintain consistency. ## When to Apply - Before writing new code - When implementing similar features - Code review for pattern consistency - Refactoring decisions --- ## Pattern Detection Process ### Step 1: Scan Existing Code | Action | Purpose | |--------|---------| | Find similar modules/components | Match structure and naming | | Find similar functions/hooks | Match return types and patterns | | Find similar services | Match error handling and API patterns | | Check shared-types location | Match how the project centralizes types | ### Step 2: Extract Patterns | Element | What to Look For | |---------|------------------| | Module/component structure | Imports, signature, body order | | State management | Local-vs-shared state decisions | | Error handling | Try/catch style, error messages | | Naming conventions | Files, functions, types | | File organization | Directory structure | ### Step 3: Apply Consistently | Rule | Description | |------|-------------| | Match existing style | New code follows established patterns | | Document deviations | If pattern changes, document why | | Refactor if needed | Update old code to match new pattern | --- ## Example: React + TypeScript conventions (illustrative) > Illustrative — the naming, component, hook, service, and type conventions below > are one team's React/TypeScript catalog shown as a concrete example. The > reusable s