For end users

Install

Setting up Pectus on your laptop, including swapping in over an existing site.

• Why is the install driven by Claude Code?
  An agent reading the install steps out loud handles signups, errors, and OAuth dances better than a setup guide.
• Can I use Pectus without Claude Code?
  Yes. Read pectus.md as a manual install guide and run each step yourself.
• Can I plug in my org's hosted Supabase, GitHub, Vercel?
  Yes. The connect commands accept existing project credentials.
• What if I don't have GA4 / Search Console / ad data yet?
  Skills declare what they need. The bundled content skills run on whatever signals you have, with seed keywords as the starting topic spine.
• I already have a site on Vercel + GitHub. How do I replace it (or add to it) with Pectus?
  Two paths: reuse your existing repo or use a new repo and switch Vercel's git source. The new-repo path is recommended.
• I'm getting errors running the migration SQL in Supabase. What do I do?
  Find the SQL Editor in the Supabase sidebar, clear the editor before pasting, and the fixes for the three or four common errors.
• GA4 says "this user doesn't exist" when I try to add my service account. Why?
  Three causes in order of likelihood: GA4 Admin API not enabled, mangled email (missing project ID suffix), or cross-account mismatch.
• The CMS won't start. It says "Your project's URL and Key are required to create a Supabase client!"
  Three causes: wrong env var names in .env.local, dev server started before env was finalized, or .env.local in the wrong folder.
• I forgot the admin password I set in step 6. How do I recover it?
  Reset it from Supabase Authentication → Users. Pectus doesn't store the password; only Supabase does, and only as a one-way hash.