hotfixlisted

Follow CLAUDE.md rules for Clean Architecture. ## Ultra Think Strategy Ultra think before each phase transition: - After clarification: ensure you fully understand the issue - After exploration results: reflect on completeness before analyzing - Before implementation: consider edge cases, patterns to follow, potential issues - After validation: ensure the fix addresses root cause, not symptoms --- ## 1. PARSE ISSUE From: `$ARGUMENTS` Extract: - **Feature area**: Which part of the app? - **Bug type**: Logic error, UI, data, performance, error handling? - **Layers**: Backend / Frontend / Both / Database? - **Database env**: Detect from description (prod/dev) - default to DEV --- ## 2. CLARIFY ISSUE Use AskUserQuestion to clarify before exploration: ### Bug context (if not specified) - Can you reproduce the bug? Steps to reproduce? - What is the expected vs actual behavior? - When did it start happening? (recent deploy, config change?) - Are there error logs or screenshots available? ### Impact & Priority (if not specified) - Is this blocking production? - Who/what is affected? - Is there a temporary workaround in place? ### Scope (if not specified) - Should we fix root cause or apply quick workaround first? - Are there related issues to address at the same time? - Environment affected: dev, staging, prod? Do not proceed until the issue is fully understood. --- ## 3. EXPLORE (PARALLEL) Launch agents based on issue scope (single message, parallel execution): | Ne