ZZD public AI gateway · zzd_public_ai_gateway_v2
Resource: 02 · Deploy a vibe-coded project / 最短路径
Canonical map: https://zzd.show/docs/ai/map.json
Full handbook: https://zzd.show/llms-full.txt

# Deploy a vibe-coded project as a ZZD Show

Use this sequence unless the user asks for a narrower task.

1. Read `/llms.txt`, this branch, `show-contract`, `quality`,
   `assets`, `baas`, `lifecycle`, and `safety`.
2. Inspect the user's project and identify the actual browser entry,
   source files, build system, routes/states, assets, environment
   variables, network dependencies, and license. Never copy secrets.
3. Choose the smallest suitable architecture:
   - static client experience: Pieces + assets;
   - framework experience: readable source Pieces plus pinned
     dependencies and source-specific assets;
   - data/stateful experience: the above plus a bound ZZD Space/BaaS;
   - approved capability: call it through `window.AppRuntime`.
4. Open `https://code.zzd.show/shows/edit/` in a browser controlled
   by the user or agent. If the user is already signed in, use that
   ambient session without reading, copying, or exposing its cookie.
   If login is required, pause while the user signs in themselves.
5. Create a draft with `private=true` and `hidden=true`. Set the
   metadata, dependency configuration, readable live Pieces, and a
   provisional thumbnail.
6. Upload source-specific assets through the editor by semantic role.
   Bind files that need stable application-relative paths. Replace
   local-machine, temporary, and source-host URLs.
7. If the experience needs persistent data, realtime state, jobs, or
   service actions, create or select an owner-scoped BaaS binding in
   the editor's BaaS panel. Define a minimal schema and access model
   before writing client calls.
8. Validate the actual Show, not only the original local project:
   blank/fullscreen desktop and mobile, the real editor preview
   iframe, and the ordinary embed iframe when available. Exercise
   every meaningful state and inspect console, network, media,
   overflow, accessibility, and source ownership.
9. Fix failures and save a fresh final-state screenshot as the
   thumbnail. Keep the draft private/hidden until both the rendered
   result and live-source quality pass.
10. Ask for explicit user confirmation before changing public
    visibility. Then set `private=false` for access and
    `hidden=false` for discovery. Return the detail, blank, edit, and
    embed URLs, validation summary, remaining risks, and external
    dependencies.

Production navigation templates:

- New Show: `https://code.zzd.show/shows/edit/`
- Edit: `https://code.zzd.show/shows/edit/{show_id}/`
- Blank/fullscreen: `https://code.zzd.show/shows/blank/{show_id}/`
- Embed: `https://code.zzd.show/shows/embed/{show_id}/`
- Detail/share: `https://zzd.show/shows/detail/{show_id}/`
- Marketplace: `https://zzd.show/shows/sales/`
- New Sale: `https://zzd.show/shows/sales/new/`

Follow redirects and use URLs returned by the platform. Do not
substitute old development hosts. Do not reverse-engineer private
AJAX endpoints as a third-party API.

Import rule: a repository build output may be useful evidence, but
do not deploy an opaque hosted-page wrapper. Re-express the meaningful
client source as live Pieces and upload only appropriate supporting
files. Server code, `.env`, credentials, private datasets, CI keys,
and repository metadata do not belong in a Show.