The Design Team Stack
A Switchy Project for the 2–6 person product design team that moves between the file, the ticket, and the doc all day.
Spinning this stack up creates a Switchy Project - your team chats together, @-mentions every model and MCP listed below with shared context, and that whole memory becomes its own MCP server inside Claude Code, Cursor, Claude Desktop, and ChatGPT for every teammate.
Heads up: this stack uses 4 MCPs. Pro is needed for unlimited MCP connections - Starter ships with 1.
The Switchy Project a small design team keeps open beside Figma. Sonnet 4.7
as the default for UX copy, naming, critique notes, and turning a fuzzy
brief into clear acceptance criteria; GPT-5 for a second voice on
microcopy and for structured output you'll drop into a spec; Gemini 2.5
Pro when you need to hand the model a long PDF — a brand guideline, a 40-
page research report, a competitor's flow captured as a doc — and get the
relevant parts back.
Figma puts the work itself in the conversation: "@figma what changed in
the checkout frames", "@figma summarise the components on this page" — so
critique happens against the actual file, not a stale screenshot in a
thread. Linear keeps design work tied to delivery: "@linear what's blocked
on design this cycle". Notion holds the system and the rationale: "@notion
pull our button states doc", "@notion draft a pattern writeup from this
discussion". Slack is where handoff lands: "@slack post the ready-for-dev
summary to #build."
What a design team gets that a folder of files can't give you: the
*reasoning* stays attached to the pixels. Why this pattern, what we tried
and rejected, the accessibility note that has to survive into dev — the
Project remembers it, and exposes that memory as an MCP server so it shows
up inside every designer's and PM's Claude Code, Cursor, Claude Desktop,
and ChatGPT. When a new designer or a contractor joins, they inherit the
*why*, not just the Figma link.
Start free on Starter, invite the rest of the team when the work outgrows
one person.