Skip to main content
Design-Token LibraryFeatured Proof

Palattes

A versioned SCSS/CSS design-token package plus a deployed showcase that consumes it — 995 palette files, a 3,097-palette searchable database, and a Python pipeline that generates and validates the whole thing.

995 palette files3,097 palettes2 consumers

Problem

Make a colour library queryable, accessible, and importable instead of a dead asset folder.

Build

995 SCSS palette files across 35 directories, published as a versioned MIT package

Outcome

Published design-token library plus a live showcase app that consumes it.

Sales Value

When selling developer tools, design systems, or component libraries, I have shipped the whole lifecycle rather than described it: a versioned, MIT-licensed token package with a release pipeline, and two of my own applications installing it as a dependency. That second consumer is the part that matters — it is the difference between writing a library and actually using one. It is also where most of my Python lives: a 22-script pipeline that generates and validates the data the package ships.

Tech Stack

Next.js 16TypeScriptPythonSQLiteSCSS

Highlights

  • 995 SCSS palette files across 35 directories, published as a versioned MIT package
  • Live showcase serving 3,097 palettes from a normalised SQLite database with full-text search
  • 22-script, ~3,700-line Python pipeline that extracts, enriches, generates, validates, and indexes
  • WCAG contrast checking and colourblind simulation built into the showcase
  • Consumed as a dependency by full-stack-genius and STR Command Center
  • Release-triggered publish pipeline; 87 commits