<!-- Generated by scripts/generate_ai_collab_docs.py. Edit metadata in that script. -->

# Cook Web Domain: c-constants

This file adds local guidance for `src/cook-web/src/c-constants`. Read the
repository root and `src/cook-web/AGENTS.md` first, then use this file for
domain-specific frontend ownership.

## Scope

- This domain owns legacy constants for course, environment, product, UI, and
  user behavior used throughout the `c` experience.

- Representative files in this subtree:
  `src/cook-web/src/c-constants/uiConstants.ts`,
  `src/cook-web/src/c-constants/env.ts`,
  `src/cook-web/src/c-constants/courseConstants.ts`,
  `src/cook-web/src/c-constants/productConstants.ts`

- Keep durable frontend rules here only when they are more specific than the
  Cook Web-wide guidance in the parent directory.

- Use focused frontend verification around `src/cook-web/src/c-constants/`
  before widening to global type and lint checks.

## Do

- Start from the local entry files and preserve how `c-constants` currently
  separates route code, shared logic, state, and utilities.

- Keep shared breakpoint, environment, and product constants as the single
  source of truth for legacy consumers.

- Preserve constant names and semantics when skills or stores already depend
  on them indirectly.

- Treat this directory as configuration data rather than a place to hide
  behavior that belongs in hooks or services.

## Avoid

- Do not duplicate breakpoints or query-parameter constants in legacy pages
  when they already exist here.

- Do not mix runtime branching logic into constant files unless the logic is
  truly configuration-oriented.

- Do not rename exported constants casually because many legacy files import
  them directly.

- Avoid pushing domain-local rules up to shared docs unless another frontend
  subtree truly depends on the same constraint.

## Commands

- `rg -n "c-constants" src/cook-web/src` to locate call sites before editing
  this subtree.

- `cd src/cook-web && npm run type-check` after TypeScript, store, hook,
  request, or route-contract changes.

- `cd src/cook-web && npm run lint` before closing the task when shared
  frontend code or route files changed.

- `cd src/cook-web && npm run test -- src/c-constants/` for focused Jest
  coverage when this subtree already has or gains tests.

## Tests

- Add or update focused tests closest to `src/cook-web/src/c-constants/` for
  the happy path and the most important regression or business-code error
  path.

- Rerun type-checking and linting when exported props, store fields, hook
  contracts, or route behavior move.

- When a domain depends on shared request or normalization helpers, update
  those tests or add new ones in the same task.

- Document skipped UI, browser, or provider-dependent verification in the task
  summary when local automation cannot cover it.

## Related Skills

- src/cook-web/skills/chat-layout-width-detection/SKILL.md

- `src/cook-web/SKILL.md`

- `SKILL.md`

- Create a focused skill under `src/cook-web/skills/<topic>/SKILL.md` when the
  same debugging or migration workflow repeats.
