Menu
Ship a monorepo web app to Vercel as static output without pretending the backend shipped too
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pilot a community Spec Kit extension without pretending it is trusted, official, or a hard gate
Lock what an analytical financial redesign may beautify, but never hide, reorder, or distort
Test tripwires for mortgage analysis UI redesign — preserves logic integrity through visual changes
Choose Spec Kit extensions that reinforce real repo gaps without duplicating existing orchestration
Run Spec Kit through the repo-pinned official CLI and keep the official git extension as the branch workflow source of truth
Freeze cross-cutting contracts before parallel implementation starts
| name | static-monorepo-vercel |
| description | Ship a monorepo web app to Vercel as static output without pretending the backend shipped too |
| domain | deployment |
| confidence | high |
| source | earned |
Use this when a pnpm monorepo contains a static web app and a separate backend service, but the current Vercel deployment only publishes the web output. The important part is not the config itself; it is keeping the deployment boundary honest in product behavior and docs.
vercel.jsonvercel.json at the monorepo root.outputDirectory at the built web artifact, not the repository root./api/v1, but allow override with environment config./api/v1 is unavailable instead of implying full-stack hosting.vercel.json installs from the monorepo root, builds @batalla-ias/web, and publishes apps/web/dist.README.md explicitly says the Vercel deploy serves only the static frontend and does not upload the Express API.apps/web/src/services/analysis-api.ts defaults to /api/v1 and marks missing compare/affordability support as visible local preview instead of fake backend success.