1---
2name: demo
3description: Build one clickable demo page with 10 genuinely different options (designs, layouts, copy, flows, or approaches) side by side, so the user can pick by number. Use when the user types /demo, or says "demo a ticket", "make a demo", "show me options", "give me 10 versions", "demo some variants".
4---
5
6# demo: one page, 10 options
7
8Show 10 distinct takes on the thing the user named, on one page, so they can compare and pick by number.
9
10## Ticket status
11
12When the subject is a Linear ticket (ID, URL, or a ticket from the conversation),
13first fetch it and confirm its identity, team and current status. If it is in
14Triage or Backlog, move it to the team's actual In Progress status (soclever:
15`In-progress`) before planning or building the demo, and read back to verify.
16Change only the status in this update. If it is in any other status, or the user
17says to keep it where it is (e.g. "demo this but keep it in backlog"), leave its
18status unchanged. This overrides a general ticket-pickup rule for demo requests. Do not
19ask for confirmation; report a failed update honestly. Requests without a
20ticket need no tracker update.
21
22## Steps
23
241. **Pin the subject.** Use what the user named: a component, a page, a hero section, copy, a flow, a pricing layout, and so on. Ask only if there is no subject at all, and then use AskUserQuestion.
252. **Plan 10 real differences.** Before building, write one line per option naming its idea. Each option must differ in structure, concept or tone, not just in colour or spacing. If two lines sound alike, replace one.
263. **Build one self-contained HTML page:**
27 - Options numbered 1-10, one visible at a time, with a compact switcher (tabs or segmented control). Keys `1`-`9` and `0` (for 10) jump to an option, and left/right arrows step through them.
28 - Each option gets a 2-4 word name. No descriptions or captions.
29 - Use real content from the user's project, not lorem ipsum.
30 - Follow the project's design system if it has one. Every option ships only what its job needs, with no extra labels, captions or chrome.
31 - Support light and dark, and make it work at phone width.
32 - Remember the last viewed option in `localStorage` (wrapped in try/catch).
334. **Share it** the easiest way your environment offers: a published page or artifact if you have one, otherwise a local file path. If the demo belongs inside a running app, put it on a throwaway route instead and give the local URL.
34 Then open it in the user's regular browser, full window: `open <url or file>` on macOS, `xdg-open` on Linux. Never leave it only in an editor or side-pane preview.
355. **Check it once** in a browser: all 10 render and the keys switch between them.
366. **Reply** with the link, then the 10 names as a numbered list, then one line: "Pick a number (or mix, like '3 with 7's header')."
37
38## Rules
39
40- Always exactly 10 options, unless the user gives a different number.
41- No option is a straw man. Each should be one you could defend shipping.
42- Once the user picks, build the chosen option properly in the real code. The demo page is throwaway.
43