The design system for the Synapse app — tokens, type, and components scoped to
mobile-app sizing (the marketing site is a separate, later build with its own scale). Tokens
live in src/styles/ds/ (the
drop-in target for Claude Design re-exports); this page renders the live system. Screens below
are shown in true ~393px iPhone frames.
Foundations
Brand
Full wordmark · 100% primary
Wordmark · 100% primary
Logomark · tree at 70%
Square lockup
Color
Teal · primaryA spotlight, not a floodlight — aim ~10% of a screen.
Recipes, not components — generalized compositions of the primitives above for recurring
use cases. If one keeps getting copied into screens, that's the signal to promote it to a
real ui/ component.
MC
Maya Chen
Medical lead · Toronto
No touch in three weeks — send the kickoff notes before Friday's review.
Action card
Use whenSurfacing the single most important next step. The hard variant earns the emphasis — max one per screen, near the top.
RecipeCard hard · entity header (Avatar + name/sub) · one supporting sentence · primary + outline button row.
Don'tStack several hard cards, or use it for passive information with no action.
Jun 24 · 9:00Confirmed
Quarterly summit
Toronto · Studio 4
MC TR LB 36 going
Media card
Use whenThe content has a visual identity — events, programs, articles. Works full-width in a feed or at ~210px in a horizontal rail.
RecipeCard soft + padding none · tinted icon panel (or photo) bleeding to the edges · meta row + display title · footer with social proof + one small button.
Don'tPad the panel away from the card edge — the full bleed is the point. Promote one featured item to hard, not all.
Last touch
3 days ago
Status
Warm
Owner
Dana H.
Summary card
Use whenA detail screen needs its key facts scannable in one glance — status strips, record headers.
RecipeCard hard (or flat for quieter contexts) · 2–4 columns of muted label over bold value, space-between.
Don'tPut buttons inside, or exceed four columns — split into two cards instead.
2
Day 2 of your streak
Tu
We
Th
Fr
Sa
Su
Mo
Weekly goal
Almost there
Progress card
Use whenOne number is trending toward a goal — streaks, scores, weekly targets.
RecipeCard soft · one big focal element on the left (icon or progress ring) · display-font headline · progress detail or one small secondary button.
Don'tUse hard — progress is encouragement, not a demand. Never two focal elements.
Your best week yet
84 touchpoints · up 31% on last week
MTWTFSS
Insight card
Use whenData has one takeaway worth telling. The headline IS the insight — the chart just backs it up.
RecipeCard soft · display-font verdict + muted detail line · small chart in teal-300 with primary highlighting the point that matters · one full-width CTA.
Don'tShow a chart without a verdict headline, or highlight more than one data point.
128advisors+12 this week
4priority
7events hosted
36touchpoints+8 this week
Stat tiles
Use whenA handful of small counts belong together — dashboard vitals, profile stats. Always in a grid, never alone.
RecipeStatTile component in a 2-up grid · one accent-colored icon each (vary the accent across tiles) · optional delta line.
Don'tUse for the hero metric — that's a Progress or Insight card. Skip deltas that say nothing.
AO
Dr. Amara Okafor
Oncology KOL · Toronto
Tier 1Warm
Person card
Use whenA person IS the content — suggestions, introductions, featured profiles. For lists of people, use ListRow instead.
RecipeCard soft · centered Avatar xl + display name + muted role · up to two Badges · action row of IconButtons + one primary button.
Don'tStack many vertically — this is for one or two people, or a horizontal rail.
Selectable card
Use whenA choice between 2–4 rich options that need a title and a description — onboarding, plans, settings. For short labels, use SegmentedToggle.
RecipeStack of interactive Cards: flat when idle, hard when selected · display-font title + muted sub · primary check dot on the right.
Don'tMix with checkboxes in the same group, or exceed four options — use a list instead.