Quick wins

The fix lists from the latest run of every prompt set, core sets first, then fastest expected ranking gain: prompts a fix could flip per working day, each weighted by what it has left to win (one minus its recommended rate over the last two weeks; named, for an info prompt). Mark a fix with the commit or pull request you submitted for it; open leaves out the ones you have. A later fix for the same page stays open, with what was tried before.

Publish popcorn.zone/docs/guides/choosing-prompts with measured prompt-count variance low documentation effort M flips 1 Finding out whether AI assistants recommend us

Where: popcorn.zone/docs/guides/choosing-prompts
Must say: Give a method for picking buyer questions: split them into category, comparison, problem and info prompts, and store them as TOML files changed through pull requests. Give sample-size guidance only after measuring it: run one prompt set repeatedly in Popcorn and publish the observed run-to-run variance in the recommended rate. Do not cite a prompt count without that data.
Done when: A re-run of prompt 11 cites this page.
Displaces: https://cloro.dev/blog/ai-visibility-sample-size/
Why: P11 codex search: top pick 'Ahrefs Brand Radar', shaped by ahrefs.com/aeo/choose-prompts-to-track.

Prompt for Claude Code

# Publish popcorn.zone/docs/guides/choosing-prompts with measured prompt-count variance

When buyers ask an AI assistant the questions below, it explains the topic without naming us or citing our pages. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Which questions should we track to measure AI visibility, and how many prompts do we need before the numbers mean anything?

## What the assistant said
P11 codex search: top pick 'Ahrefs Brand Radar', shaped by ahrefs.com/aeo/choose-prompts-to-track.

## Who wins the question today
https://cloro.dev/blog/ai-visibility-sample-size/. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/choosing-prompts so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Give a method for picking buyer questions: split them into category, comparison, problem and info prompts, and store them as TOML files changed through pull requests. Give sample-size guidance only after measuring it: run one prompt set repeatedly in Popcorn and publish the observed run-to-run variance in the recommended rate. Do not cite a prompt count without that data.

## Done when
A re-run of prompt 11 cites this page.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

From this run