What to do next on this site

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Build the definitive Artificial Intelligence cornerstone guide — on the site claudefieldguide.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Artificial Intelligence anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site claudefieldguide.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Lock down sensitive data — nothing private is publicly reachable — on the site claudefieldguide.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site claudefieldguide.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Add an interactive tool and an email capture for Artificial Intelligence — on the site claudefieldguide.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Artificial Intelligence (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Publish: The latest frontier AI model tier and what it unlocks — on the site claudefieldguide.com.

WHY IT MATTERS
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site claudefieldguide.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Species-plate pages for models and tools — on the site claudefieldguide.com.

WHY IT MATTERS
Commit fully to the field-guide conceit: give each model, skill, and harness feature an identification-plate page — habitat, range, behavior, lookalikes — written as a naturalist's entry with practical guidance underneath. The memorable format earns shares on its own, and each plate targets a real query. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Publish: Agentic workflows a small business can deploy this month — on the site claudefieldguide.com.

WHY IT MATTERS
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Searchable index of field-tested recipes — on the site claudefieldguide.com.

WHY IT MATTERS
Publish a searchable index of working prompt-and-workflow recipes, each verified in real use before listing, with a one-line habitat note on when it applies. Recipe indexes are the highest-return-visit content in this niche, and a field-tested-only policy differentiates it from scraped prompt dumps. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Publish: Answer-engine optimization — getting cited by AI search — on the site claudefieldguide.com.

WHY IT MATTERS
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Weekly field notes from real expeditions — on the site claudefieldguide.com.

WHY IT MATTERS
Post short weekly field notes documenting one real observed behavior — a quirk, a workflow win, a failure mode — dated and specific like a birder's log. Consistent first-hand observation logs build the returning readership that aggregator blogs never get, because the sightings are original. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
AdSense on plates and field notes — on the site claudefieldguide.com.

WHY IT MATTERS
Run shared AdSense pub-7759195213529699 across identification plates and field notes, where readers browse laterally through many pages per session. Keep the recipe index itself clean so the site's core utility page stays fast and trustworthy; the browsing pages carry the monetization load. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Publish: Practical AI guardrails and what to avoid — on the site claudefieldguide.com.

WHY IT MATTERS
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Naturalist's bookshelf via Amazon tag — on the site claudefieldguide.com.

WHY IT MATTERS
Curate a disclosed shelf pairing well-regarded AI-development books with a wink of real field-guide classics, via Amazon Associates tag colinfirthfan-20. The pairing reinforces the site's identity while monetizing honestly, and the shelf lives on the about page and plate footers, never inside recipes. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Deepen the main Artificial Intelligence guide with current data and examples — on the site claudefieldguide.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship Artificial Intelligence page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Artificial Intelligence.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Field-notes newsletter digest with widget — on the site claudefieldguide.com.

WHY IT MATTERS
Add the wholetech.com/newsletter/widget.js signup offering the week's field note, one recipe, and one plate in a short digest. Field-guide framing makes even a routine tips email feel like a collectible dispatch from the field. Signup notifications arrive as Gmail DRAFTS for review, never auto-sent. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Peterson-guide plate art direction — on the site claudefieldguide.com.

WHY IT MATTERS
Design like a classic Peterson or Audubon guide: cream field-notebook paper, plate-style illustration frames with figure numbers, taxonomy-label typography with Latin-style binomials for each entry, and tabbed section edges on page sides. The design commitment is the brand — it must look like a guide you'd carry. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Dichotomous-key styling for the chooser — on the site claudefieldguide.com.

WHY IT MATTERS
Style the model-chooser as a real dichotomous key — numbered couplets, either-or branches, go-to-step references — exactly as botanical keys work. It is both the site's most charming artifact and a genuinely superior interface for which-model-when decisions, because couplet questions force clear tradeoffs. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Add an FAQ answering the top questions in Artificial Intelligence — on the site claudefieldguide.com.

WHY IT MATTERS
Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Artificial Intelligence page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Artificial Intelligence.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
HowTo schema on every recipe — on the site claudefieldguide.com.

WHY IT MATTERS
Mark every recipe with HowTo schema — steps, tools, expected outcome — and every plate with a concise definitional summary block. Ship both sitemaps per the two-sitemaps rule and ping the IndexNow key so answer engines quote the field-tested steps verbatim with attribution. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Interactive which-model decision key — on the site claudefieldguide.com.

WHY IT MATTERS
Build the dichotomous key as an interactive tool: answer four or five either-or questions about the task and receive a model recommendation with the reasoning trail shown, echoing the network's own downshift policy. An interactive key gets bookmarked and shared far beyond what static pages achieve. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site claudefieldguide.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Keep the live / news feed updated on cadence (2×/day) — on the site claudefieldguide.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Artificial Intelligence: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed Artificial Intelligence items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site claudefieldguide.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Add Article + FAQ structured data — on the site claudefieldguide.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site claudefieldguide.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site claudefieldguide.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Artificial Intelligence videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: claudefieldguide.com (live at https://claudefieldguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/claudefieldguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for claudefieldguide.com and no other site — make all changes on claudefieldguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold.

GOAL (on claudefieldguide.com)
Add the network affiliate + AdSense setup — on the site claudefieldguide.com.

WHY IT MATTERS
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.