Sunday, May 31, 2026




🔴 MANDATORY PRE-FLIGHT GATE — COMPLETE ALL 8 CHECKS BEFORE WRITING ANY ARTICLE

Every drift incident in prior sessions traced back to skipping one of these checks. Run them in order — do not start generating HTML until all 8 are confirmed.

  1. ☐ Article list locked: ALL articles for this role are identified, titled, URL-slugged, and step-assigned BEFORE Phase 1 begins. Adding articles mid-rollout causes cascading updates to routing chains, guide page cards, video page cards, and step-end CTA destinations. Do not write any content until the complete article list is approved.
  2. ☐ Article type declared: Write down one — Tactical / Guide / Supplementary — before writing anything else.
  3. ☐ Step + topic match verified: Confirm the step number AND verify the planned content fits the step definition in the Step-to-Topic Mapping Table below. Content must match the step definition — not just the label. If content doesn’t fit the step → reassign before writing.
  4. ☐ Callout label confirmed: Tactical = "Quick-Start Workflow" | Guide = "In-Depth Step N Guide" (N = actual step number). These two labels are NEVER swapped.
  5. ☐ Section order confirmed: Step label <strong>AI at [ROLE] / Step N</strong> MUST appear FIRST. Cross-reference callout block appears SECOND. Body content THIRD. Never place the callout before the step label.
  6. ☐ Nav CTA destination confirmed: Look up the article type in the CTA Routing Table below and confirm the destination BEFORE writing the Nav CTA button. Tactical → video page next step. Guide → next guide article (NOT the video page).
  7. ☐ Return CTA destination confirmed: Look up the article type in the CTA Routing Table below. Tactical → returns to video page. Guide → returns to guide page. Supplementary → returns to guide page.
  8. ☐ Post-generation HTML scan: After generating all HTML — search the output for class="aiw-primary". If found, STOP and rewrite those elements with 100% inline styles before publishing.



📍 CTA ROUTING TABLE

Use this table for every article. Confirm both the Nav CTA and Return CTA destinations before writing. This is the most common source of drift.

Article Type Nav CTA Goes To Nav Button Text Format Return CTA Goes To Return Link Text Format
Tactical
(Quick-Start Workflow)		 Next step section on the VIDEO PAGE
Anchor: #[role-slug]-step-N
(N = next step number)		 “Step N: [Next Step Topic] →” VIDEO PAGE
[VIDEO_PAGE_URL]		 “← Return to Step N on the [Role] Video Path”
Guide
(In-Depth Step N Guide)		 NEXT GUIDE ARTICLE
⚠️ NOT the video page — this was a repeated error
URL = next guide article’s permalink		 “[Next Guide Article Title] →” GUIDE PAGE
[GUIDE_PAGE_URL]		 “← Return to the [Role] AI Guide”
Supplementary
(step support article)		 None — or link back to guide page N/A GUIDE PAGE
[GUIDE_PAGE_URL]		 “← Return to the [Role] AI Guide”

⚠️ COMMON ROUTING ERROR: Guide article Nav CTAs pointing to the video page instead of the next guide article. Always verify against this table — guide articles travel through the guide page article sequence, not the video page sequence.

Page Type CTA Reference

Use this to confirm which navigation elements each page type gets before building. Do not add elements that are not in the ✅ column for that page type.

Page Type Nav Button Compact Info Bar Beehiiv Form Prompt Pack CTA
Video Page ❌ (step nav built-in) ❌ ✅ at id="[ROLE_SLUG]-prompt-pack" ❌
Guide Page ❌ ✅ “Video Path” bar — no button ❌ ❌
Article (Tactical or Guide) ✅ Next step or next article ❌ ❌ ✅ Steps 2–4
Prompt Pack Page ❌ ❌ ❌ ❌ (PDF button only)



📧 PROMPT PACK EMAIL GATE ARCHITECTURE — CRITICAL

This was the single largest source of rework in the HR rollout — 11 articles required correction because this architecture was not documented. The three pages in the prompt pack funnel have distinct roles. Confusing them breaks the email gate.

Page Purpose Has Beehiiv Form? Article CTAs link here?
Video Page
/[role]-videos/		 Learning path + EMAIL GATE ✅ YES — at id="[ROLE_SLUG]-prompt-pack" ✅ YES — via [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
Prompt Pack Page
/[role]-ai-prompt-pack/		 Post-subscription PDF download ONLY ❌ NO — never ❌ NO — never
Guide Page
/ai-for-[role]-guide/		 In-depth written guide ❌ NO ❌ NO

The Rule:

  • Article Prompt Pack CTAs ALWAYS link to: [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  • NEVER link article CTAs directly to the prompt pack page URL
  • The prompt pack page URL appears only on the prompt pack page itself (for the PDF download button)
  • The Beehiiv form lives on the VIDEO PAGE ONLY — never on the prompt pack page, guide page, or articles

What Goes on the Prompt Pack Page:

  • ✅ Hero section with role name and pack description
  • ✅ Direct PDF download button (href="[PDF_DOWNLOAD_URL]") — correct and intentional
  • ✅ Content grid (what’s inside, use safely, etc.)
  • ✅ “Back to [Role] Videos” secondary return link
  • ❌ NO Beehiiv email form
  • ❌ NO article-style navigation CTAs
  • ❌ NO links from other pages pointing here (except post-subscription redirects)

Beehiiv Anchor Requirement on Video Page:

The Beehiiv block on the video page MUST have id="[ROLE_SLUG]-prompt-pack" on its outer wrapper div. Without this anchor, all article #[ROLE_SLUG]-prompt-pack links scroll to the wrong location or nowhere. Example for HR: <div id="hr-prompt-pack" ...>



🚫 NEVER RULES — CRITICAL VIOLATIONS

These rules caused full re-audits in prior sessions. Each violation required rewriting multiple articles. They are listed here as prominent callouts — not buried in prose — because that is exactly what caused the drift.

🚫 NEVER — Use class="aiw-primary" inside article post content

This class only exists in theme templates. Every button and CTA in article post content must use 100% inline styles with no class attributes. This was violated in all 9 supplementary articles in one rollout and required a complete sweep to fix. Prevent it with check #8 in the pre-flight gate above.

🚫 NEVER — Swap callout labels between article types

Tactical articles ALWAYS use the callout label “Quick-Start Workflow”. Guide articles ALWAYS use the callout label “In-Depth Step N Guide” (where N is the actual step number). Reversing these was a systematic error across all 8 main paired articles in a prior rollout and required rewriting all of them.

🚫 NEVER — Place the callout block before the step label

The step label (<strong>AI at [ROLE] / Step N</strong>) is the first element in every article body. The cross-reference callout follows it. This order was reversed on all 8 main articles in a prior rollout. Pre-flight check #5 exists specifically to catch this.

🚫 NEVER — Point a Guide article Nav CTA at the video page

Guide articles move readers forward through the guide article sequence. The Nav CTA must link to the next guide article — not to the video page or a video page anchor. This error was found on guide articles 5673, 5674, and 5675 in a prior rollout.

🚫 NEVER — Write Step 3 content without naming specific tools

Step 3 (Tools & Automations) must mention specific tool categories and at least one named tool (e.g. ChatGPT, Notion AI, Zapier, Buffer, Canva). Generic “AI tools can help” language with no specific tools named is a Step 3 violation. Pre-flight check #3 requires verifying this against the Step-to-Topic Mapping Table.

🚫 NEVER — Create a paired article without immediately updating BOTH articles

When you create a new tactical or guide article that pairs with an existing article, update the existing article in the same session to add the cross-reference callout pointing back to the new one. Both directions must be live before ending the session — not “I’ll do the other direction later.”

🚫 NEVER — Omit !important from button and link color styles

The theme overrides link colors with !important declarations. Every inline button must include color:#111111!important; and text-decoration:none!important;. Every return link must include color:#9CCBFF!important;. Missing !important means the theme will override the colors silently — buttons may appear correct in editor but wrong on the front end.

🚫 NEVER — Link article Prompt Pack CTAs directly to the prompt pack page

The prompt pack page (/[role]-ai-prompt-pack/) is a post-subscription PDF download page. Article Prompt Pack CTAs must link to the video page email gate at [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack. Linking CTAs directly to the prompt pack page bypasses the email gate entirely. This error was found on all 11 Prompt Pack CTA buttons in the HR rollout and required a full correction pass across all articles.

🚫 NEVER — Add a Beehiiv form to the prompt pack page

The prompt pack page is a post-subscription destination — users land here after submitting their email on the video page. Adding a Beehiiv form creates double opt-in confusion and defeats the email gate. The Beehiiv form belongs only on the video page at id="[ROLE_SLUG]-prompt-pack".

⚠️ NEVER — Modify shortcodes

Never modify, regenerate, or guess the shortcodes:

RECOMMENDED

Google’s Gemini Push and Qualcomm’s ByteDance Deal Show Where AI Competition Is

News
Click to open / close video
investor_market_watcherai_news
,
Featured Article

Featured article needs role and step.

Add role and step attributes to this shortcode.

,
Supporting Video

Supporting video needs role and step.

Add role and step attributes to this shortcode.

,

AI Governance for Supply Chain Operations

Video URL needed

Pre-Dispatch Quality Review: Building an AI Audit System for Logistics

Video URL needed

Logistics Data Privacy: What to Keep Out of AI Tools

Video URL needed
. Fetch the page, read the existing shortcodes, copy exactly. Shortcodes with missing or altered attributes render as error blocks on the front end.

⚠️ NEVER — Run SEO without confirming Rank Math is active

Run wp_get_plugins before Phase 6. If Rank Math does not appear in the active plugins list, skip SEO entirely and flag it as pending. The wp_update_seo_meta call fails silently if the plugin is not active — no error, no update.

⚠️ NEVER — Change the PDF download button on prompt pack pages

The direct PDF download button on prompt pack pages is correct and intentional. Do not change it to a redirect. For all other article CTAs, link to the video page email gate at [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack — not directly to the PDF file and not to the prompt pack page URL.

⚠️ CRITICAL RULES — READ BEFORE TOUCHING ANY PAGE

1. Shortcode Rules

  • NEVER change, regenerate, or guess shortcodes:
    RECOMMENDED

    Google’s Gemini Push and Qualcomm’s ByteDance Deal Show Where AI Competition Is

    News
    Click to open / close video
    investor_market_watcherai_news
    ,
    Featured Article

    Featured article needs role and step.

    Add role and step attributes to this shortcode.

    ,
    Supporting Video

    Supporting video needs role and step.

    Add role and step attributes to this shortcode.

    ,

    AI Governance for Supply Chain Operations

    Video URL needed

    Pre-Dispatch Quality Review: Building an AI Audit System for Logistics

    Video URL needed

    Logistics Data Privacy: What to Keep Out of AI Tools

    Video URL needed
  • All shortcodes on existing role video pages are already correct. Fetch the page, read the shortcodes, copy them exactly — do not modify.
  • Shortcodes with missing attributes (role=, step=) render as error blocks on the front end.
  • NEVER add shortcodes to guide articles or tactical articles — they belong only on video pages and guide pages.

2. Inline Styles — !important Required

  • The theme uses !important on link color rules. ALL inline button and link styles MUST include !important.
  • Required on every button: color:#111111!important; and text-decoration:none!important;
  • Required on every return link: color:#9CCBFF!important;
  • Required on every Prompt Pack CTA button: color:#111111!important; and text-decoration:none!important;

3. No Class-Based Styles in Article Content

  • NEVER use class="aiw-primary" inside article post content — the class is only available in theme templates.
  • ALL buttons in article content must use 100% inline styles.

4. Featured Article Blocks

  • NEVER touch featured article sections — they are shortcode-controlled and will break if edited.

5. Prompt Pack Funnel — PDF and Email Gate

  • The direct PDF download button on the prompt pack page is correct and intentional. Do NOT change it to a redirect.
  • For all other article CTAs, link to the video page email gate at [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack — not to the prompt pack page URL and not directly to the PDF file.
  • The Beehiiv form lives on the video page only — never on the prompt pack page.
  • See the 📧 EMAIL GATE ARCHITECTURE section above for the full three-page funnel spec.

6. Diff-Based Execution

  • For existing role pages, always fetch the current page content first, then compare against the template. Only add/fix what is missing or broken. Never replace sections that already exist and are correct.

📋 SOURCE REFERENCE PAGE IDs

Fetch these pages at the start of each rollout to get current correct HTML. Always fetch live — do not use stored HTML.

Page ID URL What to copy from it
AI at Home Video Page 4472 /ai-at-home/ Video page structure, Beehiiv form placement and anchor format, “Go Deeper” section
Guide Article (with Prompt Pack CTA) 5562 /safe-boundaries-for-ai-troubleshooting-at-home-when-to-stop-and-call-a-professional/ Full guide article structure, Prompt Pack CTA block (note: href goes to video page anchor), Nav CTA block, return link
Tactical Article (with Prompt Pack CTA) 5556 /how-to-build-repeatable-household-checklists-that-dont-require-ai-every-time/ Tactical article with Prompt Pack CTA, Nav CTA, return link
Guide Page 4489 /ai-at-home-guide/ Guide page layout — note compact info bar format (no nav button)
Prompt Pack Page 4487 /ai-at-home-prompt-pack/ Prompt pack page layout, direct PDF download button — no Beehiiv form
Business Owner Video Page 2162 /ai-for-business-owners/ “Go Deeper After You Finish” section (source of truth)
Step 3 Tactical Article (tool/workflow) 4493 /ai-at-home-prompt-workflows/ Step 3 tactical article format — tool categories, prompt library, automations

📝 ARTICLE WRITING FORMAT GUIDE

Each page type has a specific writing format. Match the format to the page type — do not mix them.

Tactical Articles (quick-start workflow format)

Used for: short, action-oriented articles in the video page article grid. These are step-by-step workflow references, not deep guides.

Required sections in order:

  1. <strong>AI at [ROLE_NAME] / Step [N]</strong> — step label at very top
  2. Cross-reference callout (if paired with a guide article — see Section 5 below)
  3. Opening paragraph — one sentence on who this is for and what it does
  4. <h2>When to use this</h2> — specific trigger scenarios
  5. <h2>What you need before using AI</h2> — bulleted prerequisites + privacy reminder
  6. <h2>Simple workflow</h2> — numbered steps, 5–8 items
  7. <h2>What to verify before using the output</h2> — bulleted QA checklist
  8. <h2>Review-first rule</h2> — single paragraph on human responsibility
  9. Prompt Pack CTA block (if applicable to this step) — href = [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  10. Nav CTA block (always)

Guide Articles (narrative format)

Used for: longer, in-depth articles in the guide page article grid. These explain the why and how, not just the steps.

Required elements:

  1. <strong>AI at [ROLE_NAME] / Step [N]</strong> — step label at very top
  2. Cross-reference callout (if paired with a tactical article — see Section 5 below)
  3. Opening paragraph — sets up the problem this article solves, role-specific framing
  4. 3–5 narrative sections with <h2> headings — each section answers a distinct sub-question
  5. At least one specific, actionable example or process per section
  6. Prompt Pack CTA block (if applicable to this step) — href = [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  7. Nav CTA block (always)

Guide article tone rules:

  • Write in paragraphs, not bullet lists (use bullets only for genuine lists)
  • Each section should have a clear argument, not just a list of facts
  • Never re-explain concepts already covered in a prior step — assume the reader completed earlier steps
  • End with a clear takeaway or action, not a summary of what was just covered

Video Page Articles (first-person narrative format)

Used for: articles that directly support video content and appear in the video page article grid. These have a more direct, conversational tone — day-by-day or scenario-driven structure.

Required elements:

  1. Optional <article class="aiw-article"> wrapper
  2. Opening hook — names the specific frustration or problem
  3. Short, scannable sections with <h2> headings
  4. Practical, specific examples — not generic advice
  5. Prompt Pack CTA block (if applicable) — href = [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  6. Nav CTA block pointing to next video article in sequence

🔗 ARTICLE PAIRING SYSTEM

Every major topic should have both a tactical (quick-start) version and a guide (in-depth) version. Each article in a pair must have a cross-reference callout linking to its companion.

The Rule

  • Tactical article = quick-start workflow, lives in video page article grid
  • Guide article = in-depth methodology, lives in guide page article grid
  • Both articles in a pair must acknowledge each other with a callout at the top
  • The tactical article says: “Quick-Start Workflow — For in-depth coverage, see [Guide Article]”
  • The guide article says: “In-Depth Step N Guide — For a quick-start workflow, see [Tactical Article]”

AI at Home — Known Pairs

Topic Tactical Article (ID) Guide Article (ID)
Home project planning 4494 5559
Research smarter / source verification 4495 5560
Privacy — what to keep out of prompts 4496 5554
Scam awareness 4497 5561
Review-first habits 4498 5556

Callout Label Vocabulary

⚠️ LABEL FORMAT RULE: Guide articles use “In-Depth Step N Guide” — the step number is PART OF THE LABEL. Never write just “In-Depth Guide” without the step number. Never swap the label with the tactical label.

Article Type Callout Label Description line starts with
Tactical (general workflow) Quick-Start Workflow “This is the quick-start workflow version. For in-depth coverage…”
Tactical (habit-building) Habit-Building Workflow “This article covers building the [X] habit consistently over time…”
Guide (comprehensive, paired) In-Depth Step N Guide (N = step number) “This is the in-depth Step N guide. For a quick-start workflow…”
Guide (checklist) Review Checklist / [Topic] Checklist “This article provides the practical checklist for [X]…”
Guide (fundamentals) [Topic] Fundamentals “This article covers the foundational [X] every [role] user should know…”

🔧 VARIABLE REFERENCE

Complete every row before Phase 1. Do not start writing content with unfilled variables.

Variable Description Your Value
[ROLE_NAME] Human-readable role name
[ROLE_SLUG] URL slug prefix
[VIDEO_PAGE_ID] WordPress ID of role video page
[VIDEO_PAGE_URL] Full URL of role video page
[GUIDE_PAGE_URL] Full URL of role guide page
[PROMPT_PACK_URL] Full URL of prompt pack page (used ONLY on the prompt pack page itself)
[PROMPT_PACK_ANCHOR] Anchor on video page for Beehiiv block and article CTAs — format: #[ROLE_SLUG]-prompt-pack — this is what all article Prompt Pack CTAs link to
[BEEHIIV_FORM_ID] Role-specific Beehiiv embed form ID
[PDF_DOWNLOAD_URL] Direct URL to PDF (prompt pack page only)
[STEP_1_TACTICAL_URL] URL of Step 1 tactical article
[STEP_1_GUIDE_URL] URL of Step 1 guide article
[STEP_2_TACTICAL_URL] URL of Step 2 tactical article
[STEP_2_GUIDE_URL] URL of Step 2 guide article
[STEP_3_TACTICAL_URL] URL of Step 3 tactical article
[STEP_3_GUIDE_URL] URL of Step 3 guide article
[STEP_4_TACTICAL_URL] URL of Step 4 tactical article
[STEP_4_GUIDE_URL] URL of Step 4 guide article
[GUIDE_ARTICLE_1_ID] WP post ID — guide article 1
[GUIDE_ARTICLE_2_ID] WP post ID — guide article 2
[TACTICAL_ARTICLE_1_ID] WP post ID — tactical article 1
[TACTICAL_ARTICLE_2_ID] WP post ID — tactical article 2

✅ ONE-PASS EXECUTION CHECKLIST

PRE-FLIGHT (before writing a single word of content)

  1. Lock the complete article list — all titles, URLs, step assignments approved before writing begins
  2. Fill ALL variables above — every [BRACKET] before Phase 1
  3. Fetch [VIDEO_PAGE_ID] — read shortcodes, copy exactly, note Beehiiv form ID and anchor format
  4. Fetch source pages 4472, 5562, 4493 — confirm current HTML patterns
  5. List all post IDs for this role’s articles, noting which are tactical vs. guide
  6. Map the paired articles — identify which tactical articles pair with which guide articles
  7. Fill in the CTA Routing Table above with role-specific URLs before starting Phase 2
  8. Run wp_get_plugins — verify Rank Math is active before planning Phase 6
  9. Manually close comments NOW (WP Admin → Posts → Bulk Edit → Close Comments)

Phase 1 — Video Page Audit

  1. Fetch video page (wp_get_page [VIDEO_PAGE_ID])
  2. Verify “Go Deeper After You Finish” section — 5 cards, aiw-cardbg class
  3. Verify Beehiiv form embed is present at id="[ROLE_SLUG]-prompt-pack" — this anchor is required for all article CTAs
  4. Verify shortcodes are intact — DO NOT MODIFY
  5. Fix any missing sections using source pages 4472 and 2162

Phase 2 — Guide Articles

  1. Fetch each guide article post
  2. Confirm article type = Guide, confirm step number, confirm content fits step definition
  3. Verify step label appears FIRST — before callout
  4. Verify callout label = “In-Depth Step N Guide” (with step number)
  5. Verify article uses guide narrative format (see Section 3 above)
  6. Verify cross-reference callout is present if article is part of a pair
  7. Verify Prompt Pack CTA — fully inline styles, no class=”aiw-primary”, href = [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  8. Verify all buttons and links have !important
  9. Verify Nav CTA points to NEXT GUIDE ARTICLE (not video page)
  10. Verify Return CTA points to GUIDE PAGE

Phase 3 — Tactical Articles

  1. Fetch each tactical article post
  2. Confirm article type = Tactical, confirm step number, confirm content fits step definition
  3. Verify step label appears FIRST — before callout
  4. Verify callout label = “Quick-Start Workflow”
  5. Verify article uses tactical workflow format (see Section 3 above)
  6. Verify cross-reference callout is present if article is part of a pair
  7. Confirm whether each article should have a Prompt Pack CTA (Step 3 and Step 4 tactical articles often do)
  8. If Prompt Pack CTA present: verify href = [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack — NOT the prompt pack page URL
  9. Verify all buttons and links have !important
  10. Verify Nav CTA points to video page next step section
  11. Verify Return CTA points to VIDEO PAGE

Phase 4 — Guide Page Audit

  1. Fetch guide page — verify layout matches source page 4489
  2. Verify all article links point to correct URLs
  3. Verify each step group contains the correct articles
  4. Verify guide page has compact info bar (not a nav button) pointing to video page

Phase 5 — Prompt Pack Page Audit

  1. Verify PDF download button is present and points to correct [PDF_DOWNLOAD_URL]
  2. Direct PDF link is correct here — DO NOT change to redirect
  3. Verify NO Beehiiv email form is present on this page — the form lives on the video page only
  4. Verify NO article-style Nav CTAs are present on this page

Phase 6 — SEO Meta (only if Rank Math confirmed active)

  1. For each post/page: wp_update_seo_meta with focus_keyword, title, description
  2. Focus keyword = step topic + role name (e.g. “AI home budget planning”)
  3. If Rank Math not active: skip and note as pending

Phase 7 — Final QA

  1. Buttons are gold (#C9960A) with black text
  2. Return links are blue (#9CCBFF)
  3. No shortcodes appear as literal text on front end
  4. No class="aiw-primary" in any article post content
  5. All [BRACKET] placeholders replaced — none remain in published content
  6. All paired articles have cross-reference callouts linking to each other
  7. All guide article Nav CTAs point to next guide article (not video page)
  8. All tactical article Nav CTAs point to video page next step
  9. Step label appears before callout in every article
  10. All Prompt Pack CTAs link to [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack — not to the prompt pack page URL
  11. Prompt pack page has NO Beehiiv form
  12. Comments closed on all role articles

📊 STEP-TO-TOPIC MAPPING TABLE

Every article must answer its step’s core question. Check both the label AND the content — the content must match, not just the label. Use this table in pre-flight check #3.

Step Core Question Content That Fits Content That Does NOT Fit
Step 1
Basics / Foundations		 What does AI actually mean for my [role]? Beginner explainers, first workflows, quick wins, role-specific examples, foundational safety habits (privacy, review-first). Example titles: “Getting Started With AI,” “Your First AI Workflow,” “AI Basics for [Role]” Advanced tool-stack language without context; deep security/governance without framing it as foundational. Assume no prior AI knowledge.
Step 2
Daily Workflows / Production		 Where can I save time this week? Repeatable tasks, templates, SOPs, before/after workflow examples, checklists, scheduling patterns. Example titles: “Weekly Content Planning With AI,” “AI for Daily Task Management,” “Building a Repeatable Workflow” Generic productivity tips with no role pain point; vague “AI saves time” claims; tool deep-dives (those belong in Step 3)
Step 3
Tools & Automations / Growth Systems		 Which tools should I use and how do I connect them? Tool categories (chat AI vs. search AI vs. automation), prompt libraries, tool-to-task matching, simple automations, connecting AI to other tools. MUST NAME specific tools. Example titles: “AI Tools for [Role]: A Comparison,” “Setting Up Your First Automation,” “ChatGPT vs. Jasper for [Role]” Tool hype without workflow fit; no mention of limitations; ⚠️ any Step 3 article that names zero specific tools is a violation
Step 4
Security & Governance / Trust & Risk		 What could go wrong and how do I protect myself? Privacy rules, disclosure requirements, scam awareness, safe boundaries, verification habits, AI agreements, professional handoff rules. Example titles: “What Not to Share With AI,” “AI Disclosure for [Role],” “Building Trust with AI Content” Fear-based content with no practical next step; re-covering basics from Steps 1–3; primary topic is a workflow or tool (those belong in Steps 2–3)

Step alignment red flags to catch during audit

  • Step 3 articles with NO mention of specific tools, tool categories, or automations → needs tools section added
  • Step 1 articles covering deep security/governance → OK if framed as foundational basics, not advanced risk management
  • Step 4 articles that are primarily research workflows or project planning → misaligned; strengthen the verification/governance angle
  • Any article where the content could apply to ANY role with no editing → too generic; add role-specific examples

🚫 CONNECTOR LIMITATIONS

Limitation Workaround
wp_update_post does NOT support comment_status Manual bulk edit: WP Admin → Posts → Bulk Edit → Close Comments
wp_update_seo_meta requires Rank Math plugin active Run wp_get_plugins first to verify before attempting SEO phase
wp_get_post returns raw HTML — shortcodes appear as code, not rendered output This is correct behavior — read shortcodes from raw HTML and copy exactly
wp_create_page status options: “publish” or “draft” only Create as draft, then manually set to private in WP Admin
Connector intermittent “additional permissions” error Transient outage — wait 30–60 seconds and retry. Do not assume the update failed unless you receive an explicit error after multiple retries.

🚫 NEVER LIST — QUICK REFERENCE

  • NEVER modify shortcodes:
    RECOMMENDED

    Google’s Gemini Push and Qualcomm’s ByteDance Deal Show Where AI Competition Is

    News
    Click to open / close video
    investor_market_watcherai_news
    ,
    Featured Article

    Featured article needs role and step.

    Add role and step attributes to this shortcode.

    ,
    Supporting Video

    Supporting video needs role and step.

    Add role and step attributes to this shortcode.

    ,

    AI Governance for Supply Chain Operations

    Video URL needed

    Pre-Dispatch Quality Review: Building an AI Audit System for Logistics

    Video URL needed

    Logistics Data Privacy: What to Keep Out of AI Tools

    Video URL needed
  • NEVER change the PDF download button on prompt pack pages to a redirect
  • NEVER use class=”aiw-primary” inside article post content
  • NEVER redesign page layouts or CTA systems
  • NEVER add shortcodes without role= and step= attributes
  • NEVER touch featured article blocks (shortcode-controlled)
  • NEVER omit !important from button color and text-decoration styles
  • NEVER publish this reference page — keep as draft/private
  • NEVER run SEO phase without first confirming Rank Math is active
  • NEVER skip pre-flight variable collection
  • NEVER start building content before the complete article list is locked and approved
  • NEVER create a paired article without adding cross-reference callouts to both articles in the same session
  • NEVER write Step 3 content without mentioning at least one specific tool category and tool name
  • NEVER swap callout labels — Tactical = “Quick-Start Workflow” | Guide = “In-Depth Step N Guide”
  • NEVER place the callout block before the step label
  • NEVER point a guide article Nav CTA at the video page — guide Nav CTAs go to the next guide article
  • NEVER link article Prompt Pack CTAs to the prompt pack page — link to [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack
  • NEVER add a Beehiiv form to the prompt pack page — the form belongs on the video page only

💡 HTML PATTERN QUICK REFERENCE

Cross-Reference Callout (paired articles)

<div style="background:#1F2937;border-left:3px solid #C9960A;border-radius:8px;padding:14px 18px;margin:0 0 28px;">
<p style="color:#FFE6A3;font-size:12px;font-weight:700;margin:0 0 4px;text-transform:uppercase;letter-spacing:.06em;">[CALLOUT LABEL]</p>
<p style="color:#9CA3AF;font-size:14px;line-height:1.5;margin:0;">[DESCRIPTION] <a href="[URL]" style="color:#9CCBFF!important;text-decoration:underline;">[LINK TEXT]</a>.</p>
</div>

Prompt Pack CTA Block (guide and tactical articles)

⚠️ href goes to the VIDEO PAGE anchor — NOT the prompt pack page URL. Use [VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack.

<div style="background:#111827;border:1px solid rgba(245,185,33,.45);border-radius:16px;padding:22px 24px;margin:32px 0 8px;">
<p style="color:#FFE6A3;font-weight:900;text-transform:uppercase;letter-spacing:.06em;font-size:13px;margin:0 0 8px;">Prompt Pack Resource</p>
<h3 style="color:#fff;font-size:20px;line-height:1.2;margin:0 0 10px;">[HEADLINE]</h3>
<p style="color:#D1D5DB;font-size:15px;line-height:1.5;margin:0 0 16px;">[BODY TEXT]</p>
<!-- href = video page anchor, NOT the prompt pack page URL -->
<a href="[VIDEO_PAGE_URL]#[ROLE_SLUG]-prompt-pack" style="display:inline-block;background:#C9960A;color:#111111!important;border-radius:999px;padding:11px 22px;font-weight:900;text-decoration:none!important;font-size:14px;">Get the [ROLE_NAME] Prompt Pack</a>
</div>

Beehiiv Email Gate Block (video page only)

⚠️ Must use id="[ROLE_SLUG]-prompt-pack" on the outer wrapper. This is what all article Prompt Pack CTAs link to. Place inside a <!-- wp:html --> block on the video page. Never place on the prompt pack page, guide page, or articles.

<div id="[ROLE_SLUG]-prompt-pack" class="aiw-section aiw-cardbg" style="padding:24px 22px;">
  <div style="max-width:1060px;margin:0 auto;background:#111827;border:1px solid rgba(245,185,33,.45);border-radius:18px;padding:28px;">
    <div style="display:grid;grid-template-columns:1fr .95fr;gap:24px;align-items:center;">
      <div>
        <div class="aiw-kicker">Free Prompt Pack</div>
        <h2 style="color:#fff;margin:0 0 12px;font-size:28px;font-weight:900;line-height:1.15;">Get the [ROLE_NAME] Prompt Pack</h2>
        <p style="color:#D1D5DB;font-size:16px;line-height:1.55;margin:0 0 16px;">Enter your email to get the complete [ROLE_NAME] Prompt Pack, including these [N] ready-to-use workflow prompts:</p>
        <div style="display:grid;grid-template-columns:1fr 1fr;gap:0 16px;">
          <ul style="margin:0;padding-left:18px;color:#D1D5DB;font-size:14px;line-height:1.7;">
            <li>[Prompt 1]</li>
            <li>[Prompt 2]</li>
            <li>[Prompt 3]</li>
            <li>[Prompt 4]</li>
            <li>[Prompt 5]</li>
            <li>[Prompt 6]</li>
          </ul>
          <ul style="margin:0;padding-left:18px;color:#D1D5DB;font-size:14px;line-height:1.7;">
            <li>[Prompt 7]</li>
            <li>[Prompt 8]</li>
            <li>[Prompt 9]</li>
            <li>[Prompt 10]</li>
            <li>[Prompt 11]</li>
            <li>[Prompt 12]</li>
          </ul>
        </div>
      </div>
      <div style="text-align:center;">
        <div style="background:#0B1220;border:1px solid rgba(148,163,184,.35);border-radius:16px;padding:16px;margin:0 auto;">
          <script async src="https://subscribe-forms.beehiiv.com/v3/loader.js" data-beehiiv-form="[BEEHIIV_FORM_ID]"></script>
        </div>
        <p style="color:#9CCBFF;font-size:13px;line-height:1.45;margin:10px auto 0;max-width:280px;">By entering your email, you agree to receive this resource and occasional 4AIWorld emails. You can unsubscribe anytime.</p>
      </div>
    </div>
  </div>
</div>

Guide Page Compact Info Bar (no button — info only)

Guide pages get a compact info bar pointing to the video path. No nav button. Use the aiw-compact-video-cta class — it is already in the theme CSS.

<div class="aiw-compact-video-cta" style="background:#111827;border:1px solid rgba(245,185,33,.22);border-radius:12px;padding:14px 20px;margin:24px 0;display:flex;align-items:center;gap:14px;">
  <span style="color:#FFE6A3;font-weight:900;font-size:13px;text-transform:uppercase;letter-spacing:.06em;white-space:nowrap;">Video Path</span>
  <span style="color:#D1D5DB;font-size:14px;line-height:1.45;">The [ROLE_NAME] video page is the main learning experience — use it for structured lessons, featured videos, step-by-step progression, and guided path navigation.</span>
</div>

Nav CTA Button

<a href="[NEXT_URL]" style="display:inline-flex;align-items:center;background:#C9960A;color:#111111!important;border-radius:999px;padding:11px 22px;font-weight:900;text-decoration:none!important;font-size:14px;border:1px solid #E0B23A;">[NEXT_TITLE] →</a>

Return Link

<a href="[GUIDE_OR_VIDEO_URL]" style="color:#9CCBFF!important;text-decoration:underline;font-size:14px;">← Return to [PAGE_NAME]</a>

Primary Button (video/guide pages)

<a href="[URL]" style="background:#C9960A;color:#111111!important;padding:10px 20px;border-radius:999px;font-weight:800;text-decoration:none!important;font-size:14px;display:inline-block">[LABEL]</a>