Feedback creatortrack design screenshot workflow

---

name: CreatorTrack design feedback: chat screenshots + N:/CT: tags + ledger description: Justin sends design-reference screenshots directly in chat tagged N:/CT:, logged to a ledger, compiled into a plan on request type: feedback

---

For CreatorTrack UI polish, Justin sends screenshots (Notion reference vs current CreatorTrack state) directly in chat rather than via Google Doc, since chat images are seen at full resolution with no export/extraction friction.

Convention: each message has 1-3 screenshots plus one line tagged N: (Notion reference, "copy this feel") or CT: (CreatorTrack current, "this is wrong"). iPhone markup (circle/arrow) on the exact element is encouraged.

Claude's side: save each screenshot to a dated folder in the repo (data/creatortrack-design-notes/), numbered, append to a running ledger file (what/why/exact words/priority guess), and reply with a terse "noted, item N: " so Justin can correct misreads instantly without breaking his flow of firing off more screenshots. When Justin says "write plan", the ledger gets compiled into batches grouped by touched files, and agents are spawned per batch with the exact screenshot paths (agents can open image files even though they can't see chat).

Why: keeps a multi-sitting, possibly multi-session backlog of visual UI feedback unambiguous and file-durable instead of relying on ephemeral chat context. How to apply: any future CreatorTrack (or other UI-heavy project) design-feedback session should default to this same screenshot+tag+ledger flow unless Justin says otherwise.

[auto-memory session d94ca553-ab7e-4eed-b169-14375e343389, confidence 0.85, mode direct]