These are mini apps rebuilt to the wabi-miniapp-template contract, so importing one into Wabi copies the files instead of asking a model to recreate the app from reading it. The tuning survives.
Each zip is the whole working tree: a pure sim, an isolated renderer, one durable state object, and a single
platform seam at src/wabi-shim.js. Storage, haptics and logging all pass through that one file —
which is why it is the only thing the import has to rewrite.
Importing one
- Download the zip.
- Drag it into a Wabi chat.
- The import throws away
index.htmlandsrc/main.js— they are the dev harness and the boot file — rewrites the body ofsrc/wabi-shim.jsinto store and SDK calls, and points the asset paths at Wabi's registry. Everything else is copied.
Running one standalone needs a static server, not a double-click: npx serve inside the unzipped
folder. ES modules cannot load over file://. The harness you get is a phone-sized frame with an
error badge, an FPS meter and a QR code — and a mock of the chrome Wabi floats over every mini app, so the
overlap is visible while you build. Contract:
sotabot/wabi-miniapp-template.