Andrew Antoshkin,
Design Engineer.
Design systems, agentic UI, and verification tools. I build interfaces and the guardrails that help engineers and coding agents ship them cleanly.
Projects
(11)See allPractice
(4)Design systems
I design components, tokens, and rules so the Figma file and the codebase stay in sync.
Tools
I build utilities around the design system: pack context for an agent, repair raw code, and check the output.
AI and code
I write specifications and rules that both engineers and coding agents can build from.
Verification
I verify output with code: AST and token checks on source files, plus build, axe, and Playwright on full browser runs.
Writing
(6)See allExperience
(4)
Own components, tokens, and documentation; connect Figma libraries with code and agent rules.
Led design system architecture, component libraries, and adoption across product teams.
Designed trading flows, portfolio views, and onboarding across web and mobile for retail investors.
Designed user flows and shared interface patterns across consumer digital services.
Most asked questions
(4)I don't stop at the mockup: I map the flows, specify states and tokens, and carry the work into code. That gives design, engineering, and coding agents one shared source of truth instead of three competing interpretations.
I lead components, tokens, and documentation for the Yandex HR Tech design system. Alongside it, I build open-source tools around coding agents: context packing, static token/import checks, and the ds-eval benchmark.
Without explicit context and automated checks, an agent invents its own Button and hardcodes colors. The tools cover three steps: pack system rules under a token budget, lint imports and tokens in code, and diff prompt runs.
The agent drafts against the spec and runs the checks. Problem framing, product tradeoffs, system architecture, and sign-off on what ships to production stay with me.