Vercel boilerplate

misaki-studio-vercel builds a Misaki Studio frontend as a Next.js static export and deploys the prebuilt output to a Vercel project in your own account.

The site is built locally. The deploy script uploads the prebuilt result rather than asking Vercel's builders to compile the source.

Requirements

• Node.js 20 or newer

• A Vercel account for deployment

• A linked Vercel project or scoped CI environment credentials

• A frontend-only Misaki Studio project, or a separate verified host for any generated database backend

The current public repository uses Next 16.3.3, React 19.2.8, and misaki-studio-internal 0.1.76. Review its current package.json before installation.

Clone and configure

git clone https://github.com/Misaki-Studio/misaki-studio-vercel.git
cd misaki-studio-vercel
npm install
cp .env.example .env
npx vercel link

Set SITE_NAME and the final SITE_URL without a trailing slash. Linking selects or creates the external Vercel project; review the account, scope, and project name shown by the CLI before accepting it.

If SITE_URL is empty, the current SEO script skips the sitemap and llms.txt instead of writing absolute links to a guessed origin.

Export into the clone

Coverage: UI + MCP. Desktop required for local-folder export.

Configure:

REACT SRC PATH → <clone>/src
ASSET PATH     → <clone>/public
NODEJS SRC PATH → empty

Commit the clean clone, export, and inspect the diff. src/, public/, and the exported SEO generator are generator-owned. vercel.json and next.config.js remain shell configuration.

Build and test

npm run build

The build writes the static site into out/. Before deploying, serve or inspect the static result and check every route, direct navigation, the generated 404 page, assets, responsive behavior, browser console, robots.txt, sitemap, and llms.txt.

Deploy the prebuilt result

npm run deploy

The current script runs vercel build and then vercel deploy --prebuilt --yes. This changes external Vercel state. Confirm the linked project and inspect the local build before running it.

For CI, supply VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID through the environment. Never place them in committed files or agent prompts.

To use a custom domain, add it to the Vercel project, set SITE_URL to match, rebuild, and verify the generated canonical/sitemap/LLM URLs before deployment.

Ask an agent to prepare the deployment

Coverage: UI + MCP for export; provider CLI for deployment.

Inspect the Vercel clone and my current export settings. Propose the exact React source and asset paths with no backend path. Read the linked-project configuration if it is already present, but do not install, link, export, build, or deploy.

Export, Vercel linking, and deployment are separate approvals. An agent should not infer permission to modify your Vercel account from permission to inspect or write the local clone.

Current limitation

This target serves a static frontend only. It does not run Misaki Studio's generated database backend. A frontend using generated database views/actions needs a separately supported backend before deployment.