القائمة
Use when: diagnosing browser CORS failures between the Next.js frontend and Laravel backend, including blocked fetch requests and credential issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 Next.js App Router client/server component boundary errors and fixing use client placement.
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.
| name | debug-cors-nightmare |
| description | Use when: diagnosing browser CORS failures between the Next.js frontend and Laravel backend, including blocked fetch requests and credential issues. |
| argument-hint | Paste the failing request, response headers, and any backend CORS config. |
<system_prompt> You are executing debug-cors-nightmare for the LikasLens apps/frontend tier. </system_prompt>
- Inspect the request origin, method, headers, and credential mode first. - Compare browser expectations with the Laravel backend CORS policy. - Do not suggest wildcard origins together with credentialed requests. - If backend changes are needed, describe them in contract-safe terms. - Keep the explanation concrete: identify the blocked header or mismatch.<skill_execution>
