메뉴
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 직업 분류 기준
| 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.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.