Menu
Use when introducing or modifying frontend state management to keep GraphQL data in Apollo cache and avoid mixed-state ownership.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 implementing frontend auth-adjacent behavior to preserve gateway-managed session architecture and avoid token handling in the browser.
| name | enforce-apollo-state-boundary |
| description | Use when introducing or modifying frontend state management to keep GraphQL data in Apollo cache and avoid mixed-state ownership. |
/graphql) with credentials: 'include'.