-
Notifications
You must be signed in to change notification settings - Fork 2
Troubleshooting
Say something concrete: "help me build my portfolio", "my site looks like AI made it", "why is my Open Graph image not showing". If your agent has a skills list, confirm Foreman is enabled. In Claude Code, /plugin list.
If it triggers but starts writing HTML immediately, it loaded the file but is not following it. Say "run the playbook, do not write code yet."
This is the failure mode the skill most wants to avoid, and it is worth reporting. Tell it: "do not explain the process, just ask me the first question."
Usually one of three things. A package manager mismatch, such as a package-lock.json in a pnpm project. A case sensitive import path that only breaks on Linux. A Node version difference between your machine and the host.
One of the two DNS records is missing or still pointing at the registrar's parking page.
The certificate has not been issued yet. Wait, then check in incognito before changing anything. Changing records during issuance restarts the clock.
Cache, or a stale build. Confirm the host actually rebuilt from your latest commit before debugging the code.
Sharing platforms cache aggressively. Confirm og:image is an absolute URL, not a relative path, then use the platform's own sharing debugger to refresh it once.
Common with single page app fallbacks. It quietly tells crawlers that every missing page exists. Check the host's configuration for a real 404 status.
Almost always the hero image. Export at no more than twice the displayed width, use AVIF or WebP, set explicit width and height, and cap hero media at 1.5 MB with a poster fallback.