luckyplans

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.

Use when you need LuckyPlans-specific frontend reference constraints that are not covered by task-specific frontend skills.

Use when building or modifying Next.js pages that consume frontend hooks so server/client component boundaries and Apollo provider placement are correct.

Use when adding or changing inline graphql() operations in apps/web so generated client types remain in sync.

Use when code or infrastructure changes require synchronized updates to docs under apps/web/content and related architecture references.

Use when modifying Prisma schema or creating migrations on tables with existing data, especially when adding columns or tightening constraints.

Use when adding or changing shared contracts or cross-cutting utilities in packages/shared, including entity types, message patterns, and reusable helper functions.

Use when creating a standard NestJS module in the API gateway, and when a new service is not justified by CPU-heavy, cron, or independent scaling requirements.

Use when deciding whether a new NestJS microservice is justified and, if justified, creating the full LuckyPlans microservice stack from app bootstrap through Docker, Helm, and ArgoCD deployment.

Use when preparing a git commit message to enforce conventional-commit format and repository commit hygiene.

Use when creating or refining a GitHub issue for bugs, features, chores, docs, or refactors with reproducible context and acceptance criteria.