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

# Cook Web Domain: c-common

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

## Scope

- This domain owns small shared hooks and tracking helpers that support the
  legacy `c` frontend experience.

- Representative files in this subtree:
  `src/cook-web/src/c-common/hooks/useDisclosure.ts`,
  `src/cook-web/src/c-common/hooks/useTracking.ts`,
  `src/cook-web/src/c-common/tools/tracking.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-common/` before
  widening to global type and lint checks.

## Do

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

- Keep lightweight legacy helpers centralized so the `c` experience does not
  grow duplicated micro-utilities.

- Preserve tracking and disclosure behavior because the same patterns can
  appear across multiple legacy pages.

- Treat these helpers as compatibility surfaces until the legacy experience is
  fully retired or migrated.

## Avoid

- Do not fork tracking helpers for one page when a shared legacy hook already
  exists.

- Do not let these helpers drift from the stores or constants they are
  expected to coordinate with.

- Do not move shared compatibility behavior into page files where it becomes
  hard to discover and reuse.

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

## Commands

- `rg -n "c-common" 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-common/` 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-common/` 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.
