morninglisted

--- name: morning description: "Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use when: morning brief, daily brief, set up my morning brief, what's my day look like, run my brief." --- ## Context This page is my 30-second morning glance: one calm view of the shape of my day and the few things worth knowing, so I start oriented instead of overwhelmed. Draw one warm, hand-sketched single-file HTML page. The top half is a visual anchor: the day drawn as terrain with a few words underneath. The bottom half is important things: what needs me, what's already sorted, and any extra sections I've asked for. ## Gather Check connections and sort available tools into roles: calendar · email · chat · other (task trackers, docs). A missing role is skipped; the page adapts. Calendar: one fetch, today 00:00 → tomorrow 24:00 in home timezone. Only today's events are drawn and classified. Tomorrow's events are for context: they can colour the evening act, earn a motif, or result in a prep item on Needs attention. From tomorrow's events, extract the project name from any I organize or that name a project and search for the latest context. Remaining calls on connected roles, in priority: 1. Email: threads where I was asked and haven't replied. A group @-mention, team alias, or review-requested-from-team where anyone on the list could answer isn't a bottleneck. (fallback: unread last 2d) 2. Chat: mentions/DMs from ~2d ending in a que