sc-vercel

# /sc-vercel — Vercel (online frontend) > **Status:** implemented (online path). ```mermaid flowchart TD A["/sc-vercel"] --> B["find/create Vercel project<br/>(bound to GitHub repo)"] B --> C["set CONVEX_DEPLOY_KEY (encrypted)"] C --> D["set coupled build cmd<br/>npx convex deploy --cmd 'npm run build'"] D --> E["add custom domain / subdomain"] E --> F["read required DNS from Vercel<br/>(array-normalized + IPv4 guard)"] F --> G["Hostinger DNS<br/>CNAME (sub) / A (apex)"] G --> H["trigger deploy + poll readyState<br/>(15-min cap, blip-tolerant)"] H --> I["live URL ✅<br/>NEXT_PUBLIC_CONVEX_URL injected at build"] ``` ## Connection-safe local execution When `VERCEL_TOKEN` is stored in a direct SI-Coder named connection, run this skill's credential-dependent helper through `sc run -- ...`: ```bash sc run -- node skills/sc-vercel/scripts/deploy.js --help ``` The plain `node ...` examples below are script-interface examples for callers that already supply the required environment. A Composio/native-MCP Vercel connection must execute through that external backend. ## When to use - You want Vercel's edge network for the Next.js frontend, with the Convex backend on **Convex Cloud** (managed). - You don't want to deal with a Dockerfile / Compose for the frontend. - The online counterpart to the self-hosted Dokploy path. Pair with `/sc-convex-cloud` for the backend. ## Scope (implemented) `scripts/deploy.js` is a single 12-step orchestrator: 1....