Lettuce Docs Tags Graph

Save Claude's work into your vault

#docs#recipe#agent
~4 min read

Save Claude’s work into your vault

Claude produces two kinds of output worth keeping: Markdown (notes, summaries, reports) and self-contained HTML (dashboards, briefings, interactive artifacts). Both belong in your vault — Markdown becomes a normal note, and .html files render natively in the Lettuce reader on Mac and iPhone (read-only, sandboxed, shown with a globe icon). This recipe gives Claude standing instructions so its work lands there automatically.

Setup

Two ways in, pick either (or both):

The prompt: one block that routes everything to Lettuce

Paste this into your global ~/.claude/CLAUDE.md (every session), a project’s CLAUDE.md (that project only), or a chat client’s custom instructions. Change ~/Notes to your vault folder — iCloud users, that’s the folder you opened in Lettuce. It covers all of Claude’s keepable output: Markdown notes and reports, and self-contained HTML artifacts.

# Save your work into my Lettuce vault

My Lettuce vault is the folder ~/Notes. When I ask you to save, file, or keep
anything — a note, summary, report, briefing, dashboard, or "artifact" — write
it there as a plain file. No commit, no server: Lettuce picks the file up
instantly and it syncs to my phone.

## Markdown (notes, summaries, reports)

- Write it as Markdown with a descriptive Title Case filename.
- Add frontmatter with `tags`; wiki-link related notes with [[Note Title]]
  so it joins my graph.
- Put it in the folder that fits what it is; use Inbox/ when unsure.

## HTML artifacts (briefings, dashboards, interactive reports)

- Write a COMPLETE, self-contained HTML file into
  Briefings/<project>/YYYY-MM-DD-<kebab-slug>.html, where <project> is the
  name of the project or repo you're working in (create the subfolder;
  use Briefings/General/ when there's no project).
- Fully self-contained: inline all CSS and JS, embed images as data: URIs,
  NO external URLs — Lettuce renders it with no network access.
- Give it a descriptive <title>; Lettuce shows that as the note's name.
- If I say the artifact should be PUBLIC, also add
  <meta name="lettuce-published" content="true"> to the <head> — Lettuce
  publishes it to my site on the next deploy. Otherwise never add that tag.

For MCP clients the same instruction works — Claude will reach for write_note (and list_folders / list_notes to pick a sensible location) instead of the filesystem. Prefer reviewing each save first? Hand Claude a --propose key and the files arrive as proposals in Suggestions mode instead.

Why the artifact rules matter: Lettuce renders HTML documents offline and read-only, so anything not inlined shows up broken; the per-project Briefings/ subfolders keep one busy vault navigable; and with the publish meta tag plus auto-deploy switched on, saying “make it public” is the entire publishing workflow — the artifact is on your site minutes later.

Drop the file in the vault and it appears in the sidebar like any note, renders fully styled in the reader, and syncs to the iPhone app. Moving or renaming it keeps the .html extension. It never runs through the Markdown parser, so it can’t affect tags or search.

Publishing artifacts: an artifact carrying <meta name="lettuce-published" content="true"> in its head rides along when you publish your site — copied byte-for-byte to the same flat URL scheme as notes and listed on the index by its <title>. Right-click any HTML document on the Mac → Publish to Site / Unpublish to toggle the tag without editing the file yourself. Mind that publishing an artifact publishes its inline scripts exactly as authored — that’s the point, and it’s your call.

Try it

With the instructions in place:

“Summarize this thread and save it as a note.” “Build a dashboard of this quarter’s numbers and keep it as an artifact.”

The first lands as Inbox/Thread Summary.md (or a proposal, on a --propose key); the second as Briefings/Acme/2026-07-15-q3-dashboard.html (per-project subfolder), readable on your phone a sync later. Add “make it public” and it also carries the publish tag.