What problem does it solve?
This skill centralizes patterns and practical fixes for the browser layer of web apps so engineers can quickly build, debug, and refactor React/Next.js/TypeScript/Tailwind user interfaces without repeatedly re-explaining project conventions or making the wrong server/client tradeoffs.
Core Features & Use Cases
- Server-first boundaries: Prefer Server Components and add client-only code only where interactivity or browser APIs are required.
- Debugging rendering & styling: Diagnose hydration mismatches, Tailwind class purge issues, layout shifts, CSS specificity problems, and unstable key bugs.
- Refactor & architecture: Split Server vs Client Components, colocate types/hooks, follow file naming conventions, and optimize bundle size and data fetching (cache controls).
- Real-world example: Fix a page that SSRs correctly but hydrates with missing Tailwind classes and a broken form by extracting the interactive form into a client component, safelisting classes, and applying no-store where fresh data is required.
Quick Start
Start by locating the feature boundary, prefer a Server Component, extract only the interactive leaf into a client component, and apply the project's colocation and naming conventions to implement or fix the UI.