What to do next on this site

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

GOAL (on buildercamp.com)
Build the definitive Home Building cornerstone guide — on the site buildercamp.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Home Building 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 Home Building — 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Lock down sensitive data — nothing private is publicly reachable — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Add an interactive tool and an email capture for Home Building — on the site buildercamp.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Home Building (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 Home Building — 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site buildercamp.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 Home Building — 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Publish: Material costs and lead times right now — on the site buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Budget-killer post-mortems shared to builder forums — on the site buildercamp.com.

WHY IT MATTERS
Write honest post-mortem articles — the five places owner-builder budgets die: change orders, dry-in delays, allowance underestimates, rework, financing gaps — grounded in documented industry patterns, not invented anecdotes. Failure analysis is the most-shared genre in owner-builder forums, where this site's audience already congregates. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Free ten-lesson owner-builder curriculum as flagship — on the site buildercamp.com.

WHY IT MATTERS
Publish a complete free curriculum — site prep, foundation, framing, mechanicals, inspections, certificate of occupancy — as ten substantial lesson pages in fixed sequence. A genuinely complete free course is the link magnet and email-list engine this brand name promises; thin teaser content would squander the 'camp' framing. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Publish: The energy-code changes builders must meet in 2026 — on the site buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Publish: Prefab and panelized methods gaining ground — on the site buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Publish: Labor-shortage workarounds that work — on the site buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Sell printable construction-binder template bundle — on the site buildercamp.com.

WHY IT MATTERS
Package the documents every owner-builder needs — budget tracker, sub contact sheets, inspection checklists, draw-schedule log — as a one-time-purchase printable binder bundle sold alongside the free curriculum. Free lessons plus paid organization tools is an honest split: knowledge open, convenience purchasable. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Lesson clips published through YouTube pipeline — on the site buildercamp.com.

WHY IT MATTERS
Cut each lesson's core concept into a short narrated video, upload via the @PaulTerryWalhus pipeline, and embed on lesson pages plus /videos/ after check-embed.mjs verification. Owner-builder research happens heavily on YouTube; clips funnel that audience into the full written curriculum where the list-building happens. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Per-lesson Amazon tool and book lists — on the site buildercamp.com.

WHY IT MATTERS
Attach a short colinfirthfan-20 shelf to each lesson matching its phase — laser level in the foundation lesson, moisture meter in dry-in, code-reference books throughout. Phase-matched recommendations convert far better than generic tool roundups because readers arrive at each lesson exactly when needing that phase's gear. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Deepen the main Home Building guide with current data and examples — on the site buildercamp.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 Home Building 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 Home Building.
- 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Bootcamp field-manual aesthetic with stencil headings — on the site buildercamp.com.

WHY IT MATTERS
Art-direct as a military-style field manual: stencil-lettered lesson headings, kraft-paper card backgrounds, drill-list checkboxes for each task sequence, and phase numbers stamped like manual section codes. The 'camp' brand promises discipline and completeness — the field-manual visual system delivers that promise before reading begins. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
AdSense on curriculum and post-mortem pages — on the site buildercamp.com.

WHY IT MATTERS
Run pub-7759195213529699 on lesson and article pages with placements kept outside instructional step sequences. Construction-education traffic draws well-paying home-improvement and financing inventory; protecting the reading flow keeps completion rates high, since students who finish lessons are the ones who buy the binder bundle. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Phase-completion badges styled as merit patches — on the site buildercamp.com.

WHY IT MATTERS
Design each curriculum phase's completion marker as an embroidered merit-patch graphic — foundation, framing, rough-in, finish — collected on a visible progress strip as students advance. Scouting's patch language makes dry construction milestones feel earned and gives learners a shareable artifact per phase completed. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
HowTo schema per lesson with FAQ blocks — on the site buildercamp.com.

WHY IT MATTERS
Mark each lesson with HowTo schema — steps, materials, duration estimates — and add FAQPage answers for 'can I be my own general contractor' and 'how long does owner-building take.' Run af-deploy.py to 90+ so answer engines route owner-builder questions into the curriculum's front door. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Add an FAQ answering the top questions in Home Building — on the site buildercamp.com.

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

HOW TO APPROACH IT
1. Audit the flagship Home Building 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 Home Building.
- 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Personal build-checklist generator from lesson content — on the site buildercamp.com.

WHY IT MATTERS
Build a static-JS tool that assembles a personalized build checklist — user picks foundation type, stories, septic-or-sewer — outputting a printable task sequence drawn from the curriculum, in the spirit of the network's /act/ worksheets. It converts passive readers into planners who return throughout their build. (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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

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

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

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Home Building: 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 Home Building 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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Add Article + FAQ structured data — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site buildercamp.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: buildercamp.com (live at https://buildercamp.com/), a Home Building site in the WholeTech network, served from /var/www/buildercamp.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for buildercamp.com and no other site — make all changes on buildercamp.com. Act like a senior editor and web engineer who knows the Home Building niche cold.

GOAL (on buildercamp.com)
Add the network affiliate + AdSense setup — on the site buildercamp.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.

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

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

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Home Building 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.