Tour Guide
Each project's instructions were written for AI helpers: what and how, never why. Someone new had no friendly way to learn what a project is for.
A /tour command now walks a newcomer through the design project: its purpose, its neighbours, key ideas and common tasks. The rollout to other projects never happened.
Documents
With file names, on their own page →Start here
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Typing /tour starts a conversation about the project; /tour with a topic jumps straight to that stop.
A guided tour on request · came from Mark Parson
- A story of the design project, about a thousand words, now sits beside its technical instructions. In words
- It started as an assistant that could start on its own, and became a command, because only a person ever asks for a tour. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Typing /tour starts a conversation about the project; /tour with a topic jumps straight to that stop.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for a guide that shows a new person around
His prompt imagined a guide per project that knows how to get started and can explain the founding principles and purpose.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 5 key-change entries · 233 words · 0 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c30 →