scaffoldlisted

# Scaffold New Feature Build a new feature end-to-end across all layers in the correct dependency order. ## 1. Confirm scope Before starting, confirm with the user: - **What** is being built (feature name and one-sentence description) - **Which layers** are needed (API, DB, backend, frontend — not every feature needs all four) - **Any constraints** (naming conventions, existing patterns to follow, related entities) Read `docs/CONVENTIONS.md` if it exists. Check `memory/**/*.md` for any architecture or design decisions relevant to this feature. If `memory/architecture/repo-map.md` exists, consult it to decide where new files for each layer belong (which directory owns API, data, service, and frontend code) so the scaffold follows the existing structure. After the feature lands and adds new directories, recommend `/repo-map refresh` so the map stays current. ## 2. git-engineer — branch setup Always first. Confirm the working branch. If on `main` or `master`, ask the user to name the feature branch before proceeding. Do not start any implementation until the branch is confirmed. ## 3. api-designer — REST contract Always invoke for new features that expose any endpoint. Pass: - The feature description and scope confirmed in step 1 - Any existing API patterns to follow (from CONVENTIONS.md or memory) The api-designer will produce routes, HTTP methods, request/response shapes, status codes, and auth requirements. Present the contract to the user and ask for approval before