Site Launch Checklist

Site Launch Checklist

Pre-launch audit and setup workflow for shipping a new website. Opinionated for Cloudflare DNS + Vercel hosting + PostHog + Legal context.

Interaction style (READ FIRST)

This skill is intentionally interactive. Use `ask_user_input_v0` aggressively instead of assuming. Ask one question at a time with 2-4 tappable options. The user will tap, not type.

Always ask these questions at the start of a run (one at a time, in this order):

1. Site type: doc-site | marketing/lead-gen | SaaS-app | training/paid-course | personal-portfolio 2. Migration: greenfield-new-domain | migration-need-301-redirects | replacing-existing-on-same-domain 3. Multilingual: single-locale | en | fr+en | other-multi 4. PostHog setup: hogpost.samber.dev | set-up-new-proxy | skip-PostHog 5. AI scraper policy: use-default-for-site-type | customize-per-bot | block-all 6. Browser tool available: claude-chrome-extension | playwright | neither-skip-browser-checks

Ask again at every decision point throughout the phases, including:

• Whether to install Sentry / BetterStack / Crisp (depends on site type, ask explicitly)
• www vs apex canonical preference (most sites: apex; ask anyway)
• Which AI bots to allow if user chose customize-per-bot
• CSP tightness level: strict-default-src-none | balanced-allow-self | permissive-for-marketing
• Whether to skip a phase entirely (e.g., skip Phase 3 if non-FR site)

Never proceed past a decision point without explicit user input. Verbose checklists without checkpoints are not the goal.

Never install any MCP server or skill without explicit user confirmation. Always ask via ask_user_input_v0 before running npx skills add, claude mcp add, or any equivalent install command — even when the skill selection workflow proposes a curated subset.

How to use this skill

1. Run the start-of-session questions above. 2. Walk the user through phases 1-10 in order. For each phase: a. List items, ask if any should be skipped. b. For each remaining item, run the verification command (see "Verification tools" below). c. Report pass/fail. On fail, ask the user if they want to fix now or queue for later. 3. End with a status report grouped by phase, with blockers, recommended fixes, and optional improvements clearly separated.

Companion skills

Six skill packs are useful for site launches. Never install full multi-skill packs. The actual subset to install is decided at invocation time based on the site type the user confirms.

Pack inventory

Skill selection workflow (run at session start)

After the user confirms site type, for each pack relevant to that site type:

1. List available sub-skills: npx skills add owner/repo --list 2. Propose a curated subset based on site type and the phases this skill will execute. Match each phase's needs to specific sub-skills the listing returns. 3. Confirm with the user via ask_user_input_v0. Use multi-select when the proposed list has more than 3 items, single-select (install-as-proposed | let-me-modify | skip-this-pack) otherwise. 4. Bulk install the agreed subset: npx skills add owner/repo --skill A B C

Rules:

• Sub-skill names live in the pack, not in this SKILL.md. Always query --list for the current state. Pack contents change.
• Never run npx skills add owner/repo without --skill (that installs everything).
• Site type → packs mapping (which packs to enumerate, sub-skills still selected per workflow):
• doc-site: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills, devmarketing-skills
• marketing/lead-gen: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills, marketingskills
• SaaS-app: all six
• training/paid-course: claude-seo, web-quality-skills, trailofbits, marketingskills
• personal-portfolio: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills (lightweight subset)
• If the user later requests a phase that needs a sub-skill not yet installed, run the workflow again for that single sub-skill rather than re-installing the whole subset.

This avoids importing 80+ skills the user does not need, avoids going stale on sub-skill names, and avoids overfitting to a single pack version.

When delegating during a phase, do not duplicate work this skill orchestrates. Call the specialist with a narrow scope (e.g., "run only the security headers sub-audit on URL X").

Copywriting voice and humanizer pass

Every site has visible marketing copy (hero, features, CTAs, meta descriptions, OG descriptions, blog posts, 404 page text). Two layers of polish are mandatory before launch:

1. Define TONE.md once per site

Ask the user (ask_user_input_v0): "Does this site already have a TONE.md?" (yes-already-exists | no-create-from-template | skip-use-default).

If creating: write it to .agents/TONE.md or repo root TONE.md. See references/templates.md (section "TONE.md template") for the structure.

TONE.md specifies: voice (terse, contrarian, etc.), forbidden patterns (e.g., "delve", "crucial", em dashes, AI-sounding openers), sentence length preference, audience reading level, examples of good and bad sentences from the user's own writing.

2. Run a humanizer pass in the matching language

After every drafting step (whether by a copywriting skill, by hand, or by Claude directly), run a humanizer to strip AI patterns.

Ask the user (ask_user_input_v0) for the site's primary audience language at the start of the session if not already known:

• english-global → npx skills add https://github.com/blader/humanizer --skill humanizer
• french → use samber/humaniseur-fr (custom French humanizer) or equivalent French-tuned skill
• other → install matching humanizer if available; otherwise the skill writes a short language-specific anti-pattern checklist inline

Apply the humanizer to: hero copy, feature descriptions, CTA buttons, meta descriptions, OG/Twitter card descriptions, blog posts, email signup confirmations, 404 page text. Skip for legal pages (mentions légales, CGV) since they have rigid wording requirements.

3. Always reference TONE.md when invoking copywriting skills

When delegating to any copywriting or content-writing sub-skill (selected at invocation per the skill selection workflow), include TONE.md in the prompt context. Pass voice constraints explicitly: "Follow .agents/TONE.md. Avoid the listed patterns. Apply the humanizer after drafting."

Browser interaction preference

Many checks require a real browser (Lighthouse runs, securityheaders.com scan, opengraph.xyz validation, Twitter card validator, mobile viewport, screen reader smoke, Network tab inspection).

Always prefer the Claude Chrome extension. Fall back to Playwright only if the Chrome extension is unavailable. If neither is available, ask the user (ask_user_input_v0) whether to skip browser checks entirely or wait until they enable one.

Verification tools

Most checks are doable from the command line without third-party services. Use these tools inline at every phase. Don't trust panels in Cloudflare/Vercel/Google dashboards alone, verify with curl.

DNS (Phase 1):

dig +short A example.com                          # A record
dig +short AAAA example.com                       # AAAA (IPv6)
dig +short MX example.com                         # MX (mail)
dig +short TXT example.com                        # SPF + verification TXT
dig +short TXT _dmarc.example.com                 # DMARC
dig +short TXT default._domainkey.example.com     # DKIM (selector varies)
dig +short CAA example.com                        # CAA
dig +dnssec example.com | grep RRSIG              # DNSSEC active

TLS / HTTPS (Phase 1):

curl -sIL https://example.com | head             # follow redirects
curl -sI https://www.example.com                 # check www handling
openssl s_client -showcerts -connect example.com:443 < /dev/null 2>/dev/null | openssl x509 -noout -dates

Headers (Phase 4):

curl -sI https://example.com | grep -iE 'content-security-policy|strict-transport-security|x-frame-options|x-content-type-options|referrer-policy|permissions-policy'
# Full header dump:
curl -sI https://example.com
# External graders:
curl -s "https://api.securityheaders.com/?q=https://example.com&followRedirects=on&hide=on" -I | grep -i 'x-grade'

SEO files (Phase 5):

curl -s https://example.com/robots.txt
curl -sI https://example.com/sitemap.xml
curl -s https://example.com/sitemap.xml | head -40
curl -s https://example.com/llms.txt
# Schema (JSON-LD):
curl -s https://example.com/ | grep -A 50 'application/ld+json'
# hreflang:
curl -s https://example.com/ | grep -i hreflang

Open Graph & social (Phase 6):

curl -s https://example.com/page | grep -iE 'og:|twitter:|<title|name="description"'

Favicons & manifest (Phase 7):

curl -sI https://example.com/favicon.ico
curl -sI https://example.com/favicon.svg
curl -sI https://example.com/apple-touch-icon.png
curl -s https://example.com/manifest.json | jq .

404 / 500 / redirects:

curl -sI https://example.com/this-does-not-exist
curl -sIL https://example.com/old-url     # verify 301 chain

Always run the relevant command, paste the output to the user when reporting, then ask (via ask_user_input_v0) whether to fix immediately or queue.

---

Phase 1: Domain & Infrastructure

Most of this is one-click via Cloudflare's dashboard if the domain is on Cloudflare.

Ask first: "Is the domain already on Cloudflare with the standard config from previous launches?" (yes-standard | yes-needs-review | no-fresh-setup)

Checklist:

• [ ] Cloudflare: proxy ON for apex + www, TLS 1.3 minimum, "Always Use HTTPS" enabled, HSTS preload enabled in Cloudflare SSL/TLS settings
• [ ] DNS A/AAAA or CNAME pointing to Vercel (verify with dig +short A example.com)
• [ ] MX records for Google Workspace (verify with dig +short MX example.com)
• [ ] SPF, DKIM, DMARC records (verify all 3 with the dig commands above)
• [ ] CAA records restricting cert issuance (verify with dig +short CAA example.com)
• [ ] DNSSEC enabled at registrar level (verify with dig +dnssec)
• [ ] Vercel: project linked to repo, prod + preview env vars set, custom domain attached, prod and preview aliases correct
• [ ] Decide www vs apex canonical, configure 308 redirect for the non-canonical (verify with curl -sIL https://www.example.com)
• [ ] Custom 404 page renders (verify with curl -sI https://example.com/does-not-exist)
• [ ] Custom 500 page exists (cannot easily verify without forcing an error, ask user)
• [ ] If migration: 301 redirect map for every old URL (loop verification with curl -sIL per URL)

Backups

If you don't configure backups at launch, you never will. Do it now.

Ask the user (ask_user_input_v0): "Which data stores does this app write to?" (database-only | database-plus-file-storage | file-storage-only | stateless-no-persistent-data). If stateless-no-persistent-data, skip this section.

Database:

• [ ] Automated daily backups enabled at the provider level (Neon, Supabase, PlanetScale, Railway, RDS — each has a one-click toggle). Verify by opening the backup panel and confirming the last backup timestamp is recent.
• [ ] Retention policy set to ≥30 days
• [ ] Point-in-time recovery (PITR) enabled if available (Neon, Supabase, RDS all support it)
• [ ] Off-site copy: if the provider stores backups in the same region as the primary, configure cross-region replication or a nightly export to a separate storage account (S3, R2, GCS)
• [ ] Restore drill performed before launch: pick a recent backup, restore to a staging database, verify row counts and a sample query. A backup you haven't tested is not a backup.

File storage (if applicable — S3, R2, GCS, Cloudflare Images):

• [ ] Versioning enabled on the primary bucket
• [ ] Cross-region replication or a scheduled sync to a secondary bucket. Backblaze B2 is a cheap, reliable option for off-site copies (significantly cheaper than S3/GCS egress). Use rclone to sync from S3/R2/GCS → B2 on a daily cron.
• [ ] Lifecycle rule: transition old versions to cheaper storage after 30 days, delete after 90 days (adjust to cost tolerance)

Secrets / environment variables:

• [ ] All env vars documented and stored in a secrets manager (1Password, Doppler, Vault, or equivalent). Not in a .env file on someone's laptop.
• [ ] Verify: if every engineer's machine burned tonight, could a new team member restore prod from scratch using only the secrets manager + git?

Monitoring:

• [ ] Set up an alert (email or Slack) if the daily backup job fails. Most providers support this natively; configure it before closing the backup panel.

---

Phase 2: Analytics & Observability

Most third-party integrations are one-click via Cloudflare or Vercel.

For the conditional tools (Crisp, Sentry, BetterStack), use `ask_user_input_v0` to confirm per site type. See references/decisions.md for the observability tier matrix.

Always-on:

• [ ] Google Analytics 4: property created, measurement ID embedded, gated behind CNIL consent
• [ ] PostHog: based on user's earlier answer:
• If hogpost.samber.dev: configure client with api_host: "https://hogpost.samber.dev" and verify CORS allows the new domain (test with browser console or curl -H "Origin: https://newsite.com" -I https://hogpost.samber.dev/decide)
• If set-up-new-proxy: add path rewrite in next.config.js to us.i.posthog.com and us-assets.i.posthog.com, init client with api_host: "/ingest"
• If skip-PostHog: skip
• [ ] Google Search Console: site verified (DNS TXT or HTML file), sitemap submitted
• [ ] Bing Webmaster Tools: site verified, sitemap submitted, IndexNow key file at /{key}.txt on root (verify with curl -sI https://example.com/{key}.txt)
• [ ] Ahrefs: site added to dashboard for tracking
• [ ] Add the site to the internal stats spreadsheet (PostHog properties registry + GitHub Sponsors tracking sheet if applicable)

Brand monitoring (Google Alerts):

For each alert, use these settings: Frequency: once a day | Sources: Automatic | How many: All results | Region: Any region

Set up one alert per keyword via alerts.google.com:

• [ ] Domain name (e.g., example.com)
• [ ] Brand or product name (quoted if multi-word, e.g., "My Brand")
• [ ] Key feature or library names if the site documents a project
• [ ] Competitor brand names (optional — ask user via ask_user_input_v0: yes-monitor-competitors | skip)

Ask the user: "Which additional keywords to monitor?" (product-name-only | domain-plus-brand | full-set-with-competitors | custom-list)

Developer community monitoring (F5bot) — for `doc-site` and `SaaS-app` targeting developers:

F5bot (f5bot.com) monitors Reddit, Hacker News, and Lobste.rs for keyword mentions and sends email alerts. Free, no API required.

Set up one keyword per line at f5bot.com/add:

• [ ] Brand or product name
• [ ] Domain name (catches link shares)
• [ ] Key feature or library names
• [ ] Common misspellings if applicable

Competitor analysis (`marketing/lead-gen`, `SaaS-app`, `training/paid-course` only):

Before writing copy, setting up ads, or planning content, run a competitor analysis to understand what is already working in the market — positioning, messaging angles, CTA patterns, pricing presentation, and content strategy.

Use a deep research tool or a competitor analysis skill if one is available in the toolchain. Ask via ask_user_input_v0:

• "Do you already have competitor names/URLs to analyze?" (yes-provide-list | no-discover-for-me | skip)
• If yes-provide-list: ask the user to paste 2-5 names or URLs (free text)
• "What are we looking to extract?" (positioning-and-messaging | pricing-strategy | content-and-seo | full-spectrum)

Feed the output into:

• Phase 5 keyword strategy (target queries they rank for but you can outrank or flank)
• TONE.md voice calibration (deliberately differentiate from the dominant tone in the category)
• Phase 6 OG copy and CTA language (borrow proven frames, don't clone verbatim)
• Copywriting sub-skills invoked later (pass the competitor snapshot as context)

Conditional (ask user, default per site type from `references/decisions.md`):

• [ ] Crisp
• [ ] Sentry
• [ ] BetterStack

---

Phase 3: Legal & Compliance (FR)

Ask first: "Is this site subject to French law?" (yes-FR-operator-or-audience | no-EU-only | no-non-EU). If no, ask whether GDPR or equivalent applies and adjust.

For FR sites:

• [ ] Mentions légales page (mandatory, fines up to 75k€ per omission)
• [ ] CGV (Conditions Générales de Vente) if commercial activity
• [ ] Privacy policy
• [ ] Terms of service
• [ ] CNIL-compliant cookie consent that gates GA4, PostHog, Crisp, Sentry script loading (not just a banner that always loads trackers). Use a CMP (Axeptio, Tarteaucitron, or custom). Verify with browser Network tab: no tracker fires before explicit consent.

---

Phase 4: Security

Delegate the deep audit to trailofbits/skills. The items below are the must-pass checklist.

Ask first: CSP tightness level (strict-default-src-none | balanced-allow-self | permissive-for-marketing). See references/templates.md for the CSP template per level.

• [ ] CSP: target chosen tightness level. No 'unsafe-inline' for scripts (use nonces). Verify with curl -sI ... | grep -i content-security-policy.
• [ ] HSTS: max-age=31536000; includeSubDomains; preload. Submit to hstspreload.org. Verify with curl -sI ... | grep -i strict-transport.
• [ ] X-Frame-Options: DENY
• [ ] X-Content-Type-Options: nosniff
• [ ] Referrer-Policy: strict-origin-when-cross-origin
• [ ] Permissions-Policy: deny camera, microphone, geolocation, payment unless used
• [ ] Run all headers in one go: curl -sI https://example.com | grep -iE 'content-security|strict-transport|x-frame|x-content-type|referrer-policy|permissions-policy'
• [ ] securityheaders.com: target A+ (verify via Claude Chrome extension or curl https://securityheaders.com/?q=URL and parse)
• [ ] observatory.mozilla.org: target 90+ (via Chrome extension)
• [ ] Run trailofbits/skills security audit on the codebase
• [ ] Verify no leaked secrets in client bundle: open Chrome DevTools Network tab via Claude Chrome extension, grep response bodies for sk_, pk_, AKIA, ghp_, Bearer

---

Phase 5: SEO & GEO

Delegate the full audit to AgriciDaniel/claude-seo. The items below are the orchestration list.

See references/templates.md for robots.txt, llms.txt, and manifest.json templates. See references/decisions.md for the AI scraper policy matrix by site type.

• [ ] /robots.txt present, references sitemap (verify with curl -s https://example.com/robots.txt)
• [ ] /sitemap.xml present, valid (verify with curl -s https://example.com/sitemap.xml | head -40). Sitemap-index with per-language sitemaps if multilingual.
• [ ] /llms.txt present (per llmstxt.org spec, verify with curl -s https://example.com/llms.txt)
• [ ] AI scraper policy encoded in robots.txt. Apply the matrix from references/decisions.md based on site type, then ask user via `ask_user_input_v0` to confirm each non-default decision.
• [ ] Schema markup (JSON-LD): Organization + WebSite + BreadcrumbList site-wide; per-page types where applicable (SoftwareApplication for lib homepages, Article for blog posts, FAQPage for FAQs, Person for author bio). Verify with curl -s URL | grep -A 50 'application/ld+json'. Validate structured data via Google Rich Results Test (<https://search.google.com/test/rich-results>) and Schema.org Validator (<https://validator.schema.org>) — Rich Results Test checks eligibility for rich snippets; Schema.org Validator catches spec violations that Google may silently ignore.
• [ ] Meta tags per page: unique <title> (50-60 chars), unique <meta description> (150-160 chars), <link rel="canonical">, <meta name="robots"> if needed
• [ ] hreflang tags on every page if multilingual (every language version declares all alternates including self). Verify with curl -s URL | grep -i hreflang.
• [ ] Keyword analysis using both Google Trends and Ahrefs (they answer different questions, not interchangeable):
• Google Trends (trends.google.com): trajectory (rising vs declining), geographic distribution (especially FR vs international split), seasonal patterns, related queries breakout, head-to-head comparison of 2-5 candidate keywords. Use Trends to validate direction and timing of the SEO bet.
• Exploding Topics (explodingtopics.com): surfaces emerging trends weeks or months before they peak in Google Trends. Use to identify rising queries before competition solidifies and to validate that target keywords aren't already on the decline.
• Answer The Public (answerthepublic.com/en): maps search questions, comparisons, and related queries around a seed keyword. Use to uncover long-tail intent clusters, populate FAQ schema, and identify content gaps.
• Ahrefs Keywords Explorer: monthly volume, keyword difficulty, SERP analysis, CPC, parent topic, traffic potential. Use Ahrefs to size the opportunity in absolute terms.
• Combined output: a ranked shortlist of 3-5 target queries per page, with rationale (volume × difficulty × trajectory × intent match).
• Delegate to whichever keyword-research sub-skill was installed at session start (selected from the installed packs via the skill selection workflow; typical sources are the SEO+GEO and marketing packs).
• [ ] AI visibility audit via productrank.ai: open productrank.ai in a browser, submit multiple category or product searches, run the full AI SEO report. It audits how the site appears in AI-generated answers (ChatGPT, Perplexity, Gemini, Claude). Flag any zero-visibility categories and surface content gaps the AI graders identify.
• [ ] Typo and grammar pass on all visible text content
• [ ] Backlink profile audit: run Ahrefs Backlink Checker and Moz Link Explorer to assess domain authority and surface toxic or broken inbound links before launch — especially critical on migrations to ensure old-domain equity transfers correctly
• [ ] Internal linking audit: every important page reachable in ≤3 clicks from the homepage

---

Phase 6: Open Graph & Social Preview

Verify all OG and Twitter tags with: curl -s URL | grep -iE 'og:|twitter:'

• [ ] og:title, og:description, og:url, og:type, og:site_name
• [ ] og:image 1200×630px, absolute URL, og:image:width and og:image:height declared, og:image:alt set
• [ ] Per-page `og:image`, not one global. For doc sites: generate dynamically from page title. For blog posts: per-article custom image.
• [ ] og:locale + og:locale:alternate for each language if multilingual
• [ ] Twitter Cards: twitter:card=summary_large_image, twitter:title, twitter:description, twitter:image, twitter:site (handle)
• [ ] Validate with opengraph.xyz (covers FB, LinkedIn, Slack, Discord, WhatsApp previews) via Claude Chrome extension
• [ ] Validate with Twitter's card validator
• [ ] Manual check: paste URL in a LinkedIn DM, a Slack channel, a Discord, an iMessage. Preview must render correctly in all.

---

Phase 7: Favicons & Web Manifest

See references/templates.md for the manifest.json template.

Generate from a single 1024×1024 source PNG using realfavicongenerator.net or favicon.io.

Minimum modern set:

• [ ] /favicon.ico (multi-res 16/32/48). Verify with curl -sI https://example.com/favicon.ico.
• [ ] /favicon.svg with embedded <style>@media (prefers-color-scheme: dark) { ... }</style> for dark mode. Verify with curl -sI https://example.com/favicon.svg.
• [ ] /favicon-96x96.png (PNG fallback)
• [ ] /apple-touch-icon.png 180×180px, no transparency, opaque background. Verify with curl -sI.
• [ ] /web-app-manifest-192x192.png (Android PWA icon)
• [ ] /web-app-manifest-512x512.png (Android splash)
• [ ] /manifest.json referencing both PNGs, with theme_color, background_color, name, short_name, display. Verify with curl -s https://example.com/manifest.json | jq ..

Skip (deprecated):

• mstile-*.png (Windows tiles)
• safari-pinned-tab.svg (deprecated since macOS Big Sur)
• favicon-16x16.png / favicon-32x32.png (covered by .ico and .svg)

HTML head verification:

curl -s https://example.com/ | grep -iE 'rel="icon"|rel="apple-touch-icon"|rel="manifest"'

---

Phase 8: Quality Gates

Delegate to addyosmani/web-quality-skills. The skill covers 150+ Lighthouse audits across performance, accessibility, SEO, and best practices.

• [ ] Unlighthouse site-wide crawl: npx unlighthouse --site {site} — crawls all pages and runs Lighthouse on each. Surface pages below 90 on any axis before the per-URL checks.
• [ ] Lighthouse all 4 axes, mobile mode: target ≥90 on each (perf, a11y, best practices, SEO)
• [ ] Lighthouse all 4 axes, desktop mode: target ≥95 on each
• [ ] Core Web Vitals field data (CrUX via PageSpeed Insights): LCP < 2.5s, INP < 200ms, CLS < 0.1, on both mobile and desktop
• [ ] Accessibility (WCAG 2.2 AA via web-quality-skills): keyboard nav works for every interactive element, focus rings visible, color contrast ≥4.5:1 for text, all images have alt, heading hierarchy is monotonic (H1 → H2 → H3), ARIA labels on icon-only buttons
• [ ] Real mobile device test (not just devtools emulator). Use Claude Chrome extension on mobile viewport on a real device or BrowserStack.
• [ ] Cross-browser smoke test: Chrome, Safari, Firefox latest stable
• [ ] Print stylesheet sanity (Cmd+P should not break layout)

---

Phase 9: Ecosystem Cross-linking

Internal cross-linking between owned properties. High-leverage SEO action for any multi-domain owner.

Ask the user: "List the other domains in your ecosystem that are topically relevant to this new site." Then for each one:

• [ ] Add a link from the existing site (footer / nav / "other projects" section) to the new site, where topically relevant
• [ ] Add a link to the new site in the README of the matching GitHub repo, if it documents a library
• [ ] Verify reciprocal links: every link added points back where appropriate
• [ ] If the new site documents a Go lib, link from related lib docs

Do not over-link. Only cross-link where topically relevant. A doc site for a logging lib should not link to a personal blog about cycling.

---

Phase 10: Set up weekly SEO maintenance sub-agent

After launch, set up a Hermes agent or Claude Cowork agent that runs weekly to monitor SEO health and surface action items.

See references/weekly-seo-agent.md for the full agent definition. Copy it into .claude/agents/weekly-seo.md in the site's repo (or a dedicated ops repo). The agent uses these MCP connectors:

• Ahrefs MCP (backlinks, rankings, keywords)
• PostHog MCP (analytics correlation, AI bot traffic)
• Web search (SERP monitoring, competitor checks)
• Google Search Console (via community MCP or curl with service account credentials)

Ask the user via ask_user_input_v0: "Set up the weekly SEO agent now?" (yes-create-agent-file | yes-but-defer | skip-for-now).

When MCP are not available, use Claude for Chrome extension.

---

Output format

At the end of a full run, output a status report grouped by phase:

Phase 1: Domain & Infrastructure  [9/10 pass]
  ✓ Cloudflare proxy on
  ✓ DNS records configured
  ...
  ✗ DMARC missing. Fix: add TXT record at _dmarc.example.com with policy v=DMARC1; p=quarantine;...

Phase 2: Analytics & Observability  [6/7 pass]
  ...

Followed by three lists, in order:

1. Blockers (must fix before launch) 2. Recommended fixes (should fix before announcing) 3. Optional improvements (post-launch)

End by asking via ask_user_input_v0: "Which list do you want to tackle next?" (blockers | recommended | optional | done-for-now).

---

References

• references/decisions.md: AI scraper policy matrix by site type, observability tier matrix
• references/templates.md: robots.txt, llms.txt, manifest.json, CSP templates per tightness level, security headers reference
• references/weekly-seo-agent.md: Full definition of the weekly SEO maintenance sub-agent (MCPs, tasks, output format)

Decisions and matrices

Repeating decisions for site launches. Apply the matrix based on the site type the user confirmed at the start of the session. When a decision is ambiguous or borderline, ask the user via ask_user_input_v0 rather than assuming.

AI scraper policy by site type

Decide which AI training and AI-search crawlers to allow per site type. Encode the decision in robots.txt (see templates.md).

Marketing / lead-gen page (consulting, training landing)

Allow all AI scrapers. Your conversion copy is intellectual property; training it into LLMs that may recommend competitors is anti-value. But AI citations on a sales page is good.

Paid course / training page

Block all. Content is the product.

Personal portfolio / personal blog

Allow the citing crawlers (ClaudeBot, GPTBot, PerplexityBot, Google-Extended). Useful for "who is X" or "what does X work on" queries.

SaaS app

• App subdomain (e.g., app.example.com): block all AI scrapers. The app is gated, no value in scraping.
• Landing / marketing subdomain: apply the marketing rules above.

Default when site type is unclear

Block all. Ask the user. Better to surface the decision than to silently expose content to crawlers.

---

Observability tier by site type

Decide which analytics and observability tools to install. Always confirm conditional tools with ask_user_input_v0.

Doc site / lib homepage

Marketing / lead-gen

All of the doc-site tools, plus:

SaaS app

All of the above, plus:

Personal portfolio

---

www vs apex canonical

Default: apex is canonical, www redirects to apex via 308.

Exception: if the site is hosted on a platform that requires CNAME (which cannot be set on apex per DNS RFCs), the platform's flattening / ALIAS / ANAME feature is used. Cloudflare handles this transparently with CNAME flattening, so apex remains canonical.

Verify with:

curl -sIL https://www.example.com
# Expect: 308 → https://example.com

---

CSP tightness level by site type

Three levels. Pick one with ask_user_input_v0 at the start of Phase 4.

strict-default-src-none

For doc sites, personal portfolio, SaaS app. Whitelist every source explicitly. No 'unsafe-inline'. Use nonces for any required inline scripts.

balanced-allow-self

For marketing pages with embeds (YouTube, Calendly, etc.). default-src 'self', then allow specific third parties.

permissive-for-marketing

Last resort for legacy marketing pages with many third-party scripts (HubSpot, Drift, etc.). Document why and plan to tighten.

See templates.md for the actual CSP strings per level.

---

When a decision is unclear

Always default to asking via ask_user_input_v0 with the matrix options as tappable choices. Never silently apply a guess.

Templates

File and header templates for site launches. Apply per the matrices in decisions.md.

robots.txt

Template: doc site for OSS lib (allow AI scrapers)

User-agent: *
Allow: /

Sitemap: https://EXAMPLE.com/sitemap.xml

# AI scrapers (per decisions.md: doc-site policy)
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Applebot-Extended
Allow: /

# Blocked low-value scrapers
User-agent: Bytespider
Disallow: /

User-agent: Amazonbot
Disallow: /

Template: marketing / lead-gen (block all AI scrapers)

User-agent: *
Allow: /

Sitemap: https://EXAMPLE.com/sitemap.xml

# Block all AI scrapers (per decisions.md: marketing policy)
User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Amazonbot
Disallow: /

Note: regular search engine crawlers (Googlebot, Bingbot) are not in the AI bot list and remain governed by the User-agent: * rule.

---

llms.txt

Per llmstxt.org spec. Place at root.

# Project Name

> One-line description of the project, written for an LLM consumer.

Markdown paragraph giving more context on what the project does, who it's for, and why it exists.

## Docs

- [Getting started](https://example.com/docs/getting-started): how to install and run the first example
- [API reference](https://example.com/docs/api): full API documentation
- [Examples](https://example.com/docs/examples): working code samples

## Optional

- [Changelog](https://example.com/changelog): version history
- [Contributing](https://github.com/owner/repo/blob/main/CONTRIBUTING.md): how to contribute

For richer LLM consumption, also publish llms-full.txt with the full content of all documentation pages concatenated.

---

manifest.json

Minimum modern PWA manifest. Place at root or /manifest.json.

{
  "name": "Site Full Name",
  "short_name": "Site",
  "description": "One-line description matching meta description.",
  "start_url": "/",
  "display": "standalone",
  "background_color": "#ffffff",
  "theme_color": "#000000",
  "icons": [
    {
      "src": "/web-app-manifest-192x192.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "maskable"
    },
    {
      "src": "/web-app-manifest-512x512.png",
      "sizes": "512x512",
      "type": "image/png",
      "purpose": "maskable"
    },
    {
      "src": "/web-app-manifest-192x192.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "any"
    },
    {
      "src": "/web-app-manifest-512x512.png",
      "sizes": "512x512",
      "type": "image/png",
      "purpose": "any"
    }
  ]
}

HTML <head> references:

<link rel="icon" href="/favicon.ico" sizes="any" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="apple-touch-icon" href="/apple-touch-icon.png" />
<link rel="manifest" href="/manifest.json" />
<meta name="theme-color" content="#000000" />

---

CSP templates

Three tightness levels. Pick per the matrix in decisions.md.

strict-default-src-none

For doc sites, personal portfolio, SaaS apps with bundled assets only.

default-src 'none';
script-src 'self' 'nonce-{NONCE}' https://hogpost.samber.dev;
style-src 'self' 'unsafe-inline';
img-src 'self' data: https:;
font-src 'self' data:;
connect-src 'self' https://hogpost.samber.dev https://eu.i.posthog.com;
manifest-src 'self';
base-uri 'self';
form-action 'self';
frame-ancestors 'none';
object-src 'none';
upgrade-insecure-requests;

Notes:

• style-src 'unsafe-inline' is unfortunately required by most modern frameworks (Tailwind in dev, styled-components, etc.). Tighten with hashes if feasible.
• Replace {NONCE} with a per-request random value generated server-side (Next.js middleware can do this).
• connect-src includes eu.i.posthog.com as a fallback if hogpost.samber.dev proxy is unavailable.

balanced-allow-self

For marketing pages with embeds.

default-src 'self';
script-src 'self' 'nonce-{NONCE}' https://hogpost.samber.dev https://www.youtube.com https://assets.calendly.com;
style-src 'self' 'unsafe-inline' https://assets.calendly.com;
img-src 'self' data: https:;
font-src 'self' data:;
connect-src 'self' https://hogpost.samber.dev https://*.calendly.com;
frame-src 'self' https://www.youtube.com https://calendly.com;
frame-ancestors 'none';
object-src 'none';
upgrade-insecure-requests;

Adjust embed origins as needed.

permissive-for-marketing

Legacy fallback. Add a TODO comment in the codebase to tighten in the next iteration.

default-src 'self' https:;
script-src 'self' 'unsafe-inline' 'unsafe-eval' https:;
style-src 'self' 'unsafe-inline' https:;
img-src 'self' data: https:;
font-src 'self' data: https:;
connect-src 'self' https:;
frame-ancestors 'none';
upgrade-insecure-requests;

---

Full security headers reference

Apply all of these in addition to CSP. Add to Vercel's vercel.json or Next.js next.config.js headers().

{
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        {
          "key": "Strict-Transport-Security",
          "value": "max-age=31536000; includeSubDomains; preload"
        },
        { "key": "X-Content-Type-Options", "value": "nosniff" },
        { "key": "X-Frame-Options", "value": "DENY" },
        {
          "key": "Referrer-Policy",
          "value": "strict-origin-when-cross-origin"
        },
        {
          "key": "Permissions-Policy",
          "value": "camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=()"
        },
        { "key": "Cross-Origin-Opener-Policy", "value": "same-origin" },
        { "key": "Cross-Origin-Embedder-Policy", "value": "credentialless" },
        { "key": "Cross-Origin-Resource-Policy", "value": "same-origin" }
      ]
    }
  ]
}

Notes:

• Cross-Origin-Embedder-Policy: credentialless is safer than require-corp for sites with third-party embeds.
• Permissions-Policy should enumerate every feature you want to deny, not rely on defaults.

Verify with:

curl -sI https://example.com | grep -iE 'strict-transport|x-content-type|x-frame|referrer-policy|permissions-policy|cross-origin'

---

Sitemap.xml structure

For multilingual sites, use a sitemap index referencing per-locale sitemaps.

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap><loc>https://example.com/sitemap-en.xml</loc></sitemap>
  <sitemap><loc>https://example.com/sitemap-fr.xml</loc></sitemap>
</sitemapindex>

Each per-locale sitemap declares xhtml:link alternates with hreflang:

<url>
  <loc>https://example.com/en/page</loc>
  <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/page"/>
  <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page"/>
  <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/page"/>
</url>

---

TONE.md template

Place at .agents/TONE.md or repo root. Fill in based on the user's writing samples and preferences.

# Tone of voice: [Site name]

## Audience

- Primary: [e.g., senior Go developers shipping production systems]
- Secondary: [e.g., engineering managers evaluating libraries]
- Reading level: [e.g., technical, no hand-holding]
- Language: [e.g., English, with some French for FR-specific pages]

## Voice

- Direct, dense, no filler.
- Contrarian when warranted.
- Data-grounded: claims need numbers or links.
- Concrete over abstract: prefer "200ms p95" to "fast".
- Assume reader has context, skip primers.

## Forbidden words and patterns

- AI-sounding openers: "In today's fast-paced world", "Let's dive into", "It's worth noting that".
- Vague adjectives: "crucial", "essential", "powerful", "robust", "comprehensive", "seamless", "innovative".
- Empty verbs: "delve into", "leverage", "utilize", "facilitate".
- Hedging: "might potentially", "may possibly", "kind of", "sort of".
- Em dash character ("—") forbidden. Use commas, parentheses, or two sentences.
- Marketing fluff: "game-changing", "revolutionary", "next-generation", "world-class".

## Required patterns

- One concrete example per claim.
- Numbers when possible. Prefer "20% faster" over "much faster".
- Code samples for technical content. Short, runnable, idiomatic.

## Sentence and paragraph rules

- Average sentence length: 12-18 words.
- Max paragraph length: 4 sentences.
- One idea per paragraph.
- Section headers are statements, not questions.

## Good examples (from existing content)

- "Product XYZ hit $1m ARR without paying for ads. The community wants feature-ABC done right."
- "Tool XYZ gives 50× benchmark speedups and 5% production gains. Both numbers are true. Only one matters."

## Bad examples (to avoid)

- "Product XYZ is a powerful, comprehensive productivity tool that leverages documentation to seamlessly empower designers."
- "In today's fast-paced development landscape, choosing the right productivity tool is crucial."

## Address form (FR only)

- `tu` vs `vous` must be chosen deliberately and applied consistently site-wide. Mixed forms on the same site are a copywriting error.
- Default by site type:
  - `doc-site` (OSS lib, developer tools): **tu** — developer community is informal; "vous" feels corporate and creates distance.
  - `SaaS-app` (B2B, enterprise): **vous** — default to formal unless the product targets solo developers or the brand is explicitly casual.
  - `marketing/lead-gen` (consumer-facing): **tu** if the audience is young or tech-savvy; **vous** if the audience is professional or older.
  - `training/paid-course`: **tu** — learning context is personal; "vous" creates unnecessary formality.
  - `personal-portfolio`: **vous** — professional register by default.
- Ask the user explicitly if the default does not fit: "Which address form?" (`tu` | `vous` | `already-specified-in-TONE.md`)
- Record the chosen form in TONE.md under `Address form: tu | vous` and enforce it in every copy review and humanizer pass.

## Localization notes

- FR content: use guillemets « » not quotes, use non-breaking spaces before `: ; ? !`, avoid anglicisms ("faire du sens", "adresser un problème").
- EN content: US spelling.

The skill should read TONE.md at the start of any copywriting task and pass its constraints to any delegated copywriting skill. After drafting, run the humanizer in the matching language.

Weekly SEO maintenance sub-agent

Definition for a Hermes agent or Claude Cowork agent that runs weekly post-launch to monitor SEO health and surface action items.

Setup

1. Copy the agent definition (the block at the bottom of this file) into .claude/agents/weekly-seo.md in the site's repo (or in a dedicated ops repo if you manage multiple sites). 2. Confirm the following MCP servers are connected in Claude Code / Cowork:

• Ahrefs MCP (required, for backlinks and rankings)
• PostHog MCP (required, for traffic correlation)
• Google Search Console (recommended, via community MCP such as gsc-mcp; if no MCP, fall back to curl with a service account credential file)
• Web search (built-in, for SERP feature checks and competitor monitoring)

3. Confirm the agent has access to the project source code if they apply to the site's content. 4. Schedule weekly execution. Three options:

• Cron + claude --dangerously-skip-permissions -p "/agents weekly-seo" (Linux/macOS, only if running in a trusted environment)
• Hermes agent
• Claude Cowork agent
• GitHub Actions weekly schedule, posting the report to a Slack channel
• Manual invocation each Monday morning

When MCP are not available, use Claude for Chrome extension or a browser

What the agent does

Run all 10 tasks below in one weekly pass. Each task produces a section of the final report.

1. Ranking changes (GSC + Ahrefs)

• Pull top 50 queries by impressions for the last 7 days from Google Search Console.
• Compare positions, impressions, clicks, and CTR to the prior 7 days.
• Flag any (page, query) pair that:
• Dropped more than 5 positions
• Lost more than 20% impressions
• Lost more than 30% clicks while position is stable (CTR collapse, often a SERP feature stealing clicks)
• Output: ordered list of (page, query, delta, hypothesis, recommended action).

2. Page-2 opportunities (GSC)

• Identify queries ranking positions 11 through 20 with more than 100 impressions in 7 days.
• For the top 5: fetch the current page 1 SERP via web_search and compare structure, depth, and recency of the top 3 results to the site's current content.
• Output: content gap analysis with specific edit suggestions (add FAQ section, expand introduction, add benchmark table, etc.).

3. New backlinks (Ahrefs MCP)

• Pull new referring domains acquired in the last 7 days.
• Categorize each: high authority (DR > 50), niche relevant (matches site topic), neutral, spam.
• Flag spam links for potential disavow file submission.
• Output: list of new links with category, plus a draft disavow line for any spam.

4. Lost backlinks (Ahrefs MCP)

• Pull referring domains lost in the last 7 days.
• For losses from domains with DR > 40 or known niche relevance: draft outreach email asking why and offering to fix any broken links.
• Output: list of lost links plus draft outreach for high-value losses.

5. Core Web Vitals drift (GSC + PageSpeed Insights)

• Pull the Core Web Vitals report from GSC (mobile and desktop separately).
• Compare to the prior week.
• Flag any URL group that crossed from "Good" to "Needs improvement" or "Poor".
• For each flagged group: run PageSpeed Insights via web_fetch on a representative URL and identify the failing metric (LCP, INP, or CLS) and likely cause.
• Output: list of affected URL patterns with proposed fixes.

6. Indexation health (GSC)

• Pull the Page Indexing report.
• Compare "Indexed" and "Not indexed" counts week-over-week.
• For new entries in "Not indexed", group by reason (Discovered not indexed, Crawled not indexed, Excluded by noindex, Soft 404, etc.).
• Output: per-reason summary with recommended fix.

7. AI bot traffic (PostHog MCP)

• Query PostHog for sessions where the user agent matches (GPTBot|ClaudeBot|PerplexityBot|Google-Extended|anthropic-ai|ChatGPT-User|CCBot|Bytespider|Amazonbot).
• Compare counts to the prior week, broken down by bot.
• If the site type is doc-site and counts are growing: positive signal, surface as a metric.
• If the site type is marketing/lead-gen or paid-course and any AI bot has nonzero traffic: verify robots.txt is actually blocking by fetching https://example.com/robots.txt and grepping for the bot. If it should block but isn't, this is a blocker.
• Output: per-bot weekly count with delta, plus blockers if any bot is reaching pages it should not.

8. Competitor SERP monitoring

• For the top 5 target keywords (configured per site in a YAML or JSON file the agent reads): capture the current top 3 SERP results via web_search.
• Compare to the prior week's snapshot (the agent should persist last week's snapshot).
• Flag new entrants in the top 3 (potential threat) and dropped competitors (potential opportunity).
• Output: per-keyword SERP delta with strategic note.

9. Content freshness audit

• List pages older than 6 months (use Git log on the content files, or GSC "Last crawled" date) with declining clicks over the trailing 4 weeks.
• For the top 5 by lost clicks: recommend a refresh priority based on remaining traffic, topic stability, and competitor SERP activity.
• Output: refresh queue with effort estimate.

10. Schema and structured data validity

• Sample 5 pages at random plus the homepage.
• For each, extract the JSON-LD via curl -s URL | grep -A 200 'application/ld+json'.
• Validate against schema.org by checking required properties for the declared @type (the agent has a local rules file or fetches schema.org definitions).
• Output: list of breakages with file path and fix.

11. Stats memory snapshot

At the end of every run, append a row to weekly-seo/memory/stats.csv (create if missing):

date,indexed_pages,clicks_7d,impressions_7d,avg_position,new_backlinks,lost_backlinks,lcp_ms,cls,inp_ms,ai_bot_sessions

This builds a longitudinal record the agent can query in future runs for trend analysis (e.g., 4-week rolling average, detecting regressions that don't show up in week-over-week deltas).

Also append to weekly-seo/memory/keywords.csv (one row per target keyword per run):

date,keyword,position,impressions,clicks,ctr,page_url

These two files are the agent's persistent memory. Never truncate or overwrite them. Always append.

12. Change log (what worked)

Read weekly-seo/memory/changelog.md (create if missing). This file is a running log of changes applied to the site and their measured impact.

On every run:

1. For each entry in the changelog with status: pending-validation and a measure_after date that has now passed: pull the relevant metric (rankings, clicks, CWV, etc.) for the affected page or keyword and compare to the baseline recorded at change time. Update the entry with status: validated or status: no-effect, the measured delta, and a one-sentence conclusion. 2. At the end of the report, emit a "What worked" section listing only validated entries with positive delta, ordered by impact. This is the institutional memory of SEO wins.

When instructed to log a change (user or orchestrator passes a change description):

Append to weekly-seo/memory/changelog.md:

## YYYY-MM-DD — <short title>

- **Page/scope**: `https://example.com/page` (or "site-wide")
- **Change**: one-sentence description of what was done
- **Hypothesis**: why this should improve the metric
- **Baseline**: clicks=N, position=N, LCP=Nms (snapshot at time of change)
- **Metric to watch**: clicks | position | LCP | CLS | INP | backlinks
- **Measure after**: YYYY-MM-DD (typically 3–4 weeks out)
- **Status**: pending-validation

Never delete changelog entries. no-effect entries are as valuable as wins — they prevent re-testing the same hypothesis.

Output format

The agent produces a single Markdown report saved to weekly-seo/YYYY-MM-DD.md and (optionally) posted to Slack.

Report structure:

# Weekly SEO Report: example.com (YYYY-MM-DD)

## Summary

- Indexed pages: N (delta vs last week)
- Total clicks (7d): N (delta)
- Total impressions (7d): N (delta)
- New backlinks: N | Lost: N
- AI bot sessions: N (delta)

## 🔴 Blockers

[ordered list of items requiring action this week]

## 🟡 Should fix

[ordered list of items worth addressing next sprint]

## 🟢 Opportunities

[ordered list of growth opportunities, e.g., page-2 keywords, competitor weakness]

## 📊 Per-task details

### 1. Ranking changes

### 2. Page-2 opportunities

### 3. New backlinks

### 4. Lost backlinks

### 5. Core Web Vitals drift

### 6. Indexation health

### 7. AI bot traffic

### 8. Competitor SERP monitoring

### 9. Content freshness

### 10. Schema validity

Agent definition file (copy this into .claude/agents/weekly-seo.md)

---
name: weekly-seo
description: Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities.
tools: WebFetch, WebSearch, Bash, Read, Write
---

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console (via community MCP or curl): tasks 1, 2, 5, 6
- Web search (built-in): tasks 2, 8

If an MCP is unavailable, fall back to Claude for Chrome, to a web browser, to the equivalent API call via `curl` or `web_fetch` with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

Config file template

Place at weekly-seo/config.yml in the site's repo.

domain: example.com
gsc_property: sc-domain:example.com
ahrefs_project_id: 12345
posthog_project_id: 67890
slack_webhook: https://hooks.slack.com/services/...
target_keywords:
  - "keyword one"
  - "keyword two"
  - "keyword three"
  - "keyword four"
  - "keyword five"
site_type: doc-site # or marketing, saas-app, paid-course, portfolio

The agent reads this config to scope every task. If the file is missing, the agent asks the user (via ask_user_input_v0 if invoked interactively, or fails with a clear error if invoked headlessly).