Why Markdown files make good shared memory for AI
Short answer
Markdown is plain text that every AI app reads and writes well, people can read it too, and it is easy to version. Kept in one shared Space with every version saved, it becomes memory that no single AI app owns.
Why Markdown
- Plain text: no app or format lock-in.
- Readable by people and by every AI app.
- Small and easy to compare between versions.
How Winskel stores it
- Files are Markdown, up to 256 KB each.
- Every save makes a new numbered version with a SHA-256 fingerprint.
- An AI can read the latest, the accepted, or one exact version.
- Clashing edits keep the older one as a conflict version; newer text is never overwritten.
Write for the next reader
A new teammate may need a project brief, while a reviewer may only need the behavior that changed. Keep the first paragraph useful to that reader. Prefer brief excerpts and pointers to other records over pasting a full conversation or copying the same decision into several notes.
Choose files by what readers need to find
Use a few small notes with distinct purposes. A short PROJECT.md can explain the goal, DECISIONS.md can record choices the team agreed on, and QA.md can hold checks and open questions. The filenames are examples. Pick names that match how teammates will ask for the information, and use descriptive headings so a person can skim the file without opening an old chat.
Markdown is most useful when it carries the part of the work you actually want to share. A repository stays in Git and a private conversation stays with its app. If a coding agent needs to pass a result to a chat app, have it write a small Markdown note with the observed behavior, the source version and what the next person should review.
When a decision changes, keep a readable description of what changed and why. An earlier reviewer can still cite the version they used, while a later agent can explicitly read the new version. If the note keeps growing, split durable decisions from working notes and leave a clear pointer in the handoff.
To see whether the structure works, ask a connected AI to read only the selected file and answer one project question. If it needs the whole conversation to answer, put the missing reason or assumption in the note.
Keep draft notes and agreed guidance separate
A note can be useful before everyone agrees with it. Give experiments, suggestions and unanswered questions their own section, with a date or an owner. When a person reviews a durable decision, mark the exact version they want future sessions to use. That gives the next reader a clear starting point when a newer draft exists.
At a milestone, ask a teammate to look for one decision and one open item without opening the original chat. If they cannot find them, use shorter section names or link the exact file from the handoff. Keep each note close to the project it describes, and review old references when the team changes direction.
Questions
- Can I upload PDFs?
- No. PDFs, images and other file types are not supported.
Related guides
- How Winskel worksHow your team’s AI shares versioned filesWinskel Spaces keep Markdown files with numbered versions and fingerprints, so every AI on the team reads the same text.
- Why one SpaceWhy AI chats lose context, and how to keep itAI chats forget because context lives inside one chat in one app. Here is how to keep the decisions and files your next chat needs.
- Why one SpaceKeeping versions of the notes your AI writesAI agents rewrite notes often. Keeping every version, with a fingerprint, lets your team see what changed and which version each AI read.