Getting started

Introduction

System.exe is a Webflow framework built around a strict token architecture, a mathematically-derived type scale, and short utility classes. It's designed for design and development teams who need a scalable, maintainable system, not a collection of workarounds.

Why System.EXE

Most Webflow frameworks were built for speed, not scale. Client-First relies on long, flat utility classes and has no token layer. Lumos introduces tokens and fluid type, but the architecture leaks. Components reference primitive tokens directly instead of going through the semantic layer, and class names are still verbose. System.exe fixes this at the foundation.

What you get

A strict two-tier token system.

A strict two-tier color token system. Color values flow through primitive → semantic. Semantic tokens are applied directly to components, never primitives. Spacing and typography primitives are applied directly to elements.
A type scale built on musical intervals.

Desktop uses a perfect fourth. Mobile steps down to a major second. Heading roles and visual sizes are independent, an h2 can be 5xl or 6xl depending on the design, without touching document structure.
Short, scannable class names.

u-p-1 not u-padding-1. Your Webflow style selector stays clean.
Starter kits with proper architecture.

Need an SPA with Barba.js? The kit ships with routing, transitions, and token integration already structured correctly.

Before you continue

System.exe assumes familiarity with Webflow's class system, variable modes, and CSS custom properties. If you're new to Webflow, start with the official Webflow University before coming back here.