75/75/75: why it's time for a design system to become doable
Main chat
A chat for vibe coders: news, guides, live cases, marketplace, and finding executors.
Yandex has launched a 75/75/75 program to accelerate development using AI. By the end of 2026, the company wants 75 percent of developers to use AI regularly, participate in 75 percent of the changes, and generate at least 75 percent of the code.
Speed shifts bottleneck
This does not mean that the product will be designed without people. But when code is created faster, the bottleneck is not the screens or the components, but the clarity of intent: what to do, what constraints cannot be broken, and how to verify the outcome.
For the designer, this adds value to the design system. It should be not just a library of beautiful components in Figma, but a set of executable rules: tokens, states, content restrictions, accessibility, adaptability and examples of behavior.
From layout to verifiable context
The more accurately the system rules are described, the less AI generation will produce visually similar but logically incorrect interfaces. The team needs to move from the phrase “do as on the layout” to structured requirements: what components are permissible, what states are required, what the error looks like, what happens on the mobile screen and what criteria the script is tested against.
Such a context is useful for both the person and the AI agent. It turns design from a set of artifacts into a source of solutions that can be replicated in a product.
New Design Responsibility Area
An interesting practical pattern is to show the difference between the intention, the result generated, and the rules of the system. This requires not only layouts, but also clear specifications, verification scenarios, content restrictions and accessibility criteria.
The Yandex program shows that AI development is becoming an organizational practice, not an experiment of individual enthusiasts. The designer in this model is important to include earlier: to form rules, quality criteria and test scenarios. Then the increase in speed will not lead to an increase in visual and UX debt.
Source: Яндекс