AI Built Website

Paste the prompt and the agent asks you for one thing: a Telegram bot token. Getting it takes half a minute and happens entirely inside Telegram — message @BotFather, send /newbot, pick a name, copy the token it answers with. Paste that token to your agent, and it stores it and locks the bot to you:

TELEGRAM_BOT_TOKEN=123456789:AAF...
TELEGRAM_ALLOWED_USERS=987654321   # your numeric ID — ask @userinfobot

The agent restarts its gateway and your bot comes alive. Say hi to it — anyone not on the allowed list is denied by default, so the bot answers you and nobody else.

Two things only you can do: pick a domain (buy it anywhere — Cloudflare Registrar sells at cost) and give the agent permission to manage that domain’s DNS. The permission is a Cloudflare API token, and the agent tells you exactly which buttons to click — the “Edit zone DNS” template, limited to just your domain, so the token can’t touch anything else. Paste it to your agent:

CF_API_TOKEN=v1.0-abc...
CF_ZONE_ID=023e105f4ecef8ad9ca31a8372d0c353

From now on the agent manages DNS itself with one API call — this is what it runs when you say “point the domain at the server”:

curl -X POST "https://api.cloudflare.com/client/v4/zones/$CF_ZONE_ID/dns_records" \
  -H "Authorization: Bearer $CF_API_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"type":"A","name":"mysite.com","content":"<your-pocketcorp-ip>","proxied":false}'

The agent installs nginx — the web server that answers your visitors — and certbot, which fetches the free HTTPS certificate and renews it forever. One tidy folder per site:

server {
    server_name mysite.com;
    root /var/www/mysite.com;
}

# enable it, then let certbot add HTTPS + the redirect:
# ln -s ../sites-available/mysite.com /etc/nginx/sites-enabled/
# certbot --nginx -d mysite.com

The prompt has the agent write its own operating manual — the difference between “an agent that can code” and “an agency that ships”. It encodes stack defaults, the deploy path, and the golden rule: never claim “done” without a screenshot of the live site:

---
name: site-builder
description: Build, deploy and iterate websites on this server
---

## Defaults
- One git repo per site at ~/sites/<domain>. Every change = commit.
- Static-first: plain HTML + Tailwind (CDN) or Astro if a build
  step is justified. No framework unless asked.
- Deploy = copy build output to /var/www/<domain>, then
  nginx -t && systemctl reload nginx. NEVER reload without the test.

## Verify loop (non-negotiable)
- After every deploy: screenshot https://<domain> with Playwright
  and send it to me with the live URL.
- If the screenshot does not match what I asked, fix and repeat
  before replying. Max 3 loops, then ask.

## DNS
- New domains: create the A record via the Cloudflare API
  (CF_API_TOKEN in env), verify with dig before claiming success.

Now the whole workflow is conversational:

This is where Hermes differs from a one-shot site generator. After the first successful deploy, it saves what worked — your taste, the deploy quirks, the nginx layout — via its skill_manage tool, refining the site-builder skill from experience. The second site you ask for skips every mistake the first one taught it.

Prefer not to host on your own box? The same skill works with edge hosts — swap the deploy line for `wrangler pages deploy dist/` (Cloudflare Pages, free, doesn’t even consume build minutes via direct upload) or `netlify deploy --prod`. Your Pocketcorp stays the brain; the edge serves the bytes.