What problem does it solve? Getting a local project live on Vercel involves many decisions: whether the project is linked, whether the CLI is authenticated, which team to deploy to, and what to do in sandboxed environments without credentials. This Skill automates that decision flow and executes the correct deployment path. ## Core Features & Use Cases - State-aware deployment: Detects git remotes, Vercel project linking (.vercel/project.json or repo.json), and CLI authentication before choosing a deploy method. - Multiple deploy paths: Supports git-push deployments, direct vercel deploy CLI uploads, and no-auth fallback scripts that return a preview URL plus a claim URL. - Framework auto-detection: The bundled shell scripts detect over 40 frameworks (Next.js, Astro, Nuxt, SvelteKit, Remix, and more) from package.json and package the project excluding node_modules, .git, and .env files. - Use Case: You have a Next.js app in a sandboxed environment with no Vercel credentials. The Skill packages the project, uploads it via the claimable deploy endpoint, waits for the build, and returns a live preview URL and a claim URL to transfer ownership. ## Quick Start Deploy my current project to Vercel and give me the preview link.
