use-cases/deploy-app-or-website.md +75 −0 added
1---
2name: Deploy an app or website
3tagline: Build or update a web app, deploy a preview, and get a live URL.
4summary: Use Codex with Build Web Apps and Vercel to turn a repo, screenshot,
5 design, or rough app idea into a working preview deployment you can share.
6skills:
7 - token: build-web-apps
8 url: https://github.com/openai/plugins/tree/main/plugins/build-web-apps
9 description: Build, review, and prepare web apps with React, UI, deployment,
10 payments, and database guidance.
11 - token: vercel
12 url: https://github.com/openai/plugins/tree/main/plugins/vercel
13 description: Deploy previews, inspect deployments, read build logs, and manage
14 Vercel project settings.
15bestFor:
16 - Turning a screenshot, map, design brief, or rough app idea into a working
17 web preview
18 - Deploying a branch or local app without manually wiring Vercel commands
19 - Sharing a live URL after Codex runs the build and checks the deployment
20starterPrompt:
21 title: Build and Deploy a Preview
22 body: >-
23 Use @build-web-apps to turn [repo, screenshot, design, or rough app idea]
24 into a working website.
25
26
27 Then use @vercel to deploy a preview and hand me the live URL.
28
29
30 Context:
31
32 - [what the site should do]
33
34 - [source data, API, docs, or assets to use]
35
36 - [style or product constraints]
37
38 - [anything not to change]
39
40
41 Before you hand it back, run the local build and verify the deployment is
42 ready.
43 suggestedEffort: medium
44relatedLinks:
45 - label: Build Web Apps plugin
46 url: https://github.com/openai/plugins/tree/main/plugins/build-web-apps
47 - label: Vercel plugin
48 url: https://github.com/openai/plugins/tree/main/plugins/vercel
49 - label: Vercel deployments
50 url: https://vercel.com/docs/deployments/overview
51---
52
53## Start with the site and the deploy target
54
55Codex can build or update a website or app, run the project checks, deploy it with Vercel, and return the URL.
56
57The useful handoff is concrete: a repo, screenshot, map, design brief, product note, API doc, or data source. Codex should inspect the project before changing it, then use the Vercel plugin to deploy a preview by default.
58
59Use `@build-web-apps` when Codex needs to build or polish the app. Use `@vercel` when it should deploy, inspect the deployment, or read Vercel build logs.
60
61## Check the result before you share it
62
63Codex should tell you what it changed, which command it used to build the project, and whether the Vercel deployment is ready. If the deploy needs an environment variable, team choice, domain setting, or login step, Codex should call that out instead of pretending the site is finished.
64
65Keep production changes explicit. A preview deployment is the default; ask for production only when you mean it.
66
67## Iterate from the live URL
68
69Once you have the preview, keep the same thread open. Ask Codex to open the URL, fix layout issues, update copy, wire missing data, or read Vercel logs if the deploy fails. The thread already has the repo, deployment, and build context.
70
71Good follow-ups are specific:
72
73- "The mobile layout is cramped. Fix it and redeploy the preview."
74- "Use the same project and add the latest data from [source]."
75- "Read the failed build logs and fix the deploy."