A small tool built for the way we already work.

Across a variety of projects I'd built dozens of patterns — empty states, paywalls, onboarding flows, toasts — usually well, and then promptly forgot where any of them lived. The next time I needed an empty state, I asked myself “how did I solve this before?”.

I tried the obvious things: a Figma file called patterns, a Notion page, a Slack channel called #screens. Each one decayed within a month. The problem wasn't storage — it was the gap between where patterns are made and where teammates look for them.

LookBooksplits the loop into two surfaces: a Figma plugin (the place you already work, so capturing is one click) and a read-only webApp (the place to send a teammate a URL). Both speak to your own Supabase, so there's no new vendor to onboard and the data stays where you can see it.

I deliberately kept the surface small. v0.1 ships the loop and nothing else — capture, tag, browse, deep-link back. Anything more can wait until the loop earns it.

A v0.2 is on the bench: mobile-first layouts for the webApp, tag rename and merge, a proper command palette. I am not in a hurry — the goal is one good tool, not many features.