website-deploy

Give a site already deployed on simple-host a nicer address — the user's own custom domain (subdomain e.g. recipes.brand.com via CNAME, or apex e.g. brand.com via A record) or a free <name>.simple-host.app (one call, active at once, no DNS). Use when a user wants their site served from their own domain or a short name over HTTPS. Optional, since every site already has its own address, https://<site>.<handle>.simple-host.app/, where visitor sign-in and private collections work. Drives the bind → DNS → verify → live flow; the agent does the API work and relays the two DNS records (the address record and a TXT ownership record) the human must add at their registrar.

Stand up a private Simple Host instance for a hackathon on the organiser's own cloud account, create participant accounts in bulk, hand out their keys, and tear the whole thing down afterwards. Use when someone wants to run a hackathon, a class project showcase, an internal build day or any event where non-technical people need somewhere to publish what they make. Drives provider → server → DNS → install → accounts → teardown. The organiser never opens a terminal; this skill does.

Deploy static websites to simple-host.app. Use when an agent needs to build/validate a static site, deploy it (inline JSON files OR a tar.gz/zip archive), or wire up the per-site backend. Saved data nobody declared is Shared (public); anything else is declared once as Page info (the owner writes, everyone reads), Submissions (visitors send them; the owner sees all; each visitor sees, changes and withdraws their own; private unless made public), Personal (one private record per signed-in visitor) or a Shared board (a list signed-in visitors edit together). Every site lives at https://<site>.<handle>.simple-host.app/. Pages and public lists are readable by anyone; visitors sign in with Google or an emailed code via the hosted auth.js before saving, and Submissions stay private to the owner by default (orders, RSVPs, sign-ups, personal details); agents write with the Simple Host connector or, without it, an API key from email-code registration.

Plan what to build on Website Deploy (simple-host.app). Helps a user decide whether their idea fits the static + light-backend model, maps it to concrete patterns (Page info the owner writes, Submissions visitors send, Personal records each visitor keeps, Shared boards a group edits, localStorage, public APIs), and produces a focused prompt for an implementation agent. Knows the planning rules that matter - every site lives at its own address, https://<site>.<handle>.simple-host.app/, where visitors sign in (Google or an emailed code) before saving from a page; saved data nobody declared is Shared (public), and Page info or Submissions are declared once; anything personal (orders, RSVPs, sign-ups) goes in Submissions, private to the owner by default; a free <name>.simple-host.app or a custom domain is an optional nicer address. Use when a user is starting a new site or describes a feature idea and needs help mapping it to what the platform can do.