The Rundown

In this guide, you will learn how to build a daily command center in Claude Cowork with Live Artifacts. Instead of opening Slack, email, calendar, tasks, docs, and dashboards one by one, you will get one live view for today's priorities, this week's blockers, and this month's KPIs.

Who This Is Useful For

• Operators and founders who start every morning by checking too many apps before they know what actually matters
• Managers and team leads who need one place for blockers, meetings, follow-ups, and team updates
• Creators and consultants who want a lightweight command center for content, clients, pipeline, tasks, and KPIs

What You Will Build

A Claude Live Artifact that works like a daily command center. Version one gives you Today, This Week, and This Month views, plus KPI cards, quick stats, charts, and feed panels from your connected apps.

After that, you will layer on upgrades: priority labels, dashboard skills, refresh buttons, and controls like manual override, archive, and click-to-open updates.

What You Need

• Claude Desktop app
• Any paid Claude plan
• Connected apps or safe sample data to test with
• A few KPIs or recurring work streams you want to track

Step 1 Let Claude Interview You First

Open Claude Cowork and make it interview you before it builds anything. Slowing down at the start is key.

Most people skip this and jump straight to "build me a dashboard." That is how you get a pretty layout that does not match your actual day.

Paste this prompt:

Interview me about my connected apps, daily workflow, KPIs, and what counts as urgent. Then propose the modules for a daily command center before creating the artifact.

If you want Claude to go deeper, use this expanded version:

Before you build anything, interview me about my workday.

Ask me about:
- my connected apps and files
- what I check every morning
- what decisions I make daily
- the KPIs I care about
- what counts as urgent
- what updates are FYI only
- what should show up in Today, This Week, and This Month

After the interview, propose the dashboard modules before creating the artifact.

Answer with real workflow details. For example, you might say you check Slack mentions, unread Gmail, today's calendar, active Notion projects, CRM pipeline, and weekly content numbers.

If Claude asks to use a connector that is not enabled for the current chat, turn it on only if you are comfortable with the access.

Claude shows this when a connector exists, but has not been enabled for the current chat.

Pro tip: Ask Claude to summarize its understanding before it builds. A quick "Here is what I heard" step catches bad assumptions early.

Step 2 Create Version One of the Dashboard

Now tell Claude to create a v1 of the dashboard. Keep this version simple. It should prove the structure works before you add skills, buttons, animations, or advanced settings.

Paste this prompt:

Create a modular Live Artifact command center with Today, This Week, and This Month views. Include KPI cards, quick stats, charts, and app feed panels.

If you want a more detailed build prompt, use this:

Create a modular Live Artifact command center with three views:

1. Today
2. This Week
3. This Month

Include:
- KPI cards
- quick stats
- charts for trends or changes
- feed panels grouped by app or workflow
- blockers and waiting-on items
- top 3 recommended actions

Keep it scan-friendly. I should understand the day in 60 seconds.
Use the interview answers to decide what belongs in each view.

Claude may ask how you want the output delivered. Choose Live artifact so the dashboard becomes something you can reopen instead of a one-time chat summary.

Choose Live artifact when Claude asks how to deliver the dashboard.

After Claude creates the artifact, review version one like a dashboard, not like an essay. Check:

• Are the top numbers actually useful?
• Are the feeds grouped by app or workflow?
• Can you understand the day in under a minute?
• Is anything private showing up that should not be there?

Claude can build the artifact alongside the chat, so you can inspect the dashboard while it works.

Pro tip: Every step after this is an upgrade to add on top of version one. Make sure this version works and is actually useful before proceeding.

Step 3 Add Priority Tracking on Top

Once version one is useful, add priority tracking. The dashboard should rank updates, not dump another feed on you.

Paste this prompt:

Add priority labels to every update: urgent, needs review, FYI, or blocked/waiting. Rank items by deadline, business impact, customer impact, and whether I am the blocker.

For more control, add source and confidence rules:

Add priority labels to every update:
- urgent
- needs review
- FYI
- blocked/waiting

Rank items by:
- deadline
- business impact
- customer impact
- whether I am the blocker
- whether a decision is needed today

If you are not sure, mark the item "review manually."
Do not invent status. Cite the source app or source item for each recommendation.

This is what turns the artifact from "nice dashboard" into something you can act on. Slack mentions, unread emails, upcoming meetings, overdue tasks, and project updates should not all compete equally.

Pro tip: Keep the labels visible. A fast dashboard should tell you what needs action before you read the details.

Step 4 Add Dashboard Skills

Now add dashboard skills. This lets you take action without leaving the dashboard.

Paste this prompt:

Add skills to this dashboard: Plan my day, Show blockers, Draft replies, Prep meetings, and Review KPIs. Each skill should be triggered via a button on the dashboard and should return a short next-step list.

You can also ask Claude to add more specific skills:

Add these dashboard skills:

1. Summarize email
Read the latest relevant email updates, summarize the important ones, flag anything urgent, and place the results in the Today view.

2. Summarize Slack mentions
Read new Slack mentions and DMs, group them by project or urgency, and add anything actionable to the Today view.

3. Prep meetings
Look at today's calendar, find related docs or recent messages, and create a short prep brief for each important meeting.

4. Review KPIs
Compare today's numbers to this week and this month. Flag anything that changed meaningfully.

5. Draft replies
Create short draft replies for urgent messages, but do not send anything without review.

The point is not to add every possible button. The point is to turn the command center into the place where the next action starts.

Pro tip: Once the artifact opens, click the pin button to keep it in your Claude sidebar. You do not want to search through old chats every morning.

Step 5 Add Refresh and Control Buttons

This is the part that makes the artifact feel like a real command center. Once version one works and the skills are useful, ask Claude to add controls that make the dashboard easier to run every day.

Start with a daily refresh button:

Add a Daily refresh button to this command center.

When I click it, update the dashboard with current information from connected apps and files.

The refresh should show:
- what changed since the last version
- what got more urgent
- what is blocked
- what improved
- the top 3 actions I should take next

Preserve the dashboard structure. Update the state.

Then add practical controls:

Add these dashboard controls:

- Settings panel for update frequency
- Manual override for any incorrect status or priority
- Archive button for updates I have handled
- Click-to-open links for every source update
- Dark mode toggle
- Simple animations only where they make status changes easier to notice

If Claude cannot fully wire every button to every connector in your setup, keep the control anyway and have it generate the right prompt. The habit still works: open the pinned artifact, refresh the state, review what changed, and take action.

A finished command center should make the important numbers and connected-source context visible at a glance.

Pro tip: Ask for "since yesterday" and "since last week" summaries. Daily changes tell you what to do now. Weekly changes tell you whether the system is improving or drifting.

Going Further

Add dark mode and light polish. Dark mode, small animations, and cleaner section headers can make the dashboard easier to scan if you use it every day. Keep polish secondary to usefulness.

Add a settings panel. Let yourself change update frequency, visible sources, KPI definitions, and priority rules without rebuilding the artifact.

Add manual override and archive. Claude will not classify everything perfectly. A manual override and archive button keeps the dashboard useful when a status is wrong or an item is done.

Make updates clickable. Ask Claude to include source links so you can click from the dashboard into the original Slack thread, email, doc, task, or calendar event.

Use it as a morning ritual. Open the pinned artifact, refresh the dashboard, read the change report, pick the top 3 actions, and only then open the individual apps.