Workspace Home

The Home surface is a lightweight workspace launchpad for a design system.

Purpose

Home should answer three questions quickly:

1. Where am I?
2. What should I do next?
3. Is anything broken or disconnected?

Home is not a full dashboard, integrations setup flow, or documentation hub.

Experience model

Primary zones

1. Continue working

• recent artifacts (last edited)
• in-progress items and drafts (when available)
• link to full activity / browse view

2. Create

• create token
• create preset
• create pattern

3. System status (signals only)

• health score + link to issues and audits
• MCP connection status + link to Connect
• code/repo connection status + link to Connect

4. Context links

• principles
• about
• team / contributors

5. Other design systems (optional)

• either bottom section in Home, or centralized switcher

What Home should not do

• host full analytics workflows (Health owns this)
• host integration configuration flows (Integrate owns this)
• become a docs content index (Use / Docs owns this)

Routing expectations

Home should link out to deeper workflows:

• continue item → artifact-specific editor / browse route
• create CTA → creation route
• health signal → Health Dashboard / Audits
• connection signals → Connect / Integrate routes

Data requirements

Home needs fast summary data:

• design system identity (name, optional description)
• counts (presets, tokens, patterns)
• recent artifacts with type + timestamp (+ draft/published where supported)
• health score and top issue count
• MCP connection status
• code connection status