Stop taking screenshots. Just point.
I wanted to comment on 10 spots on one screen. Did I really need 10 screenshots?
3 min readShort notes, written from agency life
Short, practical pieces on design systems, handoff, workshops, UX writing and working with AI. What I do, why, and where AI fits. A few minutes each.
I wanted to comment on 10 spots on one screen. Did I really need 10 screenshots?
3 min readA client wanted "Shopee, but for fresh produce." Here's how I turned a chaotic room into one MVP.
"2 seats left" became "the seats on the left" in Thai. Later came thousands of rows of copy in a Google Sheet. So I built a tool to check the AI.
I had one Ghostty tab per project, and I never dared to close any of them. So I built an app to get back in.
I kept sending tasks to the wrong terminal. A small Claude Code mod fixed most of it.
Unnamed layers caused me trouble three times: with developers, with AI, and with a big team in a hurry.
My company asked for real prototypes on a phone. I taught my team to build them with AI. What worked was not what we tried first.
I built three Figma plugins before AI was this good. The first two took a very long time. The third, a few months later, went much faster.
I do not write code, but every AI change still gets a save point, a safe branch, and a review before it ships.
A plug that lets the AI see your actual tools. How I use it in Figma, GitHub and the browser.
A skill is my own process, written down once, so the AI follows it every time instead of guessing.
A mirrored file is not an RTL design. What flips, what stays, and who checks it.
Before tokens or AI, there is a direction the client and I pick by hand. How I get there.
Why colour, type and spacing become variables before the first screen, and which part AI can draft.
Nothing in this topic yet. Try another one, or ask me to write it.
No newsletter, no pop-up. Follow there, or email me if you want to talk about any of these in depth.