Have you registered for tomorrow's webinar?👇

Are Figma components just another kind of design system documentation? Check out Ron’s take here 👇 https://hubs.li/Q04p0B6B0

Getting an agent to place a Figma component is easy. Building it on-system takes the right docs. Join Dispatch #2 of Licence to Build to learn how to brief agents with your design system context. 📅 Tue 21 July, 4pm GMT Sign up here 👉 https://hubs.li/Q04ptQ4G0

Design system contribution is like a mountain range.  Many ways up, many ways down - and it gets very steep at the top.  Read about Mount Contribution - a framework for more effective design system contributions👇 https://hubs.li/Q04n4Bq80

Your coding agent doesn’t know your design system, so it guesses. Connect zeroheight MCP to tools like Cursor or Claude Code and it stops inventing - pulling your actual components, tokens, and usage rules on every generation. Learn more ➡️ https://hubs.li/Q04npRLd0

Gated access and permissions slow down design system adoption. 🔐 With zeroheight, your design system lives in one place. Now, anyone authorised through your identity provider can access it via MCP, without needing a zeroheight account. Learn more: https://hubs.li/Q04npm5Z0

An AI agent can whip up a POC in minutes. Staying on-system is the hard part. That's where License to Build comes in: our new webinar series exploring real-world use cases for briefing AI agents with your design system context. Join us for episode #1 July 7th, 4pm GMT. 👉 https://hubs.li/Q04nftv_0

The handover between design and development isn't always straightforward - and drift between design output and the end user experience is a real cost. Amy Rogers explores how AI agents could be the answer 👇 https://hubs.li/Q04mCSPN0

Every good agent needs a briefing. Licence to Build is our new webinar series on giving AI agents your design system as context. Dispatch #1: How to brief Claude Code via the zeroheight MCP to scaffold a POC, audit it and ship. 📅 Tue 7 July, 4pm GMT Sign up ➡️ https://hubs.li/Q04nftKC0

Converge 2026 is coming round fast. We’ve got our next speaker lined up and ready to talk all things design systems. But can you guess who it is? 👀 Get your Converge tickets here: hubs.ly/Q04mZ2X40

Do you know how mature your design system is? Introducing zeroheight's Design System Maturity model - 29 questions, 6 axes, scored between stages 1-4.  Get honest, personalised results in minutes. Take the test 👇 https://hubs.li/Q04mFKZy0

Design tokens: the key to scaling your brand across a product team. But how do you go about creating your first design token system?  In this article, Louis walks through best practices for creating, documenting, versioning and syncing your first design token system. 👉 https://hubs.li/Q04mgSM50

Want to know what the #config announcements mean for design systems? We've done a rundown for you: zeroheight.com/blog/what-do...

Hot off the press from #Config 2026🔥 @zeroheight.com now has a native connector inside the @figma.com Design Agent. Ask it to check components against your guidelines, generate on-brand screens, or get instant answers from your own design system docs, all without leaving the canvas.

Seated and ready to hear what @figma have to announce at Config this year. What are your predictions?

Every design system gets to a stage where things feel like they're breaking. The instinct is to start over - but that usually makes things worse. Renovation > demolition. Read Amy Hupe’s article for more 👉 https://hubs.ly/Q04lR34S0

We're super excited to be in Bristol for @pixelpioneers.co today!  Our Head of Advocacy @lurkmoophy.bsky.social will be taking to the stage to talk all things design systems. We'd love to see some familiar faces, so if you're attending, come say hey! 👋

AI is guessing without your design system - inventing components, ignoring tokens, generating rework. Your documentation is the missing link. The zeroheight MCP puts your components, tokens, and decisions into Claude, Cursor, Figma Make, and more. Learn more here 👉 hubs.li/Q04lRfbw0

When design system documentation lives outside the workflow, teams stop using it. Sage used the zeroheight API to build and connect a single source of truth that spanned where their team already worked. The result? Read the full story here 👉 https://hubs.li/Q04kfFVT0

Is "driving adoption" just a polite way of saying "begging colleagues to do their jobs properly?" 👀 In episode #57 of Design Systems WTF, Michelle & Luke tackle the issue of adoption, and whether we’re approaching it in the right way. 📅 Weds 17 June / 4pm BST Register here ➡️ hubs.li/Q04lnMpd0

Getting tokens out of your design tool is easy.  Getting them into production-ready CSS, Android & iOS - less so. Even the people building these pipelines will tell you it's not always pretty. Watch our webinar on demand to learn more 👇 https://hubs.li/Q04kSCWj0

Almost every product org has a documentation problem. Most know it. Barely any have fixed it. For years, that was tolerable. Humans fill gaps with intuition and conversation. LLMs don't - they resolve ambiguity and scale it everywhere. Grace explores this further: https://hubs.li/Q04kgTmM0

Join us as we get ready for Config 2026!  If you’re down to chat all things design systems and have some drinks on us, we’d love to see you there!  📍 Barebottle, Salesforce Park  📅 Monday 22nd June Register your spot → https://luma.com/24nh9egm

50+ products, 11,000 employees and a 150-person design org. Good documentation wasn’t Sage's problem. Keeping it inside of the workflow was. Check out the story of how Sage used the zeroheight API to put documentation where their teams were already working.  🔗 https://hubs.li/Q04jy7KN0

The teams winning with AI got their foundations right first. We heard this loud and clear from 123 design practitioners surveyed in our State of AI in Design Systems report. Download the report here 👉 https://hubs.li/Q04j0Xhc0

Everyone's using AI to write design system docs. But is that a good thing? 🤔 Join Luke & Michelle on 3rd June to dig into where AI belongs in documentation - and where it doesn't. 4pm GMT | 8am PT | 11am ET Register below👇

Are you designing with low-vision users in mind? Jennifer shares 9 practical ways to get it right - from WCAG compliance to avoiding usability barriers. Inclusive choices help everyone. Read the blog here 👉 https://hubs.li/Q04j1B7w0

Design teams have complicated feelings about AI. Turns out, that's actually the most interesting finding. Swipe through to see the highlights from our survey, and download the full report below 👇 hubs.li/Q04j0ML80

Thinking about Converge 2026? 👀 Incredible speakers, great conversations, and a room full of design systems folk that get it.  Check out last year’s highlights below 👇 Early bird tickets are almost sold out - grab yours now: https://hubs.li/Q04hTXFS0

✨ Introducing the zeroheight Assistant for Figma ✨ Select a component, ask a question, get answers from your design system docs - all without leaving the Figma canvas. Less interruptions, better outputs. Find out more: hubs.li/Q04hWxgl0

The countdown is on! Just 1 day until the next Product Deep Dive webinar - Luke Murphy talks all things Style Dictionary: where it fits, when to use it, and how to get code-ready token outputs every time. 📅 Tomorrow, 26th May, 4pm BST Don't miss out 👉 https://hubs.li/Q04h6_gy0

Lots of design systems have the same problem - nobody knows the full picture. 👀 In part 3 of the blog series, TJ breaks down: - Why the "source of truth" debate is the wrong conversation - What a diagnostic layer is and why systems have always needed one Check it out: hubs.li/Q04hCsSH0

Join Luke Murphy in the next Product Deep Dive webinar for a practical walkthrough of Style Dictionary: what it does, when to use it, and how to turn raw token exports into consistent, code-ready outputs. 📅Tuesday 26th May, 4pm BST Secure your spot: hubs.li/Q04h6_gn0

If your team keeps asking “Where should this live?” or “Which page is right?” your styleguide nav may have drifted. The zeroheight Assistant can propose a cleaner navigation + category structure, including merges, moves, and renames, then waits for approval before making changes. hubs.li/Q04hh5hy0

Design tokens can get messy. Multiple Figma files, modes, brands - it adds up fast. We've rebuilt how zeroheight handles tokens from the ground up 🚀 (1/5)

1 day to go! ⏰ Tomorrow @ 4PM Luke Murphy presents live findings from a survey of 123 design system practitioners on where AI is working, and where it isn't. You don't want to miss this one! Secure your spot ➡️ hubs.li/Q04gCPjF0

A year ago, "AI in design systems" was a thought experiment. Now it's an operating reality. Want to learn more? Join us on Tuesday 19 May, 4-5PM as Luke Murphy unpacks our findings. Sign up here: 🔗 hubs.li/Q04gCPh50

A broken design system is no longer just a productivity problem. In his article, TJ Pitre breaks down👇 - Why everyone can feel it but nobody fixes it - What AI tools do with a messy design system - The real cost of ignoring issues Check it out: hubs.li/Q04gMl-60

The State of AI in Design Systems Report is here! 🚀 67% of practitioners think AI is overhyped. 82% are using it anyway. Want to see what else we uncovered? Check out the full report → hubs.li/Q04grDL50

TJ Pitre has produced a 3-part series for the zeroheight blog on the future of design systems. Part 1 is live now - 'The product your design system is actually building'. Read the full article here: hubs.li/Q04g6xV00

CONVERGE IS HAPPENING AGAIN! Can't remember if I've already posted about it, but get your tickets to the Best* Design Systems Conference. converge.zeroheight.com *As confirmed by me, and I am completely unbiased.

AI doesn’t understand your design system (at least not by default), but strong documentation changes that! 👀 With zeroheight, AI helps you create and maintain your docs, then brings that knowledge directly into the tools your team already uses. The result? Find out here: hubs.li/Q04g390k0

Does your design system have a rulebook? Not just what was decided but why, and what was rejected. With AI working inside design systems, undocumented reasoning is a gap the model will fill on its own. Great piece by Kevin Muldoon on the three kinds of truth every system needs: hubs.li/Q04f6BFv0

Murphy Trueman just nailed something we've been thinking about for a while. Most design system contribution models have great documentation. Almost none have momentum. The difference isn't process. It's ritual. 💡 A great read for anyone working on design systems: hubs.ly/Q04dSNBz0

Design system docs drift — and when they do, teams guess (and AI does too). That’s when inconsistency creeps in. Run a quick audit with zeroheight Assistant to spot gaps, prioritize fixes, and get your docs back on track in minutes. Get started today 👉 hubs.li/Q04dJj6x0

We're hiring a Design Systems Advocate (Partnerships) at zeroheight 🚀 If you've built a design system, written about one, and argued passionately about one, this role was made for you.👇 Remote-first | UK | Full-time Apply here: apply.workable.com/zeroheight/j...

Here's my latest article for @zeroheight.com, inspired by @kvlly.com, diving deep into the hidden costs of a design system team saying "yes".

61% of design system teams don’t have enough people — the #1 challenge in this year’s report. Join us today to unpack what’s really going on with resourcing, the hidden cost of understaffing, and what to do about it. If your system is stretched thin, this one’s for you: hubs.li/Q04cHBXG0

New on the zeroheight blog from Tammie Lister 👇 96.6% of open design systems ignore native HTML. Most teams still start from scratch. Everyone's vibe coding the same kits. She makes a strong case for why that needs to change — and how open systems + AI are the path forward. hubs.li/Q04c7VD80

⚡ That was quick. Super Early Bird tickets for Converge are officially sold out! But good news: Early Bird tickets are now live 🎟️ If you’ve been thinking about joining us, now’s the time to make it happen (and still save). Availability is limited! Book here: hubs.li/Q04bCcCt0