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

# Cook Web Domain: config

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

## Scope

- This domain owns frontend runtime environment helpers and supporting
  documentation for browser-visible configuration.

- Representative files in this subtree:
  `src/cook-web/src/config/environment.ts`,
  `src/cook-web/src/config/ENVIRONMENT_CONFIG.md`

- 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/config/` before
  widening to global type and lint checks.

## Do

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

- Keep browser-safe environment reads centralized so pages and components do
  not branch on raw process variables.

- Preserve the contract between backend `/api/config` output and local
  environment defaults consumed on the frontend.

- Treat configuration docs as part of the public developer interface for Cook
  Web setup and troubleshooting.

## Avoid

- Do not scatter environment parsing across components or hooks when
  `environment.ts` should stay the source of truth.

- Do not expose secrets or server-only config values in frontend code or docs.

- Do not let docs drift from runtime behavior when adding or removing frontend
  configuration flags.

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

## Commands

- `rg -n "config" 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/config/` for focused Jest coverage
  when this subtree already has or gains tests.

## Tests

- Add or update focused tests closest to `src/cook-web/src/config/` 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/SKILL.md`

- `SKILL.md`

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