Trail builder

Build a trail

A short list of places, in order, with a line about each — then a page you can hand to someone. Talk it out with your own AI or fill in the form; either way it takes a few minutes.

A page Clean, readable, works on a phone. Your words, not brochure copy.
A code that is the trail Not a link to a lookup — the whole trail is inside the QR itself. Scan it and the page opens. Nothing is stored on this server to make that work.
A link that comes back The same trail as a link — hand it to somebody, or mail it to yourself. There is no account here, so opening your own link later is how you get the trail back to change it.
A file you keep One HTML file. It opens with no internet, it carries its own QR, and it does not call back here. Yours whatever happens to this site.

Rather talk it out? Build it with your own AI

Copy the prompt into whatever chat you already have open — ChatGPT, Claude, Gemini, anything. It interviews you, then hands back a block of JSON. Paste that back here and the form fills itself in. Nothing is sent from this page to any AI; you bring your own, and it costs you nothing here.

1 — Copy this into your chat

I want to build a short walking trail — a handful of places, in order, with a line about each. Interview me, one question at a time.

START WITH THE CRITERION. Before you ask for places, ask me what gets a place ON this list. Then who is walking it and when, then which places I already have in mind. Once there is a list to look at, ask what determines the ORDER — distance, a route, my own ranking.

SEARCHING AND SUGGESTING ARE DIFFERENT PERMISSIONS. Search freely: to check what I give you, and to fill in addresses, hours and booking. Only OFFER new places when I ask for suggestions — offer them, never add them. Nothing enters the list until I say yes, and never a place from memory.

FACTS COME FROM ME OR FROM A LOOKUP, NEVER FROM MEMORY. Name the lookups: say so in conversation, and put them in that stop's "source" field — one stop may have more than one. I see "source" while I review; it never appears on the finished page. An address becomes a map pin somebody walks to, so a guessed one is worse than none.

CHECK WHAT I GIVE YOU. If a place I named has moved, closed, changed its hours or gone walk-in only, tell me. Correct the facts; keep my name for the place. If I keep my version anyway, use mine and note the discrepancy once — then let it go.

ASK ME WHY. If I have not told you why a place is on the list, ask. Do not fill "note" with facts you found: hours and booking have their own fields, and "note" is my reason in my words, so keep my phrasing and do not upgrade it into brochure copy.

THE NAME AND THE INTRO ARE MINE TOO. Ask me for the trail's name, or draft one and get my yes. Build the intro only out of what I have already told you, and add nothing I have not said.

IF THE SCOPE SPLITS — more than one list, book-ahead versus walk-in, or one per direction — say so, and we finish one list at a time.

IF I ASK WHAT IS ON THE LIST, show me the stops so far in order, plus anything you are still waiting on from me.

When I say done for a list, output THAT LIST as JSON in a fenced code block, and nothing else in that message. Then wait — a finished list is a checkpoint, not the end of the conversation, and I may start another one.

```json
{
  "trail_builder": 1,
  "name": "the trail's name",
  "intro": "a sentence or two on what this is and who it is for",
  "stops": [
    {"title": "the place",
     "note": "why it is on the list, in my words",
     "address": "street address, from me or from a lookup",
     "hours": "e.g. Saturday until 1:30 AM",
     "booking": "e.g. reservations or walk-in",
     "source": "the lookups a fact came from, if any",
     "links": [{"label": "Menu", "url": "https://..."}]}
  ]
}
```

Rules for the JSON: up to 30 stops, in the order we agreed. Everything except "title" is optional — leave a string empty, and "links" absent or [], rather than filling it with something you are not sure of; never a link entry with an empty url. Keep "hours" and "booking" short. Up to 3 links per stop, each starting http:// or https://, each LABELLED for what it is — "Menu", "Reservations", "Tickets" — and pointing at the page that MATCHES its label, not the homepage.

Trail name What is this? optional

Stop 1 Name Why it is on the list optional Address optional — becomes a map link

Hours optional

Booking optional

Link 1 optional

URL

Stop 2 Name Why it is on the list optional Address optional — becomes a map link

Hours optional

Booking optional

Link 1 optional

URL

Stop 3 Name Why it is on the list optional Address optional — becomes a map link

Hours optional

Booking optional

Link 1 optional

URL

Stop 4 Name Why it is on the list optional Address optional — becomes a map link

Hours optional

Booking optional

Link 1 optional

URL

Up to 30 stops.