A prioritized, living to-do list for atxengine.com, built from this site's sources and current trends in Startup Tech. 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 atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Lock down sensitive data — nothing private is publicly reachable — on the site atxengine.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 | 98 | Security | 2026-06-20 | on atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site atxengine.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 atxengine.com Build the definitive Startup Tech cornerstone guide |
Create the single most useful, authoritative page on Startup Tech 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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Build the definitive Startup Tech cornerstone guide — on the site atxengine.com. WHY IT MATTERS Create the single most useful, authoritative page on Startup Tech 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 Startup Tech — 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 Startup Tech 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 atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site atxengine.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 | 92 | Flagship | 2026-06-24 | on atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site atxengine.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 Startup Tech — 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 Startup Tech 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 atxengine.com Add an interactive tool and an email capture for Startup Tech |
Build one genuinely useful interactive element for Startup Tech (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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add an interactive tool and an email capture for Startup Tech — on the site atxengine.com. WHY IT MATTERS Build one genuinely useful interactive element for Startup Tech (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 Startup Tech — 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 Startup Tech 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 | 91 | Popularity | 2026-06-25 | on atxengine.com Publish the 280-sites-one-droplet case study |
Write the flagship proof piece: how one operator runs approximately 280 sites on a single DigitalOcean droplet with agent workflows — architecture, nightly audits, AF scoring, real numbers from the network's own dashboards. This story is genuinely rare and is the studio's best organic-link asset. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Publish the 280-sites-one-droplet case study — on the site atxengine.com. WHY IT MATTERS Write the flagship proof piece: how one operator runs approximately 280 sites on a single DigitalOcean droplet with agent workflows — architecture, nightly audits, AF scoring, real numbers from the network's own dashboards. This story is genuinely rare and is the studio's best organic-link asset. (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 | 90 | Trends | 2026-06-26 | on atxengine.com Publish: A current, data-backed explainer in Startup Tech |
Trending angle in Startup Tech. 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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Publish: A current, data-backed explainer in Startup Tech — on the site atxengine.com. WHY IT MATTERS Trending angle in Startup Tech. 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 Startup Tech 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. | ||||
| 9 | 88 | Trends | 2026-06-27 | on atxengine.com Publish: The question your Startup Tech audience is searching most right now |
Trending angle in Startup Tech. 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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Publish: The question your Startup Tech audience is searching most right now — on the site atxengine.com. WHY IT MATTERS Trending angle in Startup Tech. 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 Startup Tech 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 | Popularity | 2026-06-28 | on atxengine.com Ship public build logs from dev.atxengine.com |
Turn real builds into dated engineering-log entries — problem, agent approach, time-to-live, lessons — linking the live result each time. Build-in-public logs are how zero-to-one studios earn founder attention, and the network generates genuine material weekly without any fabrication. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Ship public build logs from dev.atxengine.com — on the site atxengine.com. WHY IT MATTERS Turn real builds into dated engineering-log entries — problem, agent approach, time-to-live, lessons — linking the live result each time. Build-in-public logs are how zero-to-one studios earn founder attention, and the network generates genuine material weekly without any fabrication. (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. | ||||
| 11 | 83 | Popularity | 2026-06-30 | on atxengine.com Plant the flag in Austin founder circles |
Cross-link from the texascoworking.com Capital Factory and Capital Thought pages, list the studio on atxaisites.com, and draft (never auto-send) outreach notes to Austin founder newsletters offering the droplet case study. The audience is local and reachable through assets the network already owns. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Plant the flag in Austin founder circles — on the site atxengine.com. WHY IT MATTERS Cross-link from the texascoworking.com Capital Factory and Capital Thought pages, list the studio on atxaisites.com, and draft (never auto-send) outreach notes to Austin founder newsletters offering the droplet case study. The audience is local and reachable through assets the network already owns. (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 | 83 | Trends | 2026-06-30 | on atxengine.com Publish: A 'what changed in 2026' round-up for Startup Tech |
Trending angle in Startup Tech. 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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Publish: A 'what changed in 2026' round-up for Startup Tech — on the site atxengine.com. WHY IT MATTERS Trending angle in Startup Tech. 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 Startup Tech 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 | 82 | Revenue | 2026-07-01 | on atxengine.com Productized zero-to-one packages with real scope |
Publish two or three fixed-scope offers — validation site in a week, agent-built content engine, AF-scored site rebuild — with deliverables and honest timelines drawn from work actually performed on the network. Productized scope converts founders who will never buy vague consulting. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Productized zero-to-one packages with real scope — on the site atxengine.com. WHY IT MATTERS Publish two or three fixed-scope offers — validation site in a week, agent-built content engine, AF-scored site rebuild — with deliverables and honest timelines drawn from work actually performed on the network. Productized scope converts founders who will never buy vague consulting. (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. | ||||
| 14 | 76 | Content | 2026-07-05 | on atxengine.com Deepen the main Startup Tech 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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Deepen the main Startup Tech guide with current data and examples — on the site atxengine.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 Startup Tech 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 Startup Tech. - 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. | ||||
| 15 | 76 | Revenue | 2026-07-05 | on atxengine.com Inquiry pipeline that drafts, never auto-sends |
Every engagement CTA feeds a form that creates a Gmail DRAFT notification with the prospect's brief, per network rules. Add a short qualification field (budget range, timeline) so drafts arrive triage-ready. The form is the studio's cash register; instrument it before anything else. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Inquiry pipeline that drafts, never auto-sends — on the site atxengine.com. WHY IT MATTERS Every engagement CTA feeds a form that creates a Gmail DRAFT notification with the prospect's brief, per network rules. Add a short qualification field (budget range, timeline) so drafts arrive triage-ready. The form is the studio's cash register; instrument it before anything else. (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. | ||||
| 16 | 76 | Sources | 2026-07-05 | on atxengine.com Add source: Y Combinator Library |
Essays and talks on building startups. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add source: Y Combinator Library — on the site atxengine.com. WHY IT MATTERS Essays and talks on building startups. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Startup Tech. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Startup Tech expert would trust. - 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 | Design | 2026-07-07 | on atxengine.com Blueprint-schematic aesthetic: exploded engine of a launch |
Art-direct the hero as a technical exploded-view drawing — an engine's parts labeled as the studio's pipeline stages (idea, agents, deploy, audit) on blueprint cyan with white linework and drafting-title-block footers. The engine metaphor becomes literal draftsmanship, signaling precision over agency gloss. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Blueprint-schematic aesthetic: exploded engine of a launch — on the site atxengine.com. WHY IT MATTERS Art-direct the hero as a technical exploded-view drawing — an engine's parts labeled as the studio's pipeline stages (idea, agents, deploy, audit) on blueprint cyan with white linework and drafting-title-block footers. The engine metaphor becomes literal draftsmanship, signaling precision over agency gloss. (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. | ||||
| 18 | 73 | Revenue | 2026-07-07 | on atxengine.com Paid teardown offer for founder sites |
Offer a fixed-price agent-era site teardown — AF score via the network's own scorer, structure and answer-engine audit, prioritized fix list — as the low-ticket entry product. Teardowns are cheap to deliver with existing tooling and convert naturally into the larger rebuild packages. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Paid teardown offer for founder sites — on the site atxengine.com. WHY IT MATTERS Offer a fixed-price agent-era site teardown — AF score via the network's own scorer, structure and answer-engine audit, prioritized fix list — as the low-ticket entry product. Teardowns are cheap to deliver with existing tooling and convert naturally into the larger rebuild packages. (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. | ||||
| 19 | 68 | Sources | 2026-07-11 | on atxengine.com Add source: Paul Graham Essays |
Foundational startup writing. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add source: Paul Graham Essays — on the site atxengine.com. WHY IT MATTERS Foundational startup writing. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Startup Tech. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Startup Tech expert would trust. - 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 | Sources | 2026-07-11 | on atxengine.com Build /sources/ out to at least 10 authoritative links |
Only 0 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Build /sources/ out to at least 10 authoritative links — on the site atxengine.com. WHY IT MATTERS Only 0 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Startup Tech. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Startup Tech expert would trust. - 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 atxengine.com ProfessionalService schema and llms.txt for agent buyers |
Add ProfessionalService JSON-LD (offers, area served) and an llms.txt describing exactly what the studio builds, since prospective clients increasingly ask AI assistants who builds agent-first sites. A studio selling agent-era work must itself score 95-plus on af-deploy.py — make that score public. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) ProfessionalService schema and llms.txt for agent buyers — on the site atxengine.com. WHY IT MATTERS Add ProfessionalService JSON-LD (offers, area served) and an llms.txt describing exactly what the studio builds, since prospective clients increasingly ask AI assistants who builds agent-first sites. A studio selling agent-era work must itself score 95-plus on af-deploy.py — make that score public. (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 | 67 | Sources | 2026-07-12 | on atxengine.com Add source: Lenny's Newsletter |
Product and growth deep-dives. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add source: Lenny's Newsletter — on the site atxengine.com. WHY IT MATTERS Product and growth deep-dives. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Startup Tech. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Startup Tech expert would trust. - 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 | 65 | Content | 2026-07-13 | on atxengine.com Add an FAQ answering the top questions in Startup Tech |
Pull the real questions people ask in Startup Tech and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add an FAQ answering the top questions in Startup Tech — on the site atxengine.com. WHY IT MATTERS Pull the real questions people ask in Startup Tech and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Startup Tech 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 Startup Tech. - 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. | ||||
| 24 | 65 | Sources | 2026-07-13 | on atxengine.com Add source: First Round Review |
Operational playbooks from founders. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add source: First Round Review — on the site atxengine.com. WHY IT MATTERS Operational playbooks from founders. Authoritative Startup Tech reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Startup Tech. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Startup Tech expert would trust. - 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 | 64 | Design | 2026-07-14 | on atxengine.com Live gauges wired to real network telemetry |
Add machined instrument-cluster gauges on the homepage showing true figures the network already computes — sites live, AF scores in the 90s, pages indexed — pulled from existing stats JSON, never hardcoded. Real moving instruments prove the engine runs; fake counters would poison the pitch. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Live gauges wired to real network telemetry — on the site atxengine.com. WHY IT MATTERS Add machined instrument-cluster gauges on the homepage showing true figures the network already computes — sites live, AF scores in the 90s, pages indexed — pulled from existing stats JSON, never hardcoded. Real moving instruments prove the engine runs; fake counters would poison the pitch. (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. | ||||
| 26 | 62 | Popularity | 2026-07-15 | on atxengine.com Syndicate one build story through the YouTube pipeline |
Record a screen-captured walkthrough of a real build going from prompt to live site, publish via @PaulTerryWalhus, and embed on a /videos/ page checked with check-embed.mjs. Watching a site materialize is the studio's most persuasive demo, and video reaches founders written logs miss. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Syndicate one build story through the YouTube pipeline — on the site atxengine.com. WHY IT MATTERS Record a screen-captured walkthrough of a real build going from prompt to live site, publish via @PaulTerryWalhus, and embed on a /videos/ page checked with check-embed.mjs. Watching a site materialize is the studio's most persuasive demo, and video reaches founders written logs miss. (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. | ||||
| 27 | 60 | Design | 2026-07-17 | on atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site atxengine.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. | ||||
| 28 | 57 | Fresh | 2026-07-19 | on atxengine.com Add a /live/ news feed for Startup Tech |
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add a /live/ news feed for Startup Tech — on the site atxengine.com. WHY IT MATTERS An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Startup Tech: 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 Startup Tech 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. | ||||
| 29 | 52 | SEO | 2026-07-22 | on atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site atxengine.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. | ||||
| 30 | 48 | SEO | 2026-07-25 | on atxengine.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add Article + FAQ structured data — on the site atxengine.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. | ||||
| 31 | 48 | SEO | 2026-07-25 | on atxengine.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 atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site atxengine.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. | ||||
| 32 | 43 | Monetize | 2026-07-28 | on atxengine.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Add the network affiliate + AdSense setup — on the site atxengine.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. | ||||
| 33 | 40 | Video | 2026-07-31 | on atxengine.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Startup Tech videos. Re-verify embeds. ★ Copy-paste prompt for atxengine.com You are working on ONE specific website: atxengine.com (live at https://atxengine.com/), a Startup Tech site in the WholeTech network, served from /var/www/atxengine.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for atxengine.com and no other site — make all changes on atxengine.com. Act like a senior editor and web engineer who knows the Startup Tech niche cold. GOAL (on atxengine.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site atxengine.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Startup Tech videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Startup Tech 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. | ||||