# Example prompts

Prompts that get good tours from a coding agent.

Agents write the best tours when they read the page's code first and point at stable selectors. Name the file or route, the steps you want, and say "draft".

## A tour for one page

> Use GuideMark. Call get_project first. Then read `src/pages/pricing.tsx` and create a three-step draft tour on pageUrl "/pricing": the billing toggle, the most popular plan, and the plan for larger teams. Use ids or data attributes that exist in that code. One short sentence per step. Don't publish it.

## After shipping a feature

> I just added the "Export CSV" button to the invoices table. Add a GuideMark beacon tooltip on it as a draft, using its `data-testid`, explaining what the export includes. Then request a review.

## Find gaps

> Use GuideMark: list_tours and list_beacons, then read our routes and tell me which important pages have no guidance. Suggest one tour per page, but don't create anything yet.

## Keep tours in sync

> I renamed `#plan-pro` to `#plan-studio` in pricing.astro. Find GuideMark tours whose steps use the old selector and update them. If a tour is live and you can't edit it, tell me which one.

## Tips

* **Stable selectors.** Ask for ids or `data-*` attributes. Generated class names (`.css-1x2y3z`) break on the next build.
* **pageUrl is a path** on your project's domain, like `/settings/billing`, not a full URL or a file path.
* **Short steps.** One idea per step; three to five steps per tour.
* **Preview before publishing** with the tour's `?playTour=` link.
* **Write the rules down once.** Paste the [AGENTS.md block](/docs/agents/install-with-agent#tell-your-agent-how-to-use-guidemark) into your repo, so every agent follows them without being told.