CLAUDE.md — working in farholm-site

Farholm is a static Eleventy marketing site (Nunjucks pages + blog/*.md advice posts) served by a thin Cloudflare Worker (worker.js: security headers/CSP, host redirects, /api/contact, /api/health). No app backend.

Full orientation already lives in README.md (stack, file map, deploy, hosts, compliance) and RUNBOOK.md — read those first. Don’t duplicate them here.

Golden rules

• Verify before claiming done. The deploy gate is npm run verify (npm ci && check && test && build && check:output). Run it — or at least npm run check && npm test && npm run check:output — before committing. Cloudflare won’t deploy if it fails and main is protected.
• Never hand-edit _site/ — it’s generated. Edit source.
• Anything site-facing is brand-governed. Before writing or editing pages, sections, copy, cards, testimonials, OG images, PDFs, or email, consult the farholm-brand skill (color tokens, Young Serif / Albert Sans, CSP + accessibility guardrails) so it stays on-brand rather than generic.
• Compliance is live, not placeholder. The Seller-of-Travel disclosure, CST number, and the FL/WA/HI state exclusions in the contact form are real — see README → “Compliance & legal” before touching them.
• Local preview: npm run serve (Eleventy) or npm run dev (build + wrangler dev, exercises the Worker).

AI tooling / installed plugins

Three plugins are installed — gstack, claude-mem, superpowers — and they overlap heavily (each ships its own planning system; two add memory). Don’t run the competing systems at once. Recommended division of labor:

• superpowers — default process layer. Use its skills as guardrails: brainstorming before new pages/features, writing-plans / executing-plans for multi-step work (e.g. the Google Ads landing pages), systematic-debugging and test-driven-development for Worker logic — the breakable code here (host redirects, /api/contact, the output link-checker), and verification-before-completion, which in this repo means npm run verify.
• claude-mem — navigation & recall only. smart-explore for token-cheap structural search, mem-search to recall how past work was done, learn-codebase to prime a fresh session. Keep the existing file-based project memory (the memory/MEMORY.md index) as the source of truth — don’t maintain a second parallel memory store.
• gstack — selective design/review/ship gates, not the full 23-role sprint. Most useful here: /design-review and /design (pair with farholm-brand), /review and /qa before shipping a page, /ship or /land-and-deploy for the Cloudflare deploy, /office-hours for “what should I do next.” Its headless browser skill can dogfood the live/preview site.

For a typical task (new advice post or landing page): brainstorming → consult farholm-brand → writing-plans if multi-step → build → /design-review + npm run verify → ship.