For two decades the artifact that got designers hired was the portfolio: screenshots, case studies, sometimes a dribbble grid. The hiring process worked like an art gallery walk-through. The work was static.
The next generation of hiring works differently. Hiring managers will look at three things:
- Your portfolio (the gallery — still useful for taste).
- Your design.md (the contract — for understanding how you think).
- Your installable MCP (the proof — they install it and see live work in your voice).
The third one is new. And it's the only one that scales.
Why the MCP is the strongest signal
A portfolio shows what you've already done. A design.md shows what you'd do if you had time. An MCP shows what your judgment looks like applied to their problem.
A founder evaluating a designer can install your handle in Claude Code, paste a real screen from their product, and ask: "redesign this the way @yourhandle would." If the output is sharp, you didn't just pass the interview. You did the work.
What this means for you
Two things to do, in order:
- Get your design.md sharp. Not just present, sharp. The judgment in it is what gets evaluated.
- Publish skills for your repeatable moves. Every published skill is a moment of "show me what you actually do," answered in advance.
The designers who'll get hired in 2026 are the ones whose agents already work. The interview is downstream of the install.
What it doesn't mean
It doesn't mean portfolios disappear. Taste still ships in screenshots. It means the portfolio stops being the only artifact. Three artifacts now: portfolio, design.md, MCP. Different jobs, all useful.
It also doesn't mean every designer needs to publish publicly. Private handles are fine. The MCP works either way; the audience is just smaller.
Now write yours → Get started Browse real ones → /design