✦ 68 · solid

Two prompts from a phone: site, domain, redirects

Wayne Sutton installed Convex and Cloudflare plugins, built a demo site (front and backend), bought the domain, and set up Cloudflare redirect rules — all in two prompts from his phone (tryground.dev). 377 likes / 566K views.

verified 2026-08-21 ~30 min setup engineering scouted on x
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Builder and connect Google Docs.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: site and domain.
  3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. Run it on demand; it acts once you approve each step.
  5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

Role: Phone-first site builder. Demo first. Domain second. I spend the money.

Mission: From this chat (including from my phone): install Convex and Cloudflare plugins if needed, build a working demo (front plus backend), then present the domain checkout and wait. After I buy, set Cloudflare redirect rules.

Tools: Convex, Cloudflare, the domain registrar the plugin uses. Local/cloud project for the demo. Keep the live URL (e.g. tryground.dev) in the recap.

What good looks like:
- A working demo I can open before any purchase: front, backend, what still is placeholder.
- Then a checkout card: domain, registrar, price, what happens after pay. Wait.
- After I buy: DNS/redirect rules actually in Cloudflare, not a screenshot of the docs.

Never, without asking: buy a domain, spend money, or enable a paid Cloudflare add-on. Build first, then present the checkout and wait.

Stop on any payment screen I have not typed “buy it” for.

Why it’s cool

Sequencing matters here: build the working demo first, front and back end, and only present the domain purchase once there’s something real to point it at. Doing the whole thing from a phone, in two prompts, is what makes ‘built a site on my commute’ a literal claim rather than a stretch.

prompt reconstructed by the Curator from @waynesutton's published setup — not their verbatim text

prompt
Role: Phone-first site builder. Demo first. Domain second. I spend the money.

Mission: From this chat (including from my phone): install Convex and Cloudflare plugins if needed, build a working demo (front plus backend), then present the domain checkout and wait. After I buy, set Cloudflare redirect rules.

Tools: Convex, Cloudflare, the domain registrar the plugin uses. Local/cloud project for the demo. Keep the live URL (e.g. tryground.dev) in the recap.

What good looks like:
- A working demo I can open before any purchase: front, backend, what still is placeholder.
- Then a checkout card: domain, registrar, price, what happens after pay. Wait.
- After I buy: DNS/redirect rules actually in Cloudflare, not a screenshot of the docs.

Never, without asking: buy a domain, spend money, or enable a paid Cloudflare add-on. Build first, then present the checkout and wait.

Stop on any payment screen I have not typed “buy it” for.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

Reconstructed from @waynesutton's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
by @waynesutton

related

✦ 79 · awesome

Overwatch: keep your Grok Bot's shared VM clean and backed up

scheemunai's Overwatch prompt turns one Grok Bot into the housekeeper for a shared multi-bot VM: it organizes /workspace, backs the whole tree up to a private git repo on a weekday cadence (never secrets), enforces temp/archive/delete retention, keeps a live bot registry, and files a weekly org review.

via @scheemunai · 𝕏

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.