A prioritized, living to-do list for fableguide.com, built from this site's sources and current trends in Artificial Intelligence. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Security | 2026-06-19 | on fableguide.com Lock down sensitive data — nothing private is publicly reachable |
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. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Lock down sensitive data — nothing private is publicly reachable — on the site fableguide.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. | ||||
| 2 | 99 | Security | 2026-06-19 | on fableguide.com Verify HTTPS, security headers & a safe Agents-First surface |
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. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site fableguide.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. | ||||
| 3 | 97 | Flagship | 2026-06-21 | on fableguide.com Build the definitive Artificial Intelligence cornerstone guide |
Create the single most useful, authoritative page on Artificial Intelligence anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Build the definitive Artificial Intelligence cornerstone guide — on the site fableguide.com. WHY IT MATTERS Create the single most useful, authoritative page on Artificial Intelligence anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations. HOW TO APPROACH IT 1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that. 2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway. 3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics. 4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 4 | 96 | Security | 2026-06-21 | on fableguide.com Make the site mythos-attack-proof — harden against automated & AI-agent abuse |
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. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site fableguide.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. | ||||
| 5 | 93 | Flagship | 2026-06-23 | on fableguide.com Add an interactive tool and an email capture for Artificial Intelligence |
Build one genuinely useful interactive element for Artificial Intelligence (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Add an interactive tool and an email capture for Artificial Intelligence — on the site fableguide.com. WHY IT MATTERS Build one genuinely useful interactive element for Artificial Intelligence (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns. HOW TO APPROACH IT 1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that. 2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway. 3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics. 4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 6 | 92 | Flagship | 2026-06-24 | on fableguide.com Make the homepage genuinely distinctive — kill any generic-template feel |
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. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site fableguide.com. WHY IT MATTERS Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory. HOW TO APPROACH IT 1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Artificial Intelligence — then build exactly that. 2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway. 3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics. 4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The page is genuinely the strongest Artificial Intelligence resource on the site — deep, accurate, and a pleasure to read, not a thin template. - Every factual claim is current and traceable to a real, linked source. - It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 7 | 88 | Popularity | 2026-06-27 | on fableguide.com Weekly what-changed digest for Fable 5 |
Publish a dated weekly digest of verifiable Fable 5 changes, drawn from official release notes and documented behavior, never speculation. Recurring dated pages give returning readers a reason to bookmark the site, and each issue pushes through the fableguide-news Flask list already running at port 8993. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Weekly what-changed digest for Fable 5 — on the site fableguide.com. WHY IT MATTERS Publish a dated weekly digest of verifiable Fable 5 changes, drawn from official release notes and documented behavior, never speculation. Recurring dated pages give returning readers a reason to bookmark the site, and each issue pushes through the fableguide-news Flask list already running at port 8993. (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. | ||||
| 8 | 88 | Popularity | 2026-06-27 | on fableguide.com Honest overnight-build case studies from network |
Write case studies of real overnight builds run across the WholeTech network, such as multi-site rollouts, with actual scope, duration, and outcomes under an institutional byline. First-hand operational detail is content nobody else can copy and earns links from AI practitioner blogs and newsletters. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Honest overnight-build case studies from network — on the site fableguide.com. WHY IT MATTERS Write case studies of real overnight builds run across the WholeTech network, such as multi-site rollouts, with actual scope, duration, and outcomes under an institutional byline. First-hand operational detail is content nobody else can copy and earns links from AI practitioner blogs and newsletters. (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. | ||||
| 9 | 88 | Trends | 2026-06-27 | on fableguide.com Publish: Agentic workflows a small business can deploy this month |
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Publish: Agentic workflows a small business can deploy this month — on the site fableguide.com. WHY IT MATTERS Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. HOW TO APPROACH IT 1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points. 2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 10 | 87 | Trends | 2026-06-28 | on fableguide.com Publish: The latest frontier AI model tier and what it unlocks |
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Publish: The latest frontier AI model tier and what it unlocks — on the site fableguide.com. WHY IT MATTERS Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. HOW TO APPROACH IT 1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points. 2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 11 | 80 | Popularity | 2026-07-03 | on fableguide.com Heavy-model versus daily-driver decision guide |
Publish a candid guide on when an overnight heavy model earns its double token burn versus a daily default, framed around subscription limits rather than per-token spend. This practical cost-discipline angle is underserved and travels well on Hacker News and the AI-tooling subreddits. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Heavy-model versus daily-driver decision guide — on the site fableguide.com. WHY IT MATTERS Publish a candid guide on when an overnight heavy model earns its double token burn versus a daily default, framed around subscription limits rather than per-token spend. This practical cost-discipline angle is underserved and travels well on Hacker News and the AI-tooling subreddits. (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. | ||||
| 12 | 80 | Trends | 2026-07-03 | on fableguide.com Publish: Practical AI guardrails and what to avoid |
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Publish: Practical AI guardrails and what to avoid — on the site fableguide.com. WHY IT MATTERS Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. HOW TO APPROACH IT 1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points. 2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 13 | 79 | Trends | 2026-07-03 | on fableguide.com Publish: Answer-engine optimization — getting cited by AI search |
Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Publish: Answer-engine optimization — getting cited by AI search — on the site fableguide.com. WHY IT MATTERS Trending angle in Artificial Intelligence. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. HOW TO APPROACH IT 1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points. 2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Artificial Intelligence reader, and a clear next step. 3. Cite and link each source inline and date the piece so its freshness is obvious. 4. Link it from the homepage and /sources/, and submit it via IndexNow. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - A reader learns something current and genuinely useful they could not get from a thin AI page. - At least 3 real sources are cited and linked; no fabricated numbers. - The page is internally linked and submitted for fast indexing. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 14 | 77 | Revenue | 2026-07-05 | on fableguide.com Newsletter widget on every guide page |
Embed the wholetech.com/newsletter/widget.js signup on all guide and library pages, feeding the fableguide-news list. A growing subscriber base is the honest monetization path here: it compounds into future sponsorship value while keeping the guide content itself free, unbiased, and worth citing. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Newsletter widget on every guide page — on the site fableguide.com. WHY IT MATTERS Embed the wholetech.com/newsletter/widget.js signup on all guide and library pages, feeding the fableguide-news list. A growing subscriber base is the honest monetization path here: it compounds into future sponsorship value while keeping the guide content itself free, unbiased, and worth citing. (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. | ||||
| 15 | 75 | Content | 2026-07-06 | on fableguide.com Deepen the main Artificial Intelligence guide with current data and examples |
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Deepen the main Artificial Intelligence guide with current data and examples — on the site fableguide.com. WHY IT MATTERS Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template. HOW TO APPROACH IT 1. Audit the flagship Artificial Intelligence page and list exactly what is stale, thin, or vague. 2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader. 3. Cross-link to /sources/ and the most related pages. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Depth and accuracy match the best competitor page in Artificial Intelligence. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 16 | 75 | Revenue | 2026-07-06 | on fableguide.com Library decks as draft-notified lead capture |
Gate the Austin investor deck downloads in /library/ behind a light email form whose submissions generate Gmail DRAFT notifications for Paul, never auto-sent mail. The list identifies serious readers and investors, creating a pipeline for partnership conversations without paywalling any of the guides. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Library decks as draft-notified lead capture — on the site fableguide.com. WHY IT MATTERS Gate the Austin investor deck downloads in /library/ behind a light email form whose submissions generate Gmail DRAFT notifications for Paul, never auto-sent mail. The list identifies serious readers and investors, creating a pipeline for partnership conversations without paywalling any of the guides. (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. | ||||
| 17 | 73 | Revenue | 2026-07-07 | on fableguide.com Amazon book roundup on agentic-AI reading |
Create a curated reading list of genuinely useful books on prompting, agents, and AI strategy, each with a two-line honest verdict, linked through the colinfirthfan-20 Amazon Associates tag. Only include titles worth recommending; the credibility of the guide is the entire asset being monetized. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Amazon book roundup on agentic-AI reading — on the site fableguide.com. WHY IT MATTERS Create a curated reading list of genuinely useful books on prompting, agents, and AI strategy, each with a two-line honest verdict, linked through the colinfirthfan-20 Amazon Associates tag. Only include titles worth recommending; the credibility of the guide is the entire asset being monetized. (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. | ||||
| 18 | 71 | Design | 2026-07-09 | on fableguide.com Illuminated-manuscript-meets-terminal art direction |
Lean into the fable name: illuminated-manuscript drop caps and woodcut-style chapter illustrations paired with monospace code blocks on deep night-sky gradients that evoke overnight builds. The tension between storybook ornament and terminal utility becomes a memorable visual signature no template can imitate. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Illuminated-manuscript-meets-terminal art direction — on the site fableguide.com. WHY IT MATTERS Lean into the fable name: illuminated-manuscript drop caps and woodcut-style chapter illustrations paired with monospace code blocks on deep night-sky gradients that evoke overnight builds. The tension between storybook ornament and terminal utility becomes a memorable visual signature no template can imitate. (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. | ||||
| 19 | 70 | Design | 2026-07-10 | on fableguide.com Field-manual chapter rail on guide pages |
Give long guides a sticky left chapter rail with numbered sections, progress ticks, and estimated reading time, styled like a field-manual index. Practitioners return mid-task to find one answer; navigation built for re-entry keeps them on fableguide instead of re-searching from scratch. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Field-manual chapter rail on guide pages — on the site fableguide.com. WHY IT MATTERS Give long guides a sticky left chapter rail with numbered sections, progress ticks, and estimated reading time, styled like a field-manual index. Practitioners return mid-task to find one answer; navigation built for re-entry keeps them on fableguide instead of re-searching from scratch. (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. | ||||
| 20 | 68 | Content | 2026-07-11 | on fableguide.com Add an FAQ answering the top questions in Artificial Intelligence |
Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Add an FAQ answering the top questions in Artificial Intelligence — on the site fableguide.com. WHY IT MATTERS Pull the real questions people ask in Artificial Intelligence and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Artificial Intelligence page and list exactly what is stale, thin, or vague. 2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader. 3. Cross-link to /sources/ and the most related pages. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Depth and accuracy match the best competitor page in Artificial Intelligence. - No filler and no fabricated specifics — every number is current and sourced. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 67 | AEO | 2026-07-12 | on fableguide.com FAQ schema plus llms.txt for model queries |
Add FAQPage schema answering what Fable 5 is, how it differs from daily models, and when overnight builds justify it, plus an llms.txt summarizing the site for answer engines. Verify both sitemaps exist and run af-deploy.py to hold the Agents-First score above 90. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) FAQ schema plus llms.txt for model queries — on the site fableguide.com. WHY IT MATTERS Add FAQPage schema answering what Fable 5 is, how it differs from daily models, and when overnight builds justify it, plus an llms.txt summarizing the site for answer engines. Verify both sitemaps exist and run af-deploy.py to hold the Agents-First score above 90. (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. | ||||
| 22 | 64 | Product | 2026-07-14 | on fableguide.com Curated videos page via embeddability checker |
Build a /videos/ page of authoritative talks and demos on agentic coding and overnight workflows, each verified embeddable with check-embed.mjs before inclusion, per the FableGuide curation rule excluding get-rich-quick content. Sequence them into viewing paths so the page reads as a course, not a dump. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Curated videos page via embeddability checker — on the site fableguide.com. WHY IT MATTERS Build a /videos/ page of authoritative talks and demos on agentic coding and overnight workflows, each verified embeddable with check-embed.mjs before inclusion, per the FableGuide curation rule excluding get-rich-quick content. Sequence them into viewing paths so the page reads as a course, not a dump. (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. | ||||
| 23 | 57 | Design | 2026-07-19 | on fableguide.com Apply a WT-Skins kit to lift the design and Agents-First score |
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. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site fableguide.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. | ||||
| 24 | 55 | Fresh | 2026-07-20 | on fableguide.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Keep the live / news feed updated on cadence (2×/day) — on the site fableguide.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Artificial Intelligence items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Artificial Intelligence: attributed, links out, and running on a 2x/day cadence. 2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The feed publishes fresh, correctly-attributed Artificial Intelligence items on schedule and is discovered quickly. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 55 | SEO | 2026-07-20 | on fableguide.com Submit updated URLs via IndexNow and refresh the sitemap |
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site fableguide.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. | ||||
| 26 | 46 | SEO | 2026-07-26 | on fableguide.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Add Article + FAQ structured data — on the site fableguide.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. | ||||
| 27 | 45 | Monetize | 2026-07-27 | on fableguide.com Verify affiliate links and ad placement resolve correctly |
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Verify affiliate links and ad placement resolve correctly — on the site fableguide.com. WHY IT MATTERS Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. 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. | ||||
| 28 | 45 | SEO | 2026-07-27 | on fableguide.com Strengthen internal links between the core, /sources/ and this worksheet |
A tight internal-link web spreads authority and keeps visitors moving through the site. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site fableguide.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. | ||||
| 29 | 45 | Video | 2026-07-27 | on fableguide.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. ★ Copy-paste prompt for fableguide.com You are working on ONE specific website: fableguide.com (live at https://fableguide.com/), a Artificial Intelligence site in the WholeTech network, served from /var/www/fableguide.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for fableguide.com and no other site — make all changes on fableguide.com. Act like a senior editor and web engineer who knows the Artificial Intelligence niche cold. GOAL (on fableguide.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site fableguide.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Artificial Intelligence videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Artificial Intelligence videos that ALLOW embedding — verify each embed actually plays. 2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||