Crade reads invites, threads, and recordings on your screen and gives you the takeaway: who, why, what is waiting on you. Walk into meetings briefed; catch up on three days of Slack in thirty seconds.
What did I miss?
3 days · 47 unread. Here's what matters: NEEDS YOU (2): • #marketing — Kim wants Q3 input by Wed • @Maya DM — contract to sign DECIDED (just FYI): • #engineering — Postgres 16 upgrade lands Friday • #design — Logo v8 picked (Anna's) SKIP — 14 reactions + small talk






You come back from a long weekend or a deep-work block to 400 unread messages across 8 channels. Crade reads the channels on your screen and tells you what actually happened, what is waiting on you, and what you can ignore.
Maya wants to walk through the revised numbers after we added the customer-portal scope. She mentioned wanting a 6-week timeline; we said 8 in the email.
Brief me for the 2pm Arclight call.
Wrote brief-arclight.md: • Who: Maya Chen (Arclight) • Why: revised estimate review (portal scope +$1,800 / 15h) • What to ask: design tokens approach, content timeline • Risk: kickoff is soft if estimate feels uncomfortable She signed yesterday — momentum's good.






A calendar invite shows up. Five minutes before the call. Crade reads the invite, the linked docs, and the email thread on your screen and hands you a one-pager: who is in the room, why, and what they probably want.
Take notes on this video.
Wrote react-19-notes.md (12 min vid, 5 key points): • 0:42 — use() replaces useEffect for data fetching • 3:18 — server actions are forms-only by default • 5:51 — cache() is per-request, not per-user • 8:04 — Suspense needs explicit fallback • 10:33 — migration story for React 18 → 19






A two-hour lecture, a YouTube tutorial, a recorded all-hands. Crade watches what is on your screen and gives you structured notes: key points, action items, timestamps for the parts worth re-watching.