Specs for a registration redesign, a particle hero effect, and a new assistant app

A day that moved from planning to shipping to starting something new, all in one arc.

Client project (NDA)

I turned the product doc into a PRD for the registration redesign, focused on the core entities and the price tables, which is where the UI and UX have to be right. Then I ran domain-modeling sessions to break the work into specs and tasks the team can pick up, deliberately staying at modeling and prototypes with no CRUD yet. Part of the day was tooling for that: adding project audit skills and evaluating a few open-source review skills to see if they fit this codebase.

tgmarinho-ai-website

I built a hero effect I had been picturing: a portrait that fills in with particles as the cursor moves across it, revealing a robot image piece by piece. To protect LCP, it loads only after the page finishes rendering. The effect is a nice-to-have, so I would rather pay for a late reveal than block the user waiting on it. I wrote a tutorial post on how it was built, linked the code in the main repo, and packaged the whole thing as a reusable skill for anyone who wants it.

iTOP

I prepared the event product for self-hosting with Postgres and Dokploy. I also cleaned up a force-dynamic I had added when moving off Vercel, which turned out to be a symptom of a build-time database call rather than a real fix.

personal-os and a new app

I created a global save-to-personal-os skill so any coding agent, on any harness, can spin up a workspace and stash whatever I ask (docs, code, folders) into my personal-os, with the idea of a symlink that works from anywhere. I also started broddy, an Expo React Native personal assistant built on the pi.dev SDK, thinking about an embedded model so it does not burn the user's tokens.

The shape of the day felt right: finish planning one thing, ship a small delightful thing, and plant a seed for the next.