takeshi-su57

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.

Use when implementing frontend auth-adjacent behavior to preserve gateway-managed session architecture and avoid token handling in the browser.

Use when creating or reorganizing routes in apps/web so route groups, layout behavior, and path conventions remain consistent.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when opening or updating a pull request so title, description, validation steps, and architecture justifications are complete.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when creating new skills, editing existing skills, or verifying skills work before deployment