Menú
Use when: diagnosing Next.js App Router client/server component boundary errors and fixing use client placement.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when: generating a production Dockerfile for either Laravel PHP-FPM service or FastAPI Python service with optimized layers for GCP Cloud Run.
Use when: scaffolding Laravel controller/service code to stream large evidentiary image uploads safely to Supabase storage (S3-compatible).
Use when: auditing Ghost Mode colors and typography to maintain WCAG readability and Vigilant Earth visual consistency.
Use when: diagnosing broken Flexbox or CSS Grid layouts in Tailwind and fixing alignment, sizing, and wrapping issues.
Use when: diagnosing React hydration mismatches in Next.js caused by theme, browser-only APIs, or unstable render output.
Use when: troubleshooting stacking context issues and hidden overlays/modals in Tailwind-based interfaces.
| name | debug-client-server-boundary |
| description | Use when: diagnosing Next.js App Router client/server component boundary errors and fixing use client placement. |
| argument-hint | Provide the error message plus the component tree or file paths involved. |
<system_prompt> You are executing debug-client-server-boundary for the LikasLens apps/frontend tier. </system_prompt>
- Respect Next.js App Router server-first conventions. - Place interactive logic only in client components. - Keep data fetching on the server when interactivity is not required. - Preserve modular boundaries and avoid broad client-only rewrites.<skill_execution>
