The State of Design Systems in 2025
As AI accelerates product development cycles, design systems have become the critical infrastructure that keeps quality high and teams aligned. Figma's Schema 2025 conference delivered a wave of announcements specifically designed to address the challenges facing modern design teams: multi-brand complexity, component scalability, and design-to-development handoffs.
This recap examines the key updates and their practical implications for teams building design systems that scale. With organizations increasingly adopting component-driven development approaches, these updates arrive at a pivotal moment for design and development teams seeking to maintain consistency at scale. If you're new to design systems, our Design Systems 101 guide provides foundational context for understanding these advanced features.
Major updates that transform how teams build and maintain design systems
Extended Collections
Manage multi-brand design systems by extending a parent collection while keeping brand-specific overrides intact.
Slots
Build truly modular, flexible components without detaching from the design system architecture.
Check Designs
Automatically flag hard-coded values and suggest variable replacements to maintain design system integrity.
MCP Server
Bridge design and development workflows with programmatic access to design system resources.
Variables 2.0
Enhanced design token workflows with JSON import/export and improved authoring experiences.
Code Connect GA
General availability of component documentation that developers can trust and implement accurately.
Extended Collections: Multi-Brand Management Redefined
Organizations managing multiple brands face a fundamental challenge: how do you maintain a cohesive design system while allowing each brand to maintain its unique identity? Extended Collections solve this by introducing a powerful inheritance model.
How Extended Collections Work
Extended Collections allow you to create a parent collection that serves as the source of truth for core design tokens, components, and styles. Child collections can then extend this parent while preserving their own brand-specific overrides. When the parent collection updates, those changes flow down to child collections--unless a child has explicitly overridden a value.
This approach transforms how agencies, franchises, and enterprise organizations manage their design ecosystems. Rather than maintaining separate design systems that diverge over time, teams can work from a shared foundation while maintaining brand autonomy. This is particularly valuable for organizations working with our brand identity services who need to maintain consistency across diverse brand expressions.
Practical Applications
- Global companies with regional brand variations can maintain a central design system while allowing regional teams to adapt colors, typography, and imagery for local markets
- Product suites requiring brand differentiation can share component architecture while expressing distinct visual identities
- Agencies managing multiple client brands can establish efficiency through shared component libraries without compromising client brand guidelines
Slots: Flexible Component Architecture
Traditional component libraries often force designers into rigid hierarchies. You create a button component, then create variants for different states, sizes, and styles--resulting in an exponential explosion of variants that becomes difficult to maintain and use.
Slots fundamentally change this paradigm. Instead of pre-defining every possible variant, Slots allow you to build components with defined slots where content, imagery, or other components can be inserted. This enables truly modular components that adapt to context without requiring a new variant for every use case.
Component Flexibility Without Compromise
With Slots, you can create a card component that has slots for a header image, title, subtitle, body content, and action buttons. Designers can then compose cards that meet their specific needs by populating only the slots they require--while the component maintains its design integrity and follows system guidelines.
This approach significantly reduces the number of components in your library while increasing the flexibility available to designers. Components become building blocks that can be combined in powerful ways, rather than rigid templates that must match predefined patterns exactly. When combined with our UI/UX design services, this flexibility enables rapid prototyping while maintaining design quality.
Check Designs: Automated Design System Compliance
One of the biggest challenges in maintaining design systems is ensuring that designers actually use them. Over time, designs drift away from the system as teams take shortcuts or simply aren't aware of available components and tokens.
Check Designs introduces automated validation that catches these issues before they compound. The feature scans your designs and flags instances where hard-coded values could be replaced with design tokens, or where custom elements could use standardized components instead. This automated approach complements our quality assurance processes by catching design inconsistencies early.
Automated Quality Assurance
Check Designs represents a shift-left approach to design system governance. Instead of catching compliance issues during design reviews or QA passes, problems are identified in real-time as designers work. This immediate feedback helps teams maintain consistency without creating bureaucratic overhead that slows down creativity.
The feature can be configured to match your organization's specific design system rules and priorities. Some teams might want strict enforcement of all token usage, while others might prefer to focus on high-impact areas like typography, colors, and spacing.
Developer Collaboration: MCP Server and Code Connect
The gap between design and development has long been a source of inefficiency and misalignment. Figma's Schema 2025 announcements address this through two complementary approaches: MCP Server for programmatic access and Code Connect for documentation.
MCP Server
The Model Context Protocol (MCP) Server enables programmatic access to your design system. Development teams can build custom tools that query design tokens, retrieve component specifications, and integrate design system information directly into their workflows. This opens possibilities for AI-assisted development, automated documentation generation, and tight integration with design systems in code.
Code Connect GA
Code Connect has reached general availability, providing component documentation that developers can trust. Unlike traditional design documentation, Code Connect examples are actual implementation code that developers can copy and use directly. The documentation stays synchronized with design changes, ensuring developers always have accurate, up-to-date guidance. This directly supports our full-stack development approach where design-to-development handoff efficiency is critical.
Programmatic Access
Build custom tools and integrations that access design system resources
Live Documentation
Component docs that stay synchronized with design changes
Platform-Specific Code
Implementation examples for React, Vue, iOS, Android, and more
AI Integration
Enable AI-assisted development with design system context
Variables 2.0: Enhanced Design Token Workflows
Design tokens are the foundation of design system consistency, but managing them at scale has traditionally been cumbersome. Variables 2.0 introduces significant improvements that make design token workflows more efficient and powerful.
JSON Import/Export
The ability to import and export tokens as JSON transforms how teams manage design tokens across systems. Tokens can now flow seamlessly between Figma and design token platforms like Style Dictionary, Tokens Studio, or custom token management solutions. This bidirectional synchronization eliminates the manual work of keeping tokens aligned across design and development.
Expanded Mode Support
Variables 2.0 adds improved support for multi-dimensional modes, making it easier to manage themes for dark mode, high contrast, localization variants, and other contextual variations. Teams can now define and preview mode combinations that would have been difficult or impossible with previous tooling.
Improved Authoring Experience
Creating and managing variables is faster and more intuitive. Bulk operations, improved organization tools, and clearer mode switching make it practical to build and maintain comprehensive token systems that scale across products and platforms.
Accessibility in Component-Driven Design
Design systems that scale must be accessible by default. When you build accessibility into foundational components, that accessibility propagates throughout every product and experience built on your design system. Schema 2025 updates reinforce the importance of accessibility-first component design.
Building Accessible Components
Accessible design systems require more than just accessible individual components. They need comprehensive documentation that tells designers and developers exactly how to maintain accessibility when using and extending components. This includes guidance on keyboard navigation, screen reader compatibility, focus management, and color contrast requirements.
Documentation Requirements
Every component in your design system should come with clear accessibility documentation specifying:
- Keyboard interactions and expected focus order
- ARIA attributes and their appropriate use
- Screen reader announcements and live region requirements
- Color contrast ratios and visual accessibility considerations
- Any known limitations and how to work around them
This documentation becomes part of the design system contract, ensuring that accessibility isn't compromised as components are used in new contexts or extended by teams across your organization. Our accessibility audit services help organizations ensure their design systems meet WCAG compliance standards.
Implementation Roadmap: Getting Started with Schema 2025 Features
Adopting new design system capabilities requires strategic planning. Here's how to approach integrating Schema 2025 features into your workflow.
Phase 1: Assessment and Planning
Start by evaluating which features address your most pressing design system challenges. If multi-brand management is a pain point, prioritize Extended Collections. If component flexibility is limiting your team's speed, focus on Slots. If design-development handoffs create friction, invest in MCP Server and Code Connect integration.
Phase 2: Pilot Implementation
Before rolling out new features organization-wide, conduct a pilot with a small team. This allows you to identify workflow issues, document best practices, and build internal expertise before scaling adoption.
Phase 3: Team Enablement
Create documentation and training materials specific to your organization's context. Share pilot learnings, establish guidelines, and provide channels for teams to ask questions and share their experiences.
Phase 4: Continuous Improvement
Design systems are living artifacts that evolve with your organization. Monitor usage patterns, gather feedback, and continue refining your approach as new Schema features become available. Regular design system audits help ensure your system continues to meet organizational needs over time.