UI references you and your agents can actually use.
Every design you save becomes living code with real tokens and working interaction: yours to inspect, and your agents' to build with.
One-time purchase, no subscription, local-first. $79.
[ 01 / 05 ]Stash
Everything you love, one gesture away.
Three ways in. Same outcome: a coded reference in your library — tokens, interactions, and the reason it works — not a JPEG in a folder.
Drop it
Drop a screenshot anywhere.
Screenshots and GIFs land on the window. Pick which engine builds it; the cost of the run is visible before you say go. GIFs keep their motion — frames and timings are read, and the interaction gets rebuilt, not just described.
Match scored against the source · region by region
Save it from the browser
See something, keep it, keep browsing.
A small Chrome extension sends any design you find straight to your Stash queue. No download dance. No breaking flow. The page stays open; the reference starts rebuilding.
Chrome · one click · lands in All items
Say it from any agent
“Add this reference to uistash.”
One sentence in Claude Code, Cursor, or any MCP-connected tool, and the thing you are looking at becomes a coded reference in your library. The agent builds it; you Keep it.
MCP · HTTP + stdio · zero dependencies
[ 02 / 05 ]Browse
A gallery that's alive.
Every entry is running code. Folders to find it. Inspect, Motion, and Comment to read it — not thumbnails of design: design.
Organize
Put taste where you can find it.
Folders you name — Landing Pages, Mobile Apps, Components, Animation. Nest them. Filter by one. Counts stay honest. The library is folders and files on your Mac, not a cloud catalog.
Local git repo · your disk · yours forever
View
Live cards, not pictures.
Each card is a real render of the coded reference. A green dot when the interactions actually work. Select one and the inspector opens on its tokens, tags, and DESIGN.md — the reasoning written down beside the specimen.
Search that reads the code · Copy for Figma
Measure
Values resolve to the reference's own tokens.
Inspect mode measures the live entry like a dev tools panel — spacing, color, type — and names the token, not just the hex. Pin a comment to the exact element it is about; it stays anchored there.
Comment mode · element-anchored · local history
Scrub
Real animation, frame by frame.
The Motion timeline plays the reference's own interactions like a DVR. Scrub at whatever speed you need to see the easing. Make it interactive when a design implies motion — tokens and layout stay untouched, then it re-checks before it lands.
Timeline · reduced-motion aware · re-checked after
[ 03 / 05 ]Recipes
Your references are the ingredients.
A Recipe is the design language agents load in one call — built from what you saved and Keep. Today the app still says Styles; Recipes is the name. Same object: what goes in, and what never does.
From the stash
What you saved becomes what the agent cooks with.
Coded references — tokens with usage rules, DESIGN.md rationale, working interaction — are the ingredients. You can also bring a real project in: its token file and components, exact truth rather than measurement. Loose mood or complete system, same kitchen.
References · project tokens · Kept components
Assembled by you
Taste in, system out.
A Recipe holds declared tokens from a project or earned from the references behind them, the exemplars that define a direction, and the components you chose to Keep. You never fill out a quiz — uistash counts what you save and Keep. A thin set reads as a thin portrait.
Declared · earned · cited · never invented
One sentence
“Use the Felt recipe from my uistash.”
Say it once at the start of a session in Claude Code, Cursor, or any MCP tool. The agent loads the Recipe — tokens, references, Kept components — and every design task after that comes out dressed in it. Agents never see drafts: only what you Keep is served.
MCP · load once · build under it
Findings, not a score
Hand the work back. Get file and line.
An agent submits what it built and gets typed findings against your Recipe: values off the system, dangling tokens, off-grid geometry. Deviations it declared on purpose are reported separately from the ones it did not. Statements with receipts — never a grade.
Check · file · line · intentional vs accidental
[ 04 / 05 ] MCP
Your agent, with your whole Stash behind it.
A zero-dependency local MCP server, HTTP and stdio. One sentence connects the agent you already use; uistash stays on your Mac. Your keys, your logins, never touched.
You
01
Read
Every reference as living code: real tokens, working interaction, the reasoning written down. Not a screenshot to guess from.
02
Load
One sentence loads a Recipe: tokens, references, Kept components. Every task after comes out dressed in it.
03
Search
Ask for what a design is built with: layered shadows, pill radii, entries that honor reduced motion. Answers come with file and line.
04
Check · in build now
Soon your agent hands its work back and gets findings against your Recipe, with file and line.
Copies one sentence. Paste it into your agent once uistash is running.
[ 05 / 05 ] FAQ
Straight answers.
What will it cost?
$79, one time. Pay once: the app is yours forever, never expires, never phones home, and works offline. A year of updates is included; every version you download in that year is yours to keep permanently. After that, renew only if you want new versions — an optional separate one-time purchase of about $39, never a subscription. 14-day money-back guarantee, no questions asked.
Do I need my own AI?
Yes. uistash drives the agent CLIs and API keys you already have (Claude Code, Codex, Cursor, and friends, or a pasted key). It never resells AI or proxies your accounts. Keys stay on your machine.
Where does my data live?
On your Mac: folders, files, and a local git repo. Nothing leaves except by your explicit act.
Why not just hand my agent a styleguide?
A styleguide describes a design. A uistash entry is one: running code, real tokens, working interaction, version history. And a styleguide anyone can download is a styleguide everyone has, which is how everyone's product ends up looking the same. A Style is written from what you save and Keep, citing the references that earned it, so it cannot be anyone else's.
What is uistash not?
Not a cloud service. Not a subscription. Not a screenshot organizer: an organizer hands your agent pictures to sort, uistash hands it the design itself, in code, with your real tokens. Not a catalog of other people's design systems: a style you download is someone else's decisions, sold to everyone who asks. Not another AI that claims to know you without showing its evidence.