# <ModuleName>

<One-line description of what the module does.>

## Screens / flows

| Screen or flow | Description | Entry / key paths |
|----------------|-------------|-------------------|
| <Name> | <What the user sees or does.> | `<Feature>/index.tsx` or `<Feature>/SubFlow/index.tsx` |

- One row per main screen or user-facing flow.
- **Entry / key paths:** folder or file that is the entry point (e.g. `List/index.tsx`, `Process/Edit/index.tsx`). Add 1–2 key component paths if it helps (e.g. main form or stepper).

## Key forms (if any)

| Form | Purpose | Path |
|------|---------|------|
| <FormName> | <What it configures or submits.> | `<Feature>/components/forms/<FormName>/` |

- Only forms that are important to find when refining a ticket (e.g. configuration modals, main wizards). Omit tiny field-level components.

## Shared

- **Root:** List root-level files that exist (`routes.ts`, `services.ts` or `services/`, `types.ts` or `types/`, `queries.ts`, `constants.ts`, `utils.ts`). If API lives outside the module (e.g. `src/services/`), note it.
- **components/**, **hooks/** (if present at module root): One line each with main exports or purpose.

---

*Generated for quick context when refining tickets. Update when adding or renaming main screens or forms.*