What to do next on this site

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

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

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

GOAL (on hoopwomen.com)
Build the definitive Women's Basketball cornerstone guide — on the site hoopwomen.com.

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

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

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

GOAL (on hoopwomen.com)
Publish: A current, data-backed explainer in Women's Basketball — on the site hoopwomen.com.

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

GOAL (on hoopwomen.com)
Add an interactive tool and an email capture for Women's Basketball — on the site hoopwomen.com.

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

GOAL (on hoopwomen.com)
Auto-publish WNBA game-day preview pages — on the site hoopwomen.com.

WHY IT MATTERS
Wire /root/gen-live.py to produce dated game-day preview and result pages through the WNBA season — matchup, storyline, where to watch — in the Google-News-friendly /live/ format the engine already outputs. Fresh dated pages during the season are how a small basketball site earns recurring crawls. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Publish: The question your Women's Basketball audience is searching most right now — on the site hoopwomen.com.

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

GOAL (on hoopwomen.com)
Publish WNBA and NCAAW schedule pages — on the site hoopwomen.com.

WHY IT MATTERS
Reuse the gamesked feed.json calendar infrastructure to publish clean season schedules for WNBA teams and top women's college programs. Schedule queries are the highest-volume searches in women's basketball, they recur weekly all season, and structured calendar pages fit the network's existing agent-shop ticket plumbing. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Publish: A 'what changed in 2026' round-up for Women's Basketball — on the site hoopwomen.com.

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

GOAL (on hoopwomen.com)
Build /videos/ of highlights and history — on the site hoopwomen.com.

WHY IT MATTERS
Curate embeddable highlight reels, classic finals moments, and player documentaries into a /videos/ page, verifying every embed with check-embed.mjs and renumbering after dropping embed=false entries. Women's-hoops highlight supply on YouTube is rich but scattered; a curated page becomes a genuine destination. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Add TicketNetwork links on schedule pages — on the site hoopwomen.com.

WHY IT MATTERS
Extend the live TicketNetwork affiliate integration — already running on five network sports sites via Impact — to hoopwomen.com's schedule and team pages, deep-linking WNBA and women's college games. Ticket intent lives exactly on schedule pages, and resale inventory covers the sold-out marquee matchups. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Publish training-gear guide with Amazon — on the site hoopwomen.com.

WHY IT MATTERS
Create an honest gear page — game balls by level, training aids, coaching books, notable player memoirs — with Amazon tag colinfirthfan-20 and a line of genuine rationale per pick. Parents and coaches of girls' teams are steady buyers underserved by men's-basketball-centric gear content. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

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

GOAL (on hoopwomen.com)
Adopt hardwood-and-paint court art direction — on the site hoopwomen.com.

WHY IT MATTERS
Design from the court itself: hardwood-plank texture backgrounds, key-and-arc paint shapes as section dividers, jersey-numeral display type for headings, and a leather-orange accent palette. The site should feel like standing at the baseline, not like a generic sports-news template with swapped logos. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Run AdSense across previews and features — on the site hoopwomen.com.

WHY IT MATTERS
Enable shared AdSense pub-7759195213529699 on game previews, schedules, and feature pages. Sports betting and streaming advertisers bid strongly on basketball terms in-season; keep ad density modest on schedule tables so tip-off times stay instantly readable on phones, where most schedule checks happen. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Add an FAQ answering the top questions in Women's Basketball — on the site hoopwomen.com.

WHY IT MATTERS
Pull the real questions people ask in Women's Basketball and answer them plainly. Mark up with FAQ schema for rich results.

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

GOAL (on hoopwomen.com)
Style stats as broadcast box scores — on the site hoopwomen.com.

WHY IT MATTERS
Present player and team numbers in box-score-styled tables — condensed tabular numerals, alternating row rules, abbreviated column heads exactly as broadcasts render them. Basketball readers parse that format instantly, and consistent box-score styling makes the site's data pages feel professionally sourced. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Add FAQ schema on season basics — on the site hoopwomen.com.

WHY IT MATTERS
Mark up FAQPage entries for 'when does the WNBA season start', 'how to watch women's college basketball', and roster-size rules, answered with current, dated, sourced facts. Season-logistics questions dominate answer-engine traffic in this niche and reward whoever maintains accurate current answers. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

GOAL (on hoopwomen.com)
Integrate agent-shop ticket feed.json — on the site hoopwomen.com.

WHY IT MATTERS
Publish the machine-readable ticket feed.json used by the gamesked agent-shop infrastructure for women's games, exposing schedules and ticket links to AI agents. Agents-First is the network principle; being the agent-readable source for women's basketball tickets is a first-mover position nobody else occupies. (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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

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

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

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Women's Basketball items and pinging IndexNow each run.

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

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

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

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

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

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Women's Basketball videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Women's Basketball 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: hoopwomen.com (live at https://hoopwomen.com/), a Women's Basketball site in the WholeTech network, served from /var/www/hoopwomen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for hoopwomen.com and no other site — make all changes on hoopwomen.com. Act like a senior editor and web engineer who knows the Women's Basketball niche cold.

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