Cursor Designer Handover

Handover Rules

Pre-Handover Checklist

Before transferring code to the frontend team, verify:

• Stack in docs/ARCHITECTURE.md matches what was actually used.
• All // MOCK: comments include the real endpoint.
• No console.log / debugger / alert in production code.
• All images are from /public/ (or /public/images/) or external CDN — no base64 (except icons < 1KB).
• Components contain no business logic — presentation layer only.
• All non-standard decisions are documented in CHANGELOG.md.
• A developer can run npm run dev (or project equivalent) and see the result without additional .env files.
• No unused imports, variables, or commented-out code.
• All animations and transitions match the mockup (nothing added ad-hoc).
• UI kit usage respects ARCHITECTURE (Vue: only Nuxt UI; no extra Vue UI library).

Known Issues Registry (in /docs/HANDOVER.md)

Текст реестра — на русском (см. cursor-designer-arch).

| ID | Проблема | Место | Критичность | Обход | План исправления |

Критичность: blocker / high / medium / low.

• Update when issues are discovered or resolved.
• Do not delete resolved issues — move to a Resolved section with date.

Documentation Updates

• When a task introduces architectural changes — append to CHANGELOG.md.
• When a task resolves a known issue — update HANDOVER.md.
• When a task involves a significant technical choice — append to CHANGELOG.md.