القائمة
Use when building or modifying Next.js pages that consume frontend hooks so server/client component boundaries and Apollo provider placement are correct.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when introducing or expanding tests in LuckyPlans, especially service logic, shared utilities, controllers, and resolvers.
Use when adding a new Next.js App Router page in apps/web, including route structure, data hooks usage, and auth/session-aware behavior.
Use when implementing or modifying frontend UI in apps/web to enforce the repository's HeroUI + Notion-style baseline consistently.
Use when adding a new GraphQL query or mutation in apps/web so the operation is defined inline in a hook and consumed by components.
Use when modifying or extending an existing frontend component in apps/web while preserving project styling conventions, hook boundaries, and accessibility.
Use when introducing or modifying frontend state management to keep GraphQL data in Apollo cache and avoid mixed-state ownership.
| name | implement-apollo-page-boundary |
| description | Use when building or modifying Next.js pages that consume frontend hooks so server/client component boundaries and Apollo provider placement are correct. |
'use client' only for pages/components using hooks/state/effects.apps/web/src/hooks.(public) layout has no providers.<AppProviders> inline.