Copy-paste ChatGPT Codex prompts for landing pages, dashboards, pricing pages and app screens, scoped as single tasks Codex can finish in one run, plus a prompt that writes your AGENTS.md design rules.
“Redesign this [site or app] so it looks professional, using the template as the new design…”
Full ChatGPT Codex prompt with a licence
AGENTS.md design rules prompt
A design section for AGENTS.md so every Codex task follows your template, colours and spacing.
“Create the design rules file at AGENTS.md for this project, so every future change follows the same design…”
Full ChatGPT Codex prompt with a licence
Every ChatGPT Codex prompt above shows its opening line for free. The full prompts, and the templates they are written for, come with a BrowserMoon licence.
Codex works through your repo as a series of tasks, so the best Codex prompts are scoped and specific. These prompts give Codex one page to build, a BrowserMoon template saved in the repo to follow, and a clear definition of done, so each task comes back as a clean pull request.
How to use these ChatGPT Codex prompts
1
Pick the prompt for your page
Choose the ChatGPT Codex prompt for the page you are building, from a SaaS landing page to a login screen or an AI chat app.
2
Copy the template it uses
Each prompt is written to go with the template shown on its card. Copy that template, or any template from the ChatGPT Codex templates page.
3
Give ChatGPT Codex the design
The design template is in design/template.html. Read it first and match its fonts, spacing, colours, corner radius and components exactly.
4
Fill in the brackets and send
Replace the parts in brackets, like [product name] and [audience], with your own details. The prompt ends with: “Keep the change to this one page and its components. When done, run the build and lint, and summarise the change for the pull request.”
Which ChatGPT Codex prompt to start with
Start with the AGENTS.md design rules prompt, because every Codex task reads AGENTS.md before it starts. Then send one page prompt per task, beginning with the page your users see first.
Why ChatGPT Codex needs a design in the prompt
OpenAI Codex works through your repository in a sandbox and returns a diff or pull request. It follows instructions carefully, so it does exactly what a task says and nothing more. If the task does not describe the design, the design is left to chance.
These prompts are written as scoped Codex tasks: one page, a template saved in the repo to follow, clear rules and a definition of done. Codex reads the template, builds the page and runs your checks, so the pull request is ready to review.
What is inside every ChatGPT Codex prompt
Each prompt on this page is built from the same five parts. The page-specific part changes per prompt; the rest is written for how ChatGPT Codex works.
1. What to buildThe product, the audience and the outcome the page must deliver, in one or two sentences.
2. Every section, in orderEach section named with what goes in it, so nothing is left for the tool to invent.
3. The designThe design template is in design/template.html. Read it first and match its fonts, spacing, colours, corner radius and components exactly.
4. The design ruleskeep one accent colour, use the template's type scale and spacing exactly, give every section generous white space, keep body text at least 15px, and make every layout work at 375px wide with no horizontal scroll.
5. The stack and how to finishUse the framework and styling already in this repo. If the repo is empty, use Next.js with Tailwind CSS. Keep the change to this one page and its components. When done, run the build and lint, and summarise the change for the pull request.
Tips for writing ChatGPT Codex prompts
One task, one page
Codex does best with one clear task. Ask for one page or section per task, not the whole site.
Keep the template in the repo
Commit the template to design/template.html so every Codex task can read it.
Define done
Tell Codex what finished looks like: builds, passes lint, matches the template at phone and desktop width.
Use AGENTS.md
Put your design rules in AGENTS.md so every Codex task follows them.
What to ask ChatGPT Codex after the first prompt
Task: build the pricing page from design/template.html, reuse existing components, run lint and tests.
Task: replace hard-coded colours across the app with the tokens defined in AGENTS.md.
Task: make every page pass at 375px wide with no horizontal scroll.
Task: write a short summary of the design rules for the pull request description.
Common ChatGPT Codex prompt mistakes
Tasks that are too big
Ask Codex for one page or one section per task. Large tasks return large, hard-to-review diffs.
No AGENTS.md
Without it, every task interprets the design again. Write the rules once and Codex follows them.
Templates outside the repo
Codex only sees what is in the repo. Commit the template before you send the task.
No definition of done
Say what finished means: builds, passes lint, matches the template at phone and desktop width.
Who these ChatGPT Codex prompts are for
Codex is used by developers and teams who hand off well-defined tasks to an agent and review the result as a pull request. These Codex prompts are for teams who want UI tasks to come back looking designed and consistent, not just working.
More templates for these ChatGPT Codex prompts
A prompt says what to build; a template shows ChatGPT Codex what it should look like. These templates also fit the prompts above.