Companies and open source projects I have founded and built, along with related content.
The decisions, constraints, and convictions that shaped a design editor built for the AI era from the ground up.
Learn the core workflow, interface, and concepts to start designing with Nokuva in minutes.
A deep dive into how W0rktree splits version control into a local background process and a remote server, and why neither runtime duplicates the other.
How W0rktree's staged snapshots give teams real-time visibility into work-in-progress without polluting branch history.
How W0rktree's version-controlled, declarative TOML-based access policies replace platform-dependent permission systems with auditable, diffable configuration.
How to create, manage, and scale a design token system using Nokuva's Theme Editor — from color palettes to typography scales to spacing rhythm.
The decisions, constraints, and convictions that shaped a new version control system from scratch.
Every element on the Nokuva canvas is a VNode — a real HTML element, not a vector. Here is why that architectural decision changes everything about design-to-code workflows.
How Nokuva converts perfected designs into clean, tokenized code — and why designing first produces better output than generating code directly.
A prompt box and a preview window do not make a design tool. Here is the test that separates real design software from code generators wearing a mask.
Learn the core concepts, terminology, and commands to start using W0rktree as your version control system.
How W0rktree's staged snapshot visibility lets teams see work-in-progress in real-time without polluting branch history.
Define fine-grained, version-controlled access policies using TOML files that live alongside your code.
Import your Git repository, map the terminology, and adopt W0rktree incrementally with live mirror mode.
Nokuva uses six specialized agents instead of one generalist model. Here is the architecture, the reasoning, and why specialization beats generalization in AI-assisted design.
Every iteration in design costs pennies. The same iteration in code costs dollars. Here is the math behind why the design phase is leverage, not overhead.
Most collaborative tools relay messages through WebSocket servers. Nokuva uses an in-memory relational database as the collaboration engine. Here is why and what it enables.
Adding an AI sidebar to a legacy design tool does not make it AI-native. Here is what the distinction actually means and why it matters.
Inline values create inconsistency that compounds with every feature. Nokuva's token system makes consistency the default from the first component to the fiftieth page.
Why W0rktree forbids rebase and force-push, and how append-only history enables better collaboration.
Git was designed for 2005. Here is why patching it is not enough and what a modern version control system actually requires.
