# spala-frontend-handoff

Use this skill when connecting React, Next.js, mobile, Webflow, or an AI-built frontend to a Spala backend.

Read first:

- https://spala.ai/ai-app-handoff/
- https://docs.spala.ai/guides/frontend-handoff/
- https://spala.ai/gap-closure.json

## Required handoff packet

- API base URL from the published Spala project.
- Generated OpenAPI, Markdown API docs, or SDK export.
- Auth routes: signup, login, refresh, logout, current user, role/permission behavior.
- Token and cookie behavior.
- CORS origins for browser clients.
- File upload contract: route, method, headers, signed URL behavior, max size, response shape.
- Realtime contract: channel names, event names, payloads, auth, reconnect, heartbeat, replay.
- Error format and validation failure format.
- Publish state and environment.

Do not let the frontend agent guess route names or project URLs. Use the generated project docs or owner-provided handoff packet.

If the frontend depends on file upload, realtime, roles, rate limits, export, backup, or deletion behavior, verify those details in the actual project and account terms before production.