check-boundaries

Review the component tree in $ARGUMENTS for incorrect or unnecessary 'use client' directives.

For each component file found:

1. Check if 'use client' is present

2. If yes, verify it is actually required by checking whether the component uses:

   • Browser APIs (window, document, localStorage, sessionStorage)
   • Event handlers that require client state (onClick with useState, onChange with controlled inputs)
   • React hooks that depend on client state: useState, useEffect, useReducer, useRef for DOM manipulation
   • Client-only third-party libraries

3. Flag as INCORRECTLY CLIENTED if 'use client' is present but the component:

   • Only renders JSX with no interactivity
   • Only passes props down to child components
   • Does data fetching that could be done in a Server Component
   • Has 'use client' because a child needed it (the child should have it, not the parent)

4. For each incorrectly cliented component, suggest the fix:

   • If the component itself needs no client features: remove 'use client', make it a Server Component
   • If only a small part needs client features: identify which piece to extract as a separate Client Component

5. Check for the anti-pattern where a large Server Component was converted to a Client Component just to pass an event handler — suggest extracting the interactive element instead.

6. In Client Components that receive params or searchParams props, check that they are unwrapped with use() from React, not accessed directly:

   • const { slug } = use(params) ✅
   • const { slug } = params ❌ (params is a Promise in Next.js 15)
   • Flag any Client Component that destructures params/searchParams without use() or await

Output format:

• List each component with its status: ✅ CORRECT, ⚠️ UNNECESSARY 'use client', or ❌ MISSING REQUIRED 'use client'
• For each issue, show the specific lines causing the classification
• Provide a concrete refactor suggestion for each problem found
• End with a summary: X components reviewed, Y issues found, estimated server-rendering improvement

If no path is provided in $ARGUMENTS, analyze all components in the current directory and subdirectories.