A walkthrough of replacing a chaotic morning routine (Slack, email, HubSpot, GitHub notifications, forgotten promises) with a single auto-refreshing 'daybook' page built in Claude Code. The page pulls from Calendar, Slack, ClickUp, HubSpot, and a Product Hub connector into 12 blocks — meetings, design docs, to-dos, customer requests, a Slack 'needs attention' digest, and a promises tracker — refreshed automatically every morning via a scheduled routine. Readers get the actual build steps, the prompt/skill pattern used to generate it, and the honest caveats about data dropping or being misclassified.
<parameter name="workflow_steps">[{"title": "Name the actual pain point before building anything", "description": "Started from waking up to thousands of Slack/email/HubSpot/GitHub notifications plus forgotten verbal promises to teammates, with no way to prioritize. This framed what the tool needed to solve, not just 'make a dashboard'."}, {"title": "Start from a simpler prototype and let it evolve", "description": "Originally had two separate Claude artifacts — a 'morning brief' and an 'open loops' to-do list — before consolidating into one unified daybook page."}, {"title": "Design the page as discrete blocks tied to real decisions", "description": "Laid out 12 blocks: meeting/focus timeline, in-progress design docs, terminal session resume (via copied session ID), product questions for a colleague, flagged to-do list, customer requests with type/link, a 'needs attention' Slack digest, a promises tracker, and a ClickUp task pipeline filtered to 'mine'."}, {"title": "Wire up connectors instead of manual log-ins", "description": "Added Calendar, Slack, ClickUp, HubSpot, and Product Hub connectors inside Claude so data pulls automatically rather than requiring repeated manual lookups; added a Product Hub API key under the product hub menu so the key persists."}, {"title": "Build in Claude Code and schedule a 'routine' instead of a 'schedule'", "description": "Switched from Claude's scheduled tasks feature to a custom routine inside Claude Code (since most work already happens there with MCP/integrations), set to trigger every morning at 9am and backed by its own database (local or cloud)."}, {"title": "Replace a hand-written prompt with a prebuilt skill for repeat tasks", "description": "For generating design doc summaries, swapped an earlier ad hoc prompt for a packaged 'skill' (built after a colleague, Andrey, suggested it), making that piece reusable without re-explaining it each time."}, {"title": "Render it as a persistent Chrome-based app, not a disappearing artifact", "description": "Chose a Chrome-based plugin/page over a Claude artifact specifically because artifacts vanished when the laptop closed; the browser-based version stays open and persistent across sessions."}, {"title": "Add one-click 'Analyze with Claude' actions on top of the static data", "description": "On customer requests and the 'needs attention' digest, added buttons to summarize a thread, draft an answer, mark an item done, or convert it into a to-do/loop item directly from the daybook."}, {"title": "Package the build into a shareable prompt for teammates", "description": "Wrote a reusable prompt (shared as 'daybook') that asks a new user their role, timezone, and which connectors they want, then auto-builds a personalized version of the page scoped to their role (e.g. someone else might not get design docs or customer requests)."}, {"title": "Leave genuinely manual blocks manual", "description": "To-do list entries and promises/loops captured from live discussions (e.g. a daily standup) are still typed in by hand and flagged urgent/high/normal/low — not automated — because they originate from spoken conversation, not a connected data source."}]
