Creative
Website autopilot: Grok Bot interviews → Imagine → Build one prompt at a time
One mega-prompt website build drifts; you still need brand rules, visuals, and human review.
What hurt
kr8tiv AI (@kr8tivai) showed a live multi-prompt, multi-page site build for Antihero using Grok, Grok Bot, Grok Imagine, and Grok Build. Six concrete steps plus copy-paste interview/build prompts. Tip with author-published prompts. Not affiliated with xAI.
What to install or create
Brand kit first. Grok Bot interviews you into a Site Brief, writes RULES + numbered TASK prompts, Imagine makes visuals, Build runs one job/one commit while Bot supervises, then you review and fix.
Bots
Site autopilot supervisor
Interviews for briefs, writes Build prompt packs, checks each Build checkpoint, hands the next TASK.
Plugins
None on day one. Follow the first-run steps.
Files
Brand kit (voice, logo, colors, two fonts, tagline) + Site Brief + Visual Direction brief + RULES paragraph file.
Routines
None on the first run. Watch one manual pass first.
The prompt
PROMPT 1 · Site interview (author-quoted)
Quoted from @kr8tivai — as published. Do not invent a second system prompt.
Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.
You're a senior web designer who has won Awwwards Site of the Day. Read my brand brain: [paste it]. Interview me to plan a website, one question at a time, and wait for each answer. Push back if I'm vague. Ask about: what the site is for and the one action visitors should take, who the visitor is, my offer, the pages and sections I think I need, the vibe in three words (and three it must never be), three to five reference sites I love and why, what I already have, what must never change, my motion appetite from 1 to 10, and my limits. Then write a one-page Site Brief and ask me what you got wrong. Never send, post, spend, or buy without my explicit yes.
PROMPT 4 · Write all Build prompts (author-quoted)
Quoted from @kr8tivai — as published. Do not invent a second system prompt.
Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.
Now write the complete build package for Grok Build, the coding agent that builds this site in my project folder. Start with one RULES paragraph that every prompt repeats word for word: brand name, fonts, colors with hex codes, voice and banned words, what must never be touched, do not deploy, do not delete files (move them to /_archive), motion rules (respect reduced motion), commit to git after every prompt. Add this line: Elevated by default, aim for an Awwwards Site of the Day result, not a regular website, one bold idea per section, real copy in my voice, specific details. Add these NO SLOP RULES: never use purple-to-blue gradients, a centered hero with a stock blob, the generic 3-card feature grid, emoji icons, words like unlock, elevate, seamless, revolutionize or empower, lorem ipsum, stock photos of people, the default Tailwind look, the same rhythm in every section, or fake testimonials and numbers. Always use asymmetric layouts, a deliberate type scale, motion with a purpose, and details only this brand would have. Then write numbered prompts, one job each, in build order: setup, navigation, each page and section, imagery, motion and effects, performance, a credits page for anything borrowed, and QA. Every prompt is one copy-paste block: the full RULES paragraph, then TASK, then exact instructions and what done looks like. Each one must work on its own. Write them all and save them as a file. Never send, post, spend, or buy without my explicit yes.
First run
- 1Read the 6-step thread https://x.com/kr8tivai/status/2106513348158488811 and the copy-paste prompts https://x.com/kr8tivai/status/2106513351434211571 (credit @kr8tivai).
- 2Brand kit first: voice, logo, colors, two fonts, tagline.
- 3Paste PROMPT 1 into Grok Bot; finish the Site Brief (optionally run visual + standout-feature interviews from the same thread).
- 4Paste PROMPT 4 so the Bot writes RULES + numbered Build TASK prompts; save that file.
- 5Make hero visuals in Grok Imagine; feed Grok Build one TASK at a time (checkpoint after each). Open locally, hard refresh, run the jury/fix list — do not deploy from the bot.
Approval fence
Do not deploy or publish from the bot. Review locally; keep a credits page for borrowed open source.
What to tweak
Steal: one prompt, one job, one commit — and paste the never-touch RULES into every Build prompt.
Source
kr8tiv AI @kr8tivai · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.