Most of this site is written to be read. This page is about the other way to use it: hand a page to your coding agent and let it do the work. Applicable pages carry a "Run this with your coding agent" block with a ready-to-paste prompt. The prompt points your agent at the page's Markdown mirror and tells it to audit your store, or to implement against a blueprint, item by item.
Key takeaways
- Every checklist, blueprint, and implementation chapter ships a copyable prompt that works with any coding agent that can fetch a URL.
- Run the audit-only prompt first. It reports against every item and changes nothing, so you see the picture before you decide.
- The agent audits and implements, but it never invents your product data, and the judgment calls stay yours. Review everything before you ship.
What the Markdown mirrors are
Every page here has a plain-text twin at the same path with a .md on the end. The Agent Selection Checklist lives at /tools/agent-selection-checklist/, and its mirror lives at /tools/agent-selection-checklist.md. The mirror carries the same facts as the page, laid out for a machine to read: each item's statement, its stable ID, its evidence type and source, and the prompt itself.
A coding agent reads the mirror instead of scraping the rendered page. That is why the prompt starts by telling your agent to fetch the mirror: it gets the full, structured checklist in one request, IDs and all, with none of the page furniture in the way.
The three steps
- Open the page for the checklist, blueprint, or chapter you want to act on.
- Copy the prompt from its "Run this with your coding agent" block. On the checklists there are two prompts side by side; start with the audit-only one.
- Paste it into your coding agent in the repository for your store, and let it work. The prompt handles the rest: it fetches the mirror, detects your platform, works through the items, and reports back.
Any coding agent that can fetch a URL works, whether that is Cursor or a terminal-based agent. If yours cannot fetch URLs, the prompt says so and asks you to paste the document in.
What a good audit report looks like
The audit-only prompt produces a report keyed to the checklist's item IDs, with each item marked pass, fail, needs human decision, or not applicable. A good report quotes its evidence and stops rather than guessing.
Platform detected: WooCommerce.
a-bot-access-01: pass. Your robots.txt allows OAI-SearchBot, Claude-SearchBot,
and PerplexityBot, with no blanket AI-crawler block.
a-structured-data-01: fail. Your Product JSON-LD carries no price; the price is
only written into the page after client-side JavaScript runs, so an agent reading
the markup sees no offer. Fix: emit price and priceCurrency (ISO 4217) in the
server-rendered JSON-LD.
a-checkout-ops-02: needs human decision. I cannot tell from the code how fresh
your inventory really is; that depends on your fulfillment process, not the code.
Tell me your real restock and sync cadence and I will judge it against what agents
expect. I did not guess a number.
Summary: of the items that apply to your store, 1 passed, 1 failed (price is
JavaScript-only), and 1 needs a decision only you can make. Several items that
assume an agentic-checkout protocol were marked not applicable, because you have
not installed one yet. Nothing was changed; this was an audit-only run.Notice what the report does not do. It does not invent a GTIN, a price, or an inventory cadence to make an item pass. Where the data is missing or the call is yours, it says so and stops. That restraint is written into every prompt on the site, and it is the difference between a report you can trust and a report that quietly makes things up.
What the agent will and will not do
The agent reads your code and configuration, checks them against the document, and (in the audit-and-fix and implement prompts) makes small, reviewable changes once you approve them. It stops and asks before anything destructive or anything that touches customer-facing copy, prices, or checkout.
What it will not do is decide your business. It will not fabricate ratings or review counts, invent GTINs or other identifiers, or guess delivery windows, prices, or return terms. Where a piece of data is missing, it lists exactly what you need to supply. The audit and the implementation are the agent's job; the judgment calls and the real business data stay yours. Review everything it changes before you ship it, because it is your store.
Where to start
Pick the surface that matches what you want to do:
- The Agentic Shopping Readiness Checklist if you want to know whether agents can find, read, and buy from your store at all.
- The Agent Selection Checklist if you are already eligible and want to know why agents are not choosing you.
- The blueprints if you want the agent to implement a specific machine surface, such as a token-efficient product feed or an edge-cache config.
- The AI shopping crawler reference if you want to check which crawlers can reach your store.
New to the whole topic? Start Here is the 30-minute triage that points you at the right checklist first.