What problem does it solve? Frontend developers often make inconsistent architectural decisions when designing React components, choosing state management tools, and structuring Next.js projects, leading to unmaintainable codebases and performance issues. ## Core Features & Use Cases - Component Design Patterns: Reference for compound components, custom hooks, container/presentational separation, and headless components with clear guidance on when to apply each. - State Management Selection Guide: Decision flow and comparison table covering useState, React Query, Zustand, nuqs, React Hook Form, and Context for different state types. - Quality Standards & Checklists: Concrete rules for component size, props limits, error boundaries, performance patterns, accessibility, and common anti-pattern red flags. - Use Case: When building a Next.js dashboard, consult this reference to decide between React Query and Zustand for server state, structure the app directory with route groups, and verify components against the accessibility checklist. ## Quick Start Ask the expert-frontend agent to review your React component architecture and recommend the appropriate state management approach for your Next.js project.
