zeroheight

@zeroheight.com

zeroheight enables teams to document, deliver, track, and manage their design system all in one place. 🚀 We also host Converge, Design System Awards and Design Systems Report 🤓

Getting an agent to generate code is easy. Getting it production-ready takes a proper briefing. Ep 3 of License to Build: briefing agents to build production-ready components, from Figma to Claude Code with the zeroheight MCP. 📅 Tue 11th Aug, 4pm GMT 👉 https://hubs.ly/Q04r8Mrg0

Promotional graphic for License to Build Episode 003: Briefing Agents to Build Components in Code, Tuesday 11th August 2026, 4:00pm BST / 11:00am ET / 8:00am PT. Illustrated characters in detective-style hats and sunglasses hold magnifying glasses, tools, and a drone. Speaker: Luke Murphy, Principal Design Advocate at zeroheight, shown in a headshot.

Your design system is only as strong as what's actually in production. Connect the zeroheight MCP to your coding agent and it checks your actual code against your design system docs - flagging what's off-system, misusing tokens, and what needs fixing. Learn more here 👉 https://hubs.li/Q04ntNHy0

Screenshot of a code editor showing a Markdown audit report titled 'Savings Dashboard Audit Report,' comparing a Savings page implementation against Baseline Design System guidance, with sections on design token usage, issues found, and a table of non-token dimension values.

Most accessibility docs focus on component level: states, contrast, keyboard behaviour. A gap remains: what happens when a team hits a pattern the system didn't anticipate? Read how to close that gap before it becomes accessibility debt 👇 https://hubs.li/Q04qQC5Y0

Blog titled: "How accessibility gets lost between base and product design systems," with the zeroheight logo. An illustration shows a hand holding an accessibility icon, alongside an eye, a computer mouse, an upward trend arrow, and a cursor.

Presenting Hops & Props London, our newest event to bring the design systems community together.  Expect talks from industry leaders, chats with other design systems folk and drinks in the summer sun.  📆 20th August at 93 Feet East, London ⏰18:00-22:00  Save your spot: https://hubs.li/Q04r9p-F0

How much of your codebase is actually following your design system? The zeroheight MCP gives your coding agent access to your design system docs - so when you ask it to audit, it knows what it's checking against and makes fixes directly within the editor. Find out more 👉 https://hubs.li/Q04ntNpx0

Screenshot of a code editor split view. The left pane shows a diff of React/JSX code for a savings dashboard component, with added lines highlighted in green including Button components and formatted currency values. The right pane shows an AI assistant's response summarising changes made to align the dashboard with the design system package and Baseline MCP guidance, listing updates to buttons, icons, and design tokens replacing custom colour and typography values.

Design system docs break down when every update needs a manual handoff.  In this month's Deep Dive, we're getting practical about markdown syncing - how it works end-to-end, and which parts of your docs are best suited to automation. 📅 Tues 28th July Register your spot 👉https://hubs.li/Q04q4W720

Pink promotional graphic for zeroheight's Product Deep Dive webinar, 'Automating Documentation: Markdown Syncing,' on Tuesday 28th July 2026. Features a black-and-white photo of Luke Murphy, Principal Design Advocate.

Design systems are supposed to make consistency easier. For most things, they deliver. Mobile accessibility is usually not one of them. This blog digs into the accessibility barriers and what mobile-first accessibility looks like in a design system. Check it out 👉 https://hubs.li/Q04pR--50

zeroheight blog header on a lavender background reading "The mobile accessibility gap most design systems ignore."

What if all it took to audit your design system was a prompt, not a whole project? zeroheight's MCP connects your docs to your MCP-enabled tool of choice so AI can read, interrogate, and deliver findings specific enough to act on. Auditing made easy. → https://hubs.li/Q04ntKLY0

Screenshot of a chat interface showing AI assistant auditing a design system styleguide. After a user asks for an audit of inconsistencies and gaps, the assistant reports using the styleguide integration, then displays summary stats — 5 critical gaps, 8 inconsistencies, 4 structural issues, 3 strengths noted.

Most design systems aren't uniformly mature. They're stronger in some areas than others - that's normal. Our new Design System Maturity Model scores yours across six independent axes, from stage 1 to 4, so you know where you stand and what to focus on next. Take the test: https://hubs.li/Q04pCgcX0

Dark promotional graphic for zeroheight's Design System Maturity Model, reading 'How mature is your design system? Six axes. Four stages. One honest picture of your design system.' A collage of colourful line-art icons (question mark, heart, arrow, document, stacked blocks, sparkles) fills the right side, with a 'Take the test' button below.

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

License to Build Episode _002 promo on a lavender background, for Tuesday 21st July 2026, 4.00pm BST / 11.00am ET / 8.00 PT. Heading: 'Briefing agents to scaffold components in Figma.' Four illustrated spy-like characters in hats and sunglasses hold tools including goggles, a magnifying glass, a drone, and a component-labelled card. A black-and-white photo shows speaker Luke Murphy, Principal Design Advocate at zeroheight, smiling.

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

Screenshot of a code editor showing a diff for a savings dashboard component. On the left, highlighted code changes show updated Button components and layout elements. On the right, an AI assistant panel summarises the changes, including updated design system components, icons and design tokens.

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

What's new" graphic on a dotted cream background. Bold black headline reads "What's new." To the right, illustrated elements float around a laptop: a colour swatch, a card with an icon, a screenshot thumbnail featuring an illustrated character face with a purple triangle overlay, a teal MCP icon, sparkles, a cursor, and a friendly illustrated character giving a thumbs up behind the laptop screen. The zeroheight logo appears bottom left.

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

Webinar banner for 'License to Build: Briefing agents to build on-system code, then audit it,' Tuesday 7th July 2026, 4.00pm BST / 11.00am ET / 8.00am PT. Illustration of a spy-like character in a fedora and sunglasses holding a folder, alongside a code icon and a checklist with tick and cross marks, on a mint green grid background.

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

Webinar banner for 'License to Build: Briefing agents to build on-system code, then audit it,' Tuesday 7th July 2026, 4.00pm BST / 11.00am ET / 8.00am PT. Illustration of a spy-like character in a fedora and sunglasses holding a folder, alongside a code icon and a checklist with tick and cross marks, on a mint green grid background.

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

An illustrated hand holds a collection of design system elements — a teal tile with a group icon, an orange tile with an arrow, a heart shape, and a textured card — alongside a clock, a cursor, and decorative squiggle details. The image accompanies a zeroheight blog post titled "How to start a design token system with confidence."