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

# Cook Web Domain: components

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

## Scope

- This domain owns shared React UI and business components used across
  learner, admin, auth, settings, preview, and chat-oriented experiences.

- Representative files in this subtree:
  `src/cook-web/src/components/auth/EmailLogin.tsx`,
  `src/cook-web/src/components/shifu-edit/ShifuEdit.tsx`,
  `src/cook-web/src/components/ui/Button.tsx`

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

## Do

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

- Keep user-facing strings routed through shared i18n and component props
  instead of hardcoded labels.

- Preserve stable component contracts for callers before making broad prop or
  state-shape changes.

- Treat chat, preview, and auth components as shared behavior that often needs
  coordinated store and skill updates.

## Avoid

- Do not hide domain logic in styling-only components when the behavior
  belongs in hooks, stores, or shared libs.

- Do not add one-off request logic inside components that should call shared
  API helpers.

- Do not copy interaction or streaming behavior between components when an
  existing shared component or skill already describes it.

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

## Commands

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

## Tests

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

- src/cook-web/skills/chat-actionbar-ask-placement/SKILL.md

- src/cook-web/skills/listen-mode-audio-streaming/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.
