magma-kit

the shared half of the magmacrunch desktop apps

The shared parts of magmacrunch's desktop apps, like SPRITE//FORGE and DECK//PRESS: what every app needs that has nothing to do with what it's for, such as menus, undo, settings, keyboard shortcuts, colour themes and crash logs. Every app gets an identical copy, so they all behave the same way.

the technical version

Everything a magmacrunch desktop app needs that has nothing to do with what the app is for: crash logging, the bridge to the native side, keyboard shortcuts, undo, settings, dialogs, a menu bar, themes, and the Rust underneath them. The apps are built with Tauri; hypnopompia does the same job for the App Store builds.

Every module here started as two or three copies in different apps and was merged once they had been compared. Anything only one app needs stays in that app.

It runs no app logic of its own. An app passes in its vocabulary (its key bindings, its commands, its colours), and the kit's files stay byte-identical in every app that uses them.

running in your browser

Three of the apps also ship as web pages on this site, and each one carries its own copy of the kit.

what's here

js/ The runtime: crash-reporting boot, the bridge to Rust, keys, undo history, prefs, modals, DOM helpers, a menu bar drawn in the page, and the theme picker
artstore.js Imported images kept off the document by reference, so one photo is not 11 MB in every undo state
crate/ The Rust half: file access contained to its folder, the shared log file, tray-popover placement, unsaved-change tracking with a close guard, autostart
themes/ The magma-themes palettes, so every app can offer the same looks while keeping its own as the default
sync.mjs Byte-copies the kit into an app and records a hash per file; --check catches any copy that has drifted
new-app.mjs Stamps template/ into a new app that builds and runs on its first try
package-pwa.mjs Turns an app's web half into an installable, offline web app from one manifest file
testkit/ The test harness the apps share, plus an integrity check that runs in each app's own suite

built on it

keeping the copies in step

Every app gets an exact copy of these files. The copies are compared from both ends, so if one is edited by mistake the tests fail, instead of the apps quietly drifting apart.

the technical version

A kit file is byte-identical in every app. Nothing is templated on the way in, so a hash comparison is a complete drift check, and it runs from both ends: each app's own tests catch a kit file edited in place, and the kit's tests catch a change made here that never reached an app.

Edit a kit file here, never in an app, then sync it out:

node ../magma-kit/scripts/sync.mjs .          # vendor into an app
node ../magma-kit/scripts/sync.mjs --check .  # is this app current?
node scripts/new-app.mjs ../my-app --name "MY//APP" --ns MyApp --from ../sprite-forge

PolyForm Noncommercial 1.0.0 · Copyright 2026 magmacrunch media

// source access //

magma-kit is developed in-house and is not publicly distributed. It ships inside the apps it exists for, rather than on its own.

For source access, licensing, or anything else, email info@magmacrunch.com.