Flisk Deploy Vercel

---
name: flisk-deploy-vercel
description: Take a stack that already works under `flisk up` to Vercel with that host's own tooling - a Vercel project for a Flisk frontend (React, Vue, Svelte) or serverless functions. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Vercel. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. Vercel CLI or Git integration recommended.
metadata:
  author: flisk-sh
  version: "1.0"
---

# Deploy to Vercel

Flisk is local-only. This skill covers deploying compatible parts of a Flisk project to Vercel.

## Workflow

1. Confirm the frontend works locally with `flisk up`.
2. Identify the frontend service (typically `appType: frontend` with Vite/React/Vue).
3. The generated `vite.config` and build output can be adapted; do not commit `.autogenerated/` files.
4. Create a `vercel.json` or use the Vercel Git integration pointing at the frontend directory.
5. Set environment variables in the Vercel dashboard (API base URLs, etc.).
6. Deploy with `vercel` or push to the connected Git branch.
7. Point the production API URL at your backend (which may still be local or deployed elsewhere).

## Guardrails

- Vercel is best for frontends and serverless; full multi-service Docker stacks stay local or go to other hosts.
- Keep the local service.json as the source of truth for the contract.
- Update CORS and API base URLs for production.