Yoona
Engineering
Engineer at Konde. Builds infra tooling.
Why we built our own changelog platform
Mintlify, ReadMe, and GitBook are all good products. None of them fit a multi-tenant publisher who ships docs, changelogs, and a blog from the same primitive. So we built kdoc — a single Cloudflare Worker that serves all three and ships in 200KB.
How we cut Claude Code token usage by 60% with RTK
We were burning $40/day on Claude Code at internal scale. RTK — a small Rust proxy that intercepts the most expensive tool calls and rewrites them — cut that to $14/day with no behavioural change. Here is how it works and why it is open source now.
Agents 101 — building your first multi-agent workflow
A practical guide to chaining agents in Konde Studio. The four anti-patterns that make multi-agent workflows fall over, the three patterns that make them work, and the worked example we use internally for shipping product changes.
Why we built kdoc on Cloudflare Workers
kdoc serves docs and blog content for the entire Konde footprint at sub-50ms globally for less than five dollars a month. Here is the architecture, the trade-offs, and the three things that surprised us about Workers in production.
KDF — the design framework powering Konde
KDF is the token-based design framework we built to keep fifty-six themes in lockstep across Studio, Caster, KW Render, and Konde Docs. Tokens in JSON, classes in TSX, dynamic-resolved at render — here is the architecture and why it works.
Shipping Sparkle integration for in-app updates
Konde Studio now self-updates with EdDSA-signed deltas, a native progress UI, and one-click relaunch. Here is why we picked Sparkle over rolling our own, and the three gotchas we hit shipping it.