Trial-and-Error

A repo with no visible cron workflow isn’t proof there’s no automated publishing. The schedule and generation logic can live entirely outside the repo, on Claude’s side.

The repo can have its CNAME file and the Pages API can have its cname field set — but without an actual DNS record at the registrar, certificate issuance stays blocked.

It’s easy to assume GitHub Pages only really serves one thing per account. In practice it’s the CNAME file that decides routing.

An English-facing site had commits piling up in Korean. Switching new commits to English seemed simple, until one easy-to-miss spot turned up.

Two options came up first — an API key in localStorage, or a Cloudflare Worker proxy — and neither was it. A GitHub-issue trigger pattern was requested instead.

The install command exits clean and the files exist on disk, but the skill still won’t show up in the session — check the path first.

An extensionless relative link like lab renders fine locally but 404s under GitHub Pages’ pretty URLs.

A project folder named CTI trips up both create-next-app and vercel deploy on name validation.

Installing remark-math + rehype-katex exactly by the book still breaks the build, because braces inside $$...$$ get parsed as JSX expressions.

Every plausible-looking ID like 01-foundations/01-cryptography/index turned out wrong. The real ID was sitting in the build output the whole time.