Reduce friction and cognitive load of using the design system

We've made a lot of progress on the DS docs for human consumption, but we've heard a desire to provide more help using the design system code for "computer consumption", and bringing it closer to where developers are working. This could include in AI, IDEs, bots, scanners and linters etc. The goal would be to reduce friction and the cognitive load of using the design system and context switching between code and docs.

Some solutions could be:

• Separating out the design tokens for consumption in other projects
• Creating an API-like interface for parts of the design system
• Creating a way for AI to index or ingest the design system (structured docs and examples, MCP servers)
• Bringing the design system API closer to IDEs with common patterns such as autocomplete code suggestions
• Making it easier to spin up a new project using our design system, including easier installation
• Making it easier to use the design system in quick prototypes or projects outside our core product

I'd love to explore which of these would be useful to our consumers and what we could prioritize for FY27