Kiril "dzhunka"Pronounced JOON-kuh Peyanski
Software Engineer
I work where human design meets machine reasoning. I love experimenting and prototyping, because it’s the best time ever to be a tinkerer, and I like sharing what I find along the way.
Design Engineer. Design systems, down to the last pixel.
I’m rebuilding a few design systems from scratch, because I love digging into their quirks and features. At Progress, I co-created the Kendo Design System.
Go on, pick one and poke around.
Have a question about your design system?
Ask meAI Engineer. Teaching machines to speak interface.
I built an engine where nobody designs the screen ahead of time. You ask, and an LLM composes the interface from your data, your session, and the design system, streamed node by node.
ui(prompt, data, state, capabilities, design_system)
Replaying recorded runs
-
Design systems for humans and machines.
I’m teaching the Kendo Design System to agents: the same tokens, components, and rules, written so a model can read them too.
Kendo design plugin -
Tools for agents.
For ten years, I built tools for developers. Now I build them for agents too: plugins that let a chat agent answer with an interface, or hand you a napkin to sketch on.
-
Designers who describe instead of draw.
I help teams of designers and developers work with AI. Developers adapt fast; for designers it’s a bigger shift, so I listen first. Now they describe changes by design intent, and code no longer stands in their way.
Figuring out AI for your team?
Ask meProduct Engineer. Products, from the very first commit.
I’m a Principal Software Engineer at Progress, and one of the first engineers on KendoReact. I watched it grow from its first line of code. Everything else branched off it: the themes behind every Kendo flavour, the docs site, ThemeBuilder, and later, AI inside it.
Building it was the start. Scaling and supporting it, release after release, has been the rest of the job.
-
mainKendoReact
Enterprise React components, from the first commit to thousands of users.
-
themes -
docs -
themebuilder -
aiAI theme generation
Describe a theme in words, get one back. It started as a hackathon prototype and shipped as a paid feature.
-
exploreWhat’s next
Exploring, prototyping, experimenting. Not all of it lands on main, and that’s the point.
Taking a product from prototype to scale?
Let’s talkCurious Engineer. Curious, out loud.
When something catches my eye, I dig in. Then I can’t keep it to myself, so it ends up on a stage or in a blog post.
-
The UI That Builds Itself: Exploring the Generative Front-End
What if an LLM wrote the code that turns your data into UI? Built live on stage, with interfaces that adapt to the user, the data, and the moment.
Slides -
React Components for Both the Client & the Server
Components rendered on the server, with just enough client code to stay interactive, and nothing written twice.
-
Polymorphic React Components for Both the Client & the Server
One data table that becomes a server or a client component, depending on where it renders, with minimal JavaScript either way.
-
Exploring the Future of Web Development: A Journey with KendoReact Server Components
Introducing the DataGrid as the first experimental KendoReact Server Component.
-
Getting Started with Color Module for Your Design System
Palettes, swatches, and intent: naming colors for what they do, not what they look like.
-
Responsive CSS Border Radius with the Fab Four Technique
A border radius that responds to its container’s size, in plain CSS.
Organizing a conference or meetup?
Invite me to speak