8+Projects·

8+Years·

50+Articles

GitHub YouTube LinkedIn X

Engineer · Founder · Builder

I build things that
should already exist.

I'm Sean Filimon. I run LegionEdge—parent company of Nokuva, W0rktree, Foltrac, and Tavoc. If a tool doesn't exist and it should, I build it. If a process is painful and it doesn't have to be, I fix it.

I write about what I learn because the best way to understand something is to explain it. This site is where I do that—deployment, distributed systems, version control, and the craft of building software.

Read My Story View Projects

Sean Filimon

Based in California

Projects

(7)

The next generation of developer tools

Cross-cloud deployment with full visibility

The premier design software for the AI era

IDE built for speed and monorepo workflows

Next-generation version control built in Rust

Open Source Maintainer

Backend server engine for building and scaling systems

Software solutions for the medical industry

Content

(18)

Building Nokuva — the thought process behind AI-native design

The decisions, constraints, and convictions that shaped a design editor built for the AI era from the ground up.

Declarative Access Control in W0rktree — Terraform for Permissions

How W0rktree's version-controlled, declarative TOML-based access policies replace platform-dependent permission systems with auditable, diffable configuration.

w0rktreeaccess-control

Staged Snapshot Visibility — How W0rktree Solves Team Coordination

How W0rktree's staged snapshots give teams real-time visibility into work-in-progress without polluting branch history.

w0rktreecollaboration

Inside W0rktree's Two-Runtime Architecture

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.

w0rktreearchitecture

Getting started with Nokuva

Learn the core workflow, interface, and concepts to start designing with Nokuva in minutes.

nokuvagetting-started

Building W0rktree — the thought process behind replacing Git

The decisions, constraints, and convictions that shaped a new version control system from scratch.

w0rktreeversion-control

Guideintermediate

Building a design system in Nokuva

How to create, manage, and scale a design token system using Nokuva's Theme Editor — from color palettes to typography scales to spacing rhythm.

nokuvadesign-system

Virtual DOM: why design structure equals code structure

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.

nokuvavirtual-dom

Guideintermediate

Converting your design to production-ready code

How Nokuva converts perfected designs into clean, tokenized code — and why designing first produces better output than generating code directly.

nokuvacode-export

Getting started with W0rktree

Learn the core concepts, terminology, and commands to start using W0rktree as your version control system.

w0rktreeversion-control

Guideintermediate

Migrating from Git to W0rktree

Import your Git repository, map the terminology, and adopt W0rktree incrementally with live mirror mode.

Guideintermediate

Understanding staged snapshots

How W0rktree's staged snapshot visibility lets teams see work-in-progress in real-time without polluting branch history.

w0rktreecollaboration

Declarative access control in W0rktree

Define fine-grained, version-controlled access policies using TOML files that live alongside your code.

w0rktreesecurity

Why design tools that skip design aren't design tools

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.

Multi-agent AI: why one model doing everything produces mediocre results

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.

The cost of skipping the design phase

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.

Real-time collaboration at database speed: SpacetimeDB vs. WebSocket relay

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.

nokuvaspacetimedb

AI-native vs. AI-bolted-on

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.

References

(1)

How LegionEdge Built a Real-Time AI Prototyping Platform with Together Code Sandbox

LegionEdge used Together AI Code Sandbox to launch 3 months sooner and get 2s cold starts, giving builders lightning-fast, real-time cloud development.