[
  {
    "id": "branded-ad-concepts",
    "title": "Generate a reviewable batch of ad concepts",
    "description": "Explore distinct messages while preserving brand rules and factual claims.",
    "category": "Creative",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Beginner",
    "evidence": "Practitioner report",
    "output": "A creative matrix with audience, angle, headline, visual direction, and claim evidence.",
    "inputs": [
      "Approved offer facts and brand guidelines",
      "Audience problem statement and placement specifications"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Create [number] distinct ad concepts for [offer] aimed at [audience]. Use [brand rules] and only [approved claims]. Vary the underlying angle rather than swapping adjectives. For each, return headline, supporting copy, visual direction, placement, and evidence for every factual promise. Flag unsupported claims. Do not fabricate testimonials or publish anything. End with a comparison matrix for the creative reviewer.",
    "steps": [
      "Approve the offer facts, audience, and brand constraints.",
      "Choose a small set of genuinely different message angles.",
      "Generate concepts and review claim support before rendering assets.",
      "Export selected designs to the required sizes and inspect text and cropping."
    ],
    "review": "A brand owner checks claims, readability, licensing, and whether the creative matches the landing page.",
    "limits": [
      "Draft concepts are not finished ad files.",
      "The source\u2019s reported speed or output count does not predict your workflow."
    ],
    "measure": "Concepts accepted for testing, factual corrections, and performance after controlled testing.",
    "sources": [
      {
        "title": "Building an ad generator",
        "url": "https://x.com/codyschneider/status/2026421911538762176",
        "author": "Cody Schneider",
        "note": "February 24, 2026. Reports building an ad generator with Claude Code. Our guide adds a creative matrix and claim review; speed and volume are not guaranteed.",
        "kind": "Practitioner report"
      }
    ]
  },
  {
    "id": "marketing-performance-brief",
    "title": "Build a GA4 and Search Console decision brief",
    "description": "Connect search visibility to site behavior without conflating different metrics.",
    "category": "Measurement",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Intermediate",
    "evidence": "Practitioner report",
    "output": "A concise report with metric definitions, changes, anomalies, and proposed investigations.",
    "inputs": [
      "Authorized GA4 and Search Console exports",
      "Reporting period and conversion-event definitions"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Analyze [GSC export] and [GA4 export] for [period]. Keep search clicks separate from sessions and explain differences in scope and attribution. Show changes against [comparison period], identify anomalies, and cite the source table for each number. Propose investigations rather than asserting causes. Include missing data and questions for the analyst. Do not change tracking or site content.",
    "steps": [
      "Match dates, time zones, properties, and event definitions.",
      "Reconcile totals in each source before combining insights.",
      "Generate the brief with separate sections for acquisition and on-site outcomes.",
      "Have the analyst approve conclusions and assign investigations."
    ],
    "review": "Verify event definitions, attribution windows, filters, and whether comparisons use the same scope.",
    "limits": [
      "The two products count different things; totals need not match.",
      "Privacy thresholds and search-data coverage can hide rows."
    ],
    "measure": "Reconciliation accuracy and investigations that lead to a checked decision.",
    "sources": [
      {
        "title": "GA4 and Search Console dashboard",
        "url": "https://x.com/codyschneider/status/2054684449086841166",
        "author": "Cody Schneider",
        "note": "May 13, 2026. Reports connecting search and analytics data to a dashboard. We do not treat the reported setup time as a repeatable benchmark.",
        "kind": "Practitioner report"
      },
      {
        "title": "Search Console query API",
        "url": "https://developers.google.com/webmaster-tools/v1/searchanalytics/query",
        "author": "Google",
        "note": "Official query interface for search-performance data; returned rows may not cover all data.",
        "kind": "Official documentation"
      },
      {
        "title": "Google Analytics Data API",
        "url": "https://developers.google.com/analytics/devguides/reporting/data/v1",
        "author": "Google",
        "note": "Official documentation for analytics reports and dashboards. Account access and compatible dimensions are required.",
        "kind": "Official documentation"
      }
    ]
  },
  {
    "id": "comparison-keyword-research",
    "title": "Research comparison keywords worth answering",
    "description": "Find decision-stage questions you can address with genuine product knowledge.",
    "category": "Search content",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Beginner",
    "evidence": "Practitioner report",
    "output": "A research table containing intent, market, evidence, existing coverage, and editorial fit.",
    "inputs": [
      "Your actual product capabilities and competitor facts",
      "Authorized keyword-tool results for a specified location and language"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Review [keyword data] for [product, market, language]. Identify comparison and alternative queries that our product can honestly help answer. For each, classify intent, show supplied metrics and their date, link supporting product facts, and check [existing content inventory] for overlap. Do not invent volume, capabilities, or superiority. Recommend a small editorial shortlist with unanswered research questions.",
    "steps": [
      "Specify the audience, geography, language, and real alternatives.",
      "Gather authorized keyword data and a current content inventory.",
      "Research product facts before selecting a comparison angle.",
      "Approve topics based on usefulness and originality, not page count."
    ],
    "review": "A product expert verifies comparison criteria and that competitor information is current.",
    "limits": [
      "Keyword metrics are estimates, not guaranteed traffic.",
      "An unsupported comparison can mislead buyers even if it ranks."
    ],
    "measure": "Useful topic approvals, factual corrections, and qualified engagement after publication.",
    "sources": [
      {
        "title": "Keyword research workflow",
        "url": "https://x.com/codyschneider/status/2028485546649993664",
        "author": "Cody Schneider",
        "note": "March 2, 2026. Describes keyword research using Claude Code, Keywords Everywhere, and DataForSEO. Our guide focuses on comparison intent and factual review.",
        "kind": "Practitioner report"
      }
    ]
  },
  {
    "id": "paid-media-diagnostic",
    "title": "Diagnose ad performance before changing spend",
    "description": "Build a hypothesis-driven review from enough data to support a decision.",
    "category": "Measurement",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Intermediate",
    "evidence": "Practitioner report",
    "output": "A diagnostic memo with observations, possible explanations, and a limited test proposal.",
    "inputs": [
      "Approved campaign and conversion exports",
      "Unit economics, attribution window, and test constraints"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Review [ad performance data] for [period] against [business objective]. Separate observed changes from hypotheses. Consider spend, volume, conversion quality, attribution delay, and sample size. List missing evidence before recommending a test. Define one bounded experiment with a control, budget limit, stop condition, and review date. Do not modify campaigns or promise a cost reduction.",
    "steps": [
      "Check tracking health and the definition of a valuable conversion.",
      "Prepare comparable time windows and record external changes.",
      "Generate competing explanations and choose what can be tested.",
      "Approve a bounded experiment and review its full business result."
    ],
    "review": "The media owner validates attribution, sample size, spend limits, and conversion quality.",
    "limits": [
      "A lower cost per lead can accompany lower lead quality.",
      "One creator\u2019s account-level result is not a general prediction."
    ],
    "measure": "Qualified conversion cost and incremental evidence from approved tests.",
    "sources": [
      {
        "title": "Facebook ads agent example",
        "url": "https://x.com/codyschneider/status/2055317298420859021",
        "author": "Cody Schneider",
        "note": "May 15, 2026. Reports an advertising-agent experiment. Performance claims describe one account and have not been independently reproduced.",
        "kind": "Practitioner report"
      }
    ]
  },
  {
    "id": "customer-problem-research",
    "title": "Find customer problems in an approved research corpus",
    "description": "Preserve what people actually said and the evidence that disagrees with your hypothesis.",
    "category": "Customer research",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Beginner",
    "evidence": "Practitioner report",
    "output": "A problem map with source excerpts, context, counterexamples, and interview questions.",
    "inputs": [
      "Permitted discussion excerpts or approved interview notes",
      "Research question and a description of the intended audience"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Analyze [approved corpus] for [research question]. Identify recurring problems in the participants' own terms and attach source IDs. Separate a direct statement from your inference. Include counterexamples, sampling limitations, and questions to validate in interviews. Do not treat frequency in this sample as market prevalence or infer sensitive personal traits. Keep quotes short and attributable.",
    "steps": [
      "Define the research question and permitted collection method.",
      "Retain source context and remove unnecessary personal details.",
      "Review the suggested themes against both supporting and contradictory excerpts.",
      "Validate important hypotheses through direct customer research."
    ],
    "review": "A researcher checks whether the summary preserves context and represents minority or conflicting views.",
    "limits": [
      "Online discussions are a biased sample.",
      "A frequent complaint does not establish willingness to pay."
    ],
    "measure": "Traceable themes, contradicted assumptions surfaced, and interview validation.",
    "sources": [
      {
        "title": "Audience problem research",
        "url": "https://x.com/codyschneider/status/1742727596616392764",
        "author": "Cody Schneider",
        "note": "January 4, 2024. Describes using public discussions to research customer problems. Our workflow uses an approved research corpus and preserves conflicting evidence.",
        "kind": "Practitioner report"
      }
    ]
  },
  {
    "id": "expert-interview-content-brief",
    "title": "Turn an expert interview into an original article brief",
    "description": "Use specific experience to answer a reader\u2019s question and separate it from unsupported claims.",
    "category": "Search content",
    "tool": "Approved AI assistant",
    "toolUrl": null,
    "level": "Beginner",
    "evidence": "Practitioner report",
    "output": "A sourced article outline with expert examples, verification tasks, and useful next steps.",
    "inputs": [
      "An approved interview transcript",
      "Reader question, source materials, and existing articles"
    ],
    "connections": "Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.",
    "prompt": "Use [approved transcript] to build an article brief answering [reader question]. Identify concrete expert observations, distinguish opinion from factual claims, and cite transcript timestamps. Propose an outline with original examples, missing research, and relevant existing pages. Do not invent quotes or results. Flag statements requiring external verification and explain what the reader should be able to do afterward.",
    "steps": [
      "Choose a real reader problem and get permission to use the interview.",
      "Extract distinctive examples with their original context.",
      "Build the brief and fill factual gaps from reliable sources.",
      "Have the expert review the draft before an editor publishes it."
    ],
    "review": "The expert approves quotations and interpretation; the editor checks factual support and original value.",
    "limits": [
      "An interview alone does not substantiate every factual claim.",
      "Publication does not guarantee indexing, traffic, or rankings."
    ],
    "measure": "Expert corrections, reader usefulness, and relevant engagement over time.",
    "sources": [
      {
        "title": "Expert input in an SEO workflow",
        "url": "https://x.com/codyschneider/status/2044551369235784037",
        "author": "Cody Schneider",
        "note": "April 15, 2026. Reports a research and transcript-based article workflow. We do not present its ranking claims as expected results.",
        "kind": "Practitioner report"
      }
    ]
  }
]