01/ 06
Motion Garden UI


I designed and built Motion Garden, a catalog of animated React components. Each one runs live on its page with a control for every prop, and when it looks right you copy the source, or a full brief for your coding agent. 147 components are live, and 44 of them sit behind a paid Pro tier.
What it does
- Every component page has a live preview, a Controls panel (number, enum, boolean and color props), the source, an install command and a props table. All of it comes from one typed registry entry per component, so the docs can't drift away from the code.
- Tuned values live in the URL, so a preview you've tuned is a link you can share.
- "Copy for Agent" builds one paste with every source file, the dependencies, the props and the integration rules, ready for Claude Code, Cursor or any other agent.
- The catalog covers backgrounds, text animations, micro-interactions, power-user systems and hero templates. The heavy ones, like Aurora, Grainient, Black Hole and Mycelium, are WebGL shaders. Ten components are adapted from React Bits (MIT) and credited on their pages.
How I built it
It runs on Next.js 16 with Cache Components, so most of each page is prerendered and Shiki highlights the code on the server. No syntax highlighter ships to the browser. The Pro gate lives on the server too: for a locked component the source never reaches the client, only a "locked" marker does. Sign-in is Supabase with GitHub, data is Postgres through Drizzle, and payments go through Polar at $4.99 a month or $99 lifetime.
Polar webhooks push payment events, and a sync on the checkout return page pulls them in case a webhook gets lost. Both write the same entitlements row. Lifetime beats a subscription, and buying lifetime cancels the old subscription. A lifetime order that's refunded or charged back grants nothing, because once someone has copied the source, you can't take it back.
The paywall only turns on when Polar, Supabase and the database are all configured: a deploy that can't sell anything doesn't lock anything. That's a tradeoff. If one of those settings goes missing in production, the Pro source is open to everyone until it's fixed.
What broke and how I fixed it
- In July, 19 animated components drew one frame and froze. Each one wrapped its draw call in the same one-line fallback, and that fallback turned every successful frame into the stop signal. My test script had passed all 19, because it only checked that something was drawn. I fixed the wrapper, made the pattern fail the build, and changed the script to count real draw calls over two seconds.
- A deploy with the Polar webhook secret set but no database accepted payment events, then crashed before writing the entitlement, and Polar kept retrying. The webhook route now checks for both up front and answers 503 with the name of the missing setting.
I built it over 189 commits between July and October 2026, 82 of them with Claude, along with a separate admin console that reads the same database to track members, revenue and feedback.

Open to full-time roles