Give your agent a useful starting point.
Copyable website-building prompts for your first brief, mobile layout, visual refinement and checks before deployment.
Your first website
Replace the bracketed text with your own purpose, audience and content. Start small, check the preview, and make one clear change at a time.
Build a small website for me, ready to publish on Vercel.
The site should:
- Purpose: [what the website should do]
- Audience: [who it is for]
- Visual direction: [colours, typography and references]
- Sections: [the content visitors need]
Use Next.js, as in the masterclass. Keep the site simple.
Use the attached design or brand reference. Make it easy to read
and use on a phone and a computer.
Build it, start the preview and open it for me.
Run the checks, fix errors and tell me what to review.
Explain any steps I need to do in plain English.Improve the mobile layout
Give the small screen the same care.
Review this page at mobile widths and fix any overflow, cramped spacing or layouts that should stack vertically. Check tap targets and code blocks. Preserve the desktop design.Make the design less generic
More intention. Less decoration.
Review the visual design for generic AI/SaaS patterns. Remove unnecessary gradients, decorative cards and visual clutter. Use stronger typography, spacing and a more deliberate visual hierarchy instead.Check before deployment
Turn a working draft into a site you can publish.
Prepare this project for production deployment. Run linting and the production build. Fix any errors. Check for broken links, console errors, obvious accessibility problems and mobile overflow. Do not make unrelated design changes. Summarise what you tested and any remaining issues.Turn a design into a build brief
Use in ChatGPT after choosing your design. This follows the planning handoff in the stream.
Turn this website idea and chosen design into a brief I can paste into Codex. Use Next.js for deployment on Vercel. Include the audience, pages, content, brand references and what visitors should do. Keep the first version simple. Ask Codex to build it, open a preview and check it for me.Save the site to GitHub
Connect GitHub in Codex, then replace the bracketed URL.
Here is my GitHub repository: [paste URL]. Save this site there. Exclude passwords and private files. Handle the Git setup, commit and push, then confirm the files are on GitHub.Try an update before it goes live
A branch is a separate version you can review. The stream used this for the logo and information pages.
Make a feature branch for this change: [describe change]. Build it, check it and push the branch to GitHub. Help me open its Vercel preview so I can review it before changing the live site.Publish an update I have checked
Use after reviewing the preview. In the stream, main was the branch Vercel published to the live site.
I have checked the preview and am happy with it. Merge this change to main and clean up the feature branch. Confirm the live deployment succeeds and give me the website address to check.Check my published site for AI agents
Use after publishing. Replace the address with your live website URL.
Review my published site at [live website URL] for AI agents. Help me run it through https://is-agentic.com/ and read the report. If you cannot start the scan, tell me how to run it and ask for the report link. Verify the findings, explain the important gaps in plain English, and fix relevant Essential issues on a feature branch. Check that agents can read the main content and use links and forms. Do not expose private content or invent APIs or services. Show me a preview to approve, then help publish the fixes and rescan the live site. Report what improved and what remains.When another prompt isn’t the answer
If the scope keeps growing or you cannot tell whether the result is ready, a conversation may be more useful than another iteration.