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

# Cook Web Domain: c-types

This file adds local guidance for `src/cook-web/src/c-types`. 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 ambient declarations and compatibility types used
  across the `c` experience.

- Representative files in this subtree: `src/cook-web/src/c-types/index.ts`,
  `src/cook-web/src/c-types/store.ts`, `src/cook-web/src/c-types/sse.d.ts`,
  `src/cook-web/src/c-types/user-roles.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-types/` before
  widening to global type and lint checks.

## Do

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

- Keep compatibility types aligned with the actual `c` stores, services, and
  runtime payloads they describe.

- Preserve narrow declaration files and augmentations so legacy type support
  does not shadow modern package exports.

- Treat this directory as a compatibility contract, not as a place to mask
  runtime drift with broad casts.

## Avoid

- Do not add overly broad ambient declarations that hide real type errors
  elsewhere in the `c` stack.

- Do not rename exported legacy types without updating all stores and service
  helpers in the same task.

- Do not keep dead declarations after a migration; remove or relocate them
  once the owning runtime code moves.

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

## Commands

- `rg -n "c-types" 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-types/` 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-types/` 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/module-augmentation-guardrails/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.
