# Make an Animated Map of Anything: start prompts

Paste this into your AI after you get Make an Animated Map of Anything.

There are two prompts. Paste the first one in the session where you build your first map. Paste the second one at the start of every later session, so your AI keeps the map true and uses it as memory.

## Prompt 1: first session (interview, then build)

```text
I bought the journal "Make an Animated Map of Anything". It is the method, tested in real builds, for turning a business, a project, an idea or a process into one animated, clickable map that a person reads in seconds and that you can read as memory. Your job is to read it, interview me, and build my first map with the free map kit, one step at a time, checking each step on screen.

WHAT IT IS FOR
One picture of how my thing works: the pieces, what feeds what, and the state of each piece (working, partly, stuck, missing, my call, or not measured). It is not a report and not a poster: every piece answers what it is, how it is today, what to fix next, the goal, and who does it.

HOW TO GET AND READ THE JOURNAL
- With the Vibedna connector: call list_library, find the slug make-an-animated-map-of-anything, then read_journal(slug="make-an-animated-map-of-anything", part=1), then part=2, 3 and so on until there are no more parts. Read every part before you start.
- With Journals DNA paired: journal_get(slug="make-an-animated-map-of-anything") writes it into ~/.journal/library; read it from there with journal_read (use offset and limit).
- Read "The whole build, in order" first: it is the method on one page. Then each section as its step comes up.

GET THE KIT
Download https://vibedna.ai/drops/map-kit.zip and unzip it. Read map-kit/RECIPE.md fully: it is the truth about what the kit can do. You only ever edit map-data.js, never map.html.

ASK ME FIRST
1. The one question the map must answer.
2. Then the interview from the journal, short, grouped by topic, each question with a recommended answer. Read anything I already wrote before you ask, and never ask what is already answered.

THE BUILD, IN THE JOURNAL'S ORDER
1. List the pieces as a plain list and show it to me.
2. Split into parts (tabs), name the columns left to right, place the pieces, draw the lines and the route.
3. Write every piece in my words, from facts you checked, with the date. Anything nobody checked is state u (not measured), never a guess. Use r only for something you saw fail.
4. Fill map-data.js, open map.html, press F12: the Console and the note at the bottom of the page must show 0 problems.
5. Click every piece, read every card aloud to me, check it 390 px wide and turned sideways.

NEVER
- Never open or paste a map-data.js someone else sent. To share a map, use Save map file (map.json); to look at someone else's, use Open map file.
- Never put passwords, keys, customer names or bank details on the map.
- Never publish, share or host the map without my yes.
- Report what you could not check (a phone, a second reviewer) instead of saying it passed.
```

## Prompt 2: every later session (keep it true, use it as memory)

```text
We use the map from "Make an Animated Map of Anything" as the shared picture of my project. Before you change anything, open map-data.js, find the piece you are about to touch and read the note it points to (its note field). When you finish, update that piece: its state, its now line with the date and what you checked, and its fix. A state with no check named goes to u. Status comes from proof, never from a schedule or a plan. Then open map.html and confirm the Console and the note at the bottom show 0 problems. If the journal is not loaded in this session, read "Keep it true" and "Maps your AI can read" from it first.
```