Menu
Build and run a Basil server against a scratch site to observe changes at the real HTTP surface.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | verify |
| description | Build and run a Basil server against a scratch site to observe changes at the real HTTP surface. |
go build -o $SCRATCH/basil ./cmd/basil
verify-site/
basil.yaml
site/home/index.pars # put pages in subdirs — a root site/index.pars
# is a catch-all handler and swallows 404s
Minimal page: <!DOCTYPE html> then <html><body><h1>"Text"</h1></body></html>
(Parsley: text content must be quoted).
cd verify-site && $SCRATCH/basil --dev --port 8085
Dev mode serves HTTP on localhost; browser tools can open it directly. Note: handler errors show the detailed dev error page, not the production 500 page; 404s show the real production 404 page (no root handler → 404).
Production requires https.auto: true + email, or manual cert/key.
Self-signed works for curl (-k); the in-app browser refuses it, so
capture bodies with curl and screenshot them via a static server:
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 2 -nodes -subj "/CN=localhost"
server:
host: localhost
port: 8443
https: {auto: false, cert: ./certs/cert.pem, key: ./certs/key.pem}
site:
path: ./site
curl -ks https://localhost:8443/whatever
let x = definitelyNotDefined.pkill -f "$SCRATCH/basil" — shell job control (%1)
doesn't survive across Bash tool calls, and a stale server holding the
port makes the next launch die with "address already in use" while curl
happily talks to the old binary.[WARN]/[ERROR].Run the project Definition of Done for the current unit of work and integrate it — build, test, verify, docs/changelog, commit, rebase, merge to main, push, and remove the worktree. Use when a piece of work is finished and should land on main. Merge model is direct-to-main (no PR).
Develop and test Basil web applications with HTTP handlers, routing, sessions, authentication, databases, and interactive components (Parts).
How to write Parsley code for tests, examples and documentation.