The loop — old-world slides, new-world workflow

1. Draft. Make the thing in any Claude chat or session, then say "save this to the design repo." That's v1 on the shelf.
2. Iterate. Tell Claude: "pull the fund terms page from the studio and tighten the headline." It posts the change back as a new version with a label. The version rail replaces final_v3_FINAL2.pptx.
3. Review. The team reacts in the item's discussion thread, right next to the work.
4. Decide. One click on Mark direction approved pins the version that won. Machines can post work; only people can approve.
5. Present. Open the file on the approved item — what you show is exactly what was approved.

Ground rules

• One item per piece of work. Revisions are versions, never a second item.
• Never edit a downloaded copy — change it through Claude so the new version lands back here and history stays whole.
• Text beats binary: slide copy, specs, and rationale save as markdown or HTML, so every change is diffable.
• Every save carries a one-line description that will still make sense in three months.
• Every save is a git commit in rivent-dev/slw-design — nothing on this shelf can be lost or silently overwritten.

Ways to save

• Claude Code / Desktop session — say "save this to the design repo" (the /save command works in every repo).
• Plain claude.ai chat — with the Studio connector added, say the same thing and it files directly; or copy the output and use + Add to shelf here.
• This site — + Add to shelf takes pasted text or a dropped file (PPTX, PDF, PNG, HTML up to 13 MB).

What lives where

• Studio (here) — creative work: presentations, mockups, positioning, project thinking, brand assets.
• System Design (design.rivent.dev) — architecture and cross-app build plans.
• Proof Desk (on the portal) — a mockup that is mid-review for a product build; it moves here once it's part of the record.
• Slide Library — stays the presentation tool; over time it reads from this shelf, it never replaces it.