AI Built WebsiteAI Built WebsiteAI Built Website

Create a bot with @BotFather in Telegram (30 seconds — /newbot, pick a name, copy the token). Hermes reads channel credentials from its .env:

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

Restart the gateway (hermes gateway) and say hi to your bot. Unlisted users are denied by default — the bot is yours alone.

Buy a domain anywhere (Cloudflare Registrar sells at cost), manage its DNS on Cloudflare’s free plan, and create an API token with the “Edit zone DNS” template scoped to just that zone. Give it to Hermes:

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}'

Caddy turns HTTPS into a non-event: one block per domain, certificates fully automatic. Ask Hermes to install it (apt install caddy) and adopt this structure:

mysite.com {
    root * /var/www/mysite.com
    file_server
}

# every additional site = three more lines

This file is the difference between “an agent that can code” and “an agency that ships”. It encodes stack defaults, the deploy path, and the verification loop:

---
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
  caddy validate && caddy reload. NEVER reload without validate.

## 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 Caddy 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.