At Perplexity, the design system lives in the codebase, not Figma. Designers contribute directly to the frontend, creating a single source of truth that eliminates drift between design files and production code, forcing a highly practical and collaborative process.

To keep pace with AI development, the barrier between design and engineering must fall. Intercom made it a non-negotiable job requirement for every product designer to ship code to production. This empowers them to fix UI bugs directly and accelerates the entire development cycle.

The rise of AI tools like Claude Design necessitates structured, machine-readable inputs to function effectively. This is driving an industry shift toward standards like Google's 'design.md,' making a well-defined, codified design system a prerequisite for leveraging AI in the product development lifecycle.

Building a true platform requires designing components to be general-purpose, not use-case specific. For instance, creating one Kanban board for sales, support, and engineering. This thoughtful approach imposes a ~20% development 'tax' upfront but creates massive speed and leverage in the future.

AI tooling is creating a 'fluid model' where any employee, regardless of role, can potentially ship code. This dramatically expands the design system team's responsibility, which must now create tooling and guardrails to support a much broader and less technical user base across the entire organization.

While brand consistency is a benefit, the primary business impact of a well-built design system is operational efficiency. It drastically accelerates speed to market for new features and slashes onboarding time for new hires because the system's intelligence is effectively self-documenting.

Figma's CDO explains that new tools enable designers to build systems, not just static screens. Using node-based interfaces, they can create workflows or "mini-apps" that generate various outputs based on inputs, embedding brand and intent into a reusable system rather than a single artifact.

Instead of relying on scattered design docs or linking a repo, generate a "living design system" as a single HTML file. This artifact visually represents colors, typography, and components. It's easily passed to an AI agent in any new project, providing a compressed, comprehensive, and visual understanding of design constraints.

Move beyond fragmented tools like Notion for PMs and Figma for designers. By using a single, shared GitHub repository for business context, product briefs, designs, and code, teams can create joint context and dramatically increase alignment and speed.