I demoed a prototype UI to our UI/UX team this week, an extension of the EMR rebuild. A second senior dev said he'd push it to production immediately if the contracting team didn't need to be looped in first. Then he reached out with something specific: apply the same UI/UX to our internal site, which was still running the same outdated styling as everything else.
Skills, not one-off prompts
I fixed real UI issues in our datatables and rebuilt the frontend. Rather than prompting for individual updates, I built AI skills to guide the work: reusable CSS classes, tokenized colors instead of hardcoded ones, and modularity instead of per-page fixes.
Building it so it travels
The goal was styles that apply to our other systems too. I reworked the styling from the ground up, then went through the existing files pulling in the new classes in place rather than leaving the new system next to the old one.
Three days
Planning and executing a rebuild like this usually takes days before any code gets touched. I had a new frontend in three. The site had run default Bootstrap styling for about 20 years; it has a modern look now. Plenty left to improve, but the gap between "outdated" and "current" closed fast.
Update: that rebuild is still in testing, and it's already led to something bigger. See the follow-up on becoming the lead on our new design system.