A zero-dependency, open-source library: 60 canvas animations and a tokenized UI kit behind one API
(Galaxy.create()), ~20 kB gzipped, accessible by default — and it ships its own MCP
server. I designed and engineered all of it. Best experienced live, so the demos below are real GalaxyJS,
running on this page.
A zero-dependency, open-source animation + UI library (v3.1.0 “Nova”, MIT) built solo: 60 canvas animations and a tokenized UI kit behind one API, ~20 kB gzipped, accessible and reduced-motion-safe. It ships TypeScript types, its own MCP server, a deterministic machine-readable manifest, ESLint, CI on Node 18/20/22, and unit + live-MCP integration tests.
Galaxy.create(type, target, options)data-galaxy) or imperative; live update() / pause / resume / destroy--gx-* tokens + Galaxy.theme(); light/dark out of the boxrequestAnimationFrame loop for the whole page; off-screen auto-pauseprefers-reduced-motion (one static frame); HiDPI via devicePixelRatioOne constraint shapes the whole library: add a beautiful, accessible cosmic backdrop — or a working modal, toast, or tab group — in a single line, no build step, nothing in your dependency tree. The API is the product as much as the pixels are.
60 canvas animations, each live-tweakable. The performance is the part I’m proudest of,
and you can watch it below: every surface shares one requestAnimationFrame loop,
auto-pauses off-screen via IntersectionObserver, renders at devicePixelRatio,
and falls back to a single static frame under prefers-reduced-motion.
Live, on this page — not a screenshot. Every stage below is a real GalaxyJS instance, all sharing one render loop, each auto-pausing as it scrolls off-screen, and all rendering a single static frame if you prefer reduced motion. Several of these — supernova, galaxy merge, lattice, orrery, star cluster, magnetosphere, starburst — are new in v3.1.0.
Beyond backdrops, it’s a usable UI kit — all driven by --gx-* tokens,
so one Galaxy.theme() call re-skins everything. Try it live:
All live components, straight from the library — buttons, inputs, a switch, badges, a tooltip and rating, tabs and an accordion, plus Galaxy.toast(), Galaxy.modal(), Galaxy.confirm() and Galaxy.drawer() on the buttons above.
GalaxyJS ships its own MCP server with a manifest generated from the runtime, so the effects an AI agent sees can never drift from the code. Four tools let an agent discover everything and return ready-to-paste code in one call — the same AI-native contract approach as my eds-mcp design-system server.
Packaged like a real product: TypeScript types, a ~20 kB-gzipped bundle on unpkg/jsdelivr,
a deterministic manifest, and two test suites — one dependency-free, one that boots the real MCP
server over stdio — all run on Node 18/20/22. Clone it and npm run validate is green.
What it evidences is range: alongside the regulated-finance work, GalaxyJS shows I can design and engineer a polished, zero-dependency front-end library — API, performance, accessibility, a tokenized system, a real build and test pipeline, an AI-native contract — solo. It’s a self-initiated open-source project, not a client deployment, and its numbers are measured facts. The discipline is the same one I bring to fintech; the domain is creative.
GalaxyJS connects two threads: shipping AI-native open-source the right way, and front-end craft held to a production standard.
A machine-readable single source of truth served to humans and AI agents alike — the same MCP + manifest discipline across very different domains.
Pixels held to an engineering standard — one render loop, off-screen pausing, HiDPI, reduced-motion, and a tokenized component system.