frontend-ai-guide

# AI Developer Guide - Technical Decision Criteria and Anti-pattern Collection (Frontend) ## Value-First Engineering Explore broadly, then converge on the lowest-lifecycle-cost solution that delivers the required user value while keeping the UI correct and maintainable. - Resolve verified problems within confirmed scope or dependencies required for the outcome; report other findings with evidence for a scope decision. - Introduce state, props, variants, abstractions, or speculative edge-case handling when a current outcome, verified constraint, or evidence-backed material risk requires them. ## Technical Anti-patterns (Red Flag Patterns) Pause the affected decision and review the design when detecting the following patterns: ### Code Quality Anti-patterns 1. **Writing similar code 3 or more times** - Violates Rule of Three 2. **Multiple responsibilities mixed in a single component** - Violates Single Responsibility Principle (SRP) 3. **Defining same content in multiple components** - Violates DRY principle 4. **Making changes without checking dependencies** - Potential for unexpected impacts 5. **Disabling code with comments** - Should use version control 6. **Error suppression** - Hiding problems creates technical debt 7. **Excessive use of type assertions (as)** - Abandoning type safety 8. **Prop drilling through 3+ levels** - Mandatory ownership review. Use composition, Context, or the project's state layer when intermediate components only forward the value; retain e...