Registry
How wristkit is distributed and how to keep your copy in sync.
What is the registry?
The registry is this site. Each component page lists the files you need, with a copy button on every file and the destination path in your project. There is no CLI, no SDK and no install step beyond pasting the code.
That choice keeps wristkit simple. You always see the real code before you run it, you can diff it in your editor, and there is no extra surface between us and your project.
Available items
| Name | Path in your project | Where to find it |
|---|---|---|
TodayActivityCard | components/wristkit/today-activity-card/ | TodayActivityCard |
| Route handler | app/api/wristkit-sync/route.ts | Installation |
| SQL migrations | Supabase SQL editor | Installation |
| iOS Shortcut | wristkit-sync.shortcut on iPhone | Shortcut setup |
How to update
When the files on this site change, copy them again. Diff your local copy against the new content in your editor and apply the parts you want. Most updates are additive (new states, new options) and a side by side diff makes them obvious.
There is no versioning beyond the wristkit release tag on GitHub. If you pin to a specific commit, copy from that commit's docs build.
Why no CLI
Earlier drafts of wristkit shipped a wristkit CLI that fetched JSON from a registry endpoint and wrote files into your project. We dropped it for v0.1 because:
- It added an attack surface (path traversal, registry integrity, package install confirmation) that did not earn its keep for four files.
- Most users want to read the code before pasting it. A copy button does that better than a download.
- Updates were opaque. A copy paste loop is honest.
If you really want to script the copy, a curl + jq against the files on this site is a few lines.