菜单
Deploy a GBL game to a shareable staging URL with Vercel + Neon Postgres, driven from the CLI (neonctl + vercel). Use when a game builds and runs locally and needs a public URL for review - the easy alternative to the k8s deploy/ path.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Work with devrouter for local dev routing (HTTP + TCP/Postgres + dependency-only Docker services)
Build the frontend of a GBL platform game - player cockpit with status-switch pattern, admin pages, realtime wiring, and which components to reuse from @gbl-uzh/ui and @uzh-bf/design-system. Use when creating or changing game pages/components in apps/<game>/src.
Scaffold a new GBL platform game app inside this monorepo by copying apps/demo-game - file-by-file copy/rename checklist, prisma setup, local dev environment, and first-run verification. Use when starting a brand-new game.
Keep the GBL platform wiki (docs/) accurate and conformant with the Open Knowledge Format - the repo-specific extension of generic OKF/LLM-wiki practice - when to update it, how to fact-check against code, house conventions, and validation. Use whenever a change touches packages/platform, packages/ui, apps/demo-game behavior, or when doc-code drift is noticed.
Implement the backend of a GBL platform game - the six-module Services contract (Actions, Period, PeriodResult, Segment, SegmentResult, GameFacts), facts types with yup schemas, and seed data. Use when writing or changing game logic in apps/<game>/src/services.
Design a learning game for the GBL platform - check platform fit, map a game idea onto periods/segments/decisions/facts, and produce a build-ready game design. Use BEFORE writing any code for a new game.
| name | gbl-deploy-staging |
| description | Deploy a GBL game to a shareable staging URL with Vercel + Neon Postgres, driven from the CLI (neonctl + vercel). Use when a game builds and runs locally and needs a public URL for review - the easy alternative to the k8s deploy/ path. |
App unreachable or environment broken locally? Run the gbl-environment-doctor skill first - this skill assumes the game already builds and runs on http://localhost:3000.
This is the easy staging path: a Vercel deployment of one game app backed by a Neon serverless Postgres, so you can hand a reviewer a URL. It is distinct from the production path (deploy/, Kubernetes + kustomize + infisical, *.env.bf-app.ch), which needs cluster access and is owned by the platform team.
The conceptual reference is docs/deploying-a-game.md - read it for the "why" behind each step. This skill is the actionable runbook.
apps/<game> builds locally (pnpm --filter @gbl-uzh/<game> run build succeeds) and the user wants a public URL.deploy/, bf-app.ch, or infisical, that is the production path - not this skill.vercel --version # npm i -g vercel; vercel login
neonctl --version # npm i -g neonctl; neonctl auth
pnpm --filter @gbl-uzh/<game> run build # must succeed locally first
If the local build fails, fix that first - a Vercel build fails the same way but slower.
Follow docs/deploying-a-game.md steps 1-6 in order. The load-bearing decisions, condensed:
neonctl projects create --name <game>-staging. Collect two connection strings - pooled (-pooler host, append ?sslmode=require) for the app, direct for migrations/seed.vercel link from the repo root. Root Directory apps/<game>. Build command MUST use pnpm --filter @gbl-uzh/<game>... run build (the ... builds workspace deps first - required because prisma/copy.ts reads @gbl-uzh/platform/dist/schema.prisma at build time)..env.production): DATABASE_URL (pooled), NEXTAUTH_URL, NEXTAUTH_SECRET, NEXT_PUBLIC_API_URL, NEXT_PUBLIC_APP_URL, AUTH0_*. See the table in the wiki page.prisma migrate deploy (or db push) then prisma:seed. Seeding is mandatory - no PlayerLevel ladder means players cannot be created.vercel (preview URL) then vercel --prod.DATABASE_URL at the direct (non-pooled) Neon string in Vercel. Serverless functions open many short-lived connections; without the pooler you hit the connection limit fast. Direct is for migrate/seed only.NEXT_PUBLIC_* are build-time baked. Changing them requires a redeploy, not a restart. Set them to the final Vercel domain before the first prod deploy.NEXTAUTH_URL must match the deployed origin exactly (including https://). A mismatch causes STATE_COOKIE_MISSING on admin login - the same localhost vs 127.0.0.1 class of bug as local Playwright.apps/<game>/.env.production is demo-game leftover. When scaffolding from apps/demo-game it still points at demo-game.stg.env.bf-app.ch. Vercel env vars override it, but fix or empty the file anyway (see gbl-new-game-app decontamination checklist).SHADOW_DATABASE_URL is not needed on Vercel. It is only used by prisma migrate dev (local authoring). Leave it unset.After vercel --prod:
https://<domain>/admin/login - sign in through your OIDC tenant.