AI drafts, I decide
AI is great at options and first drafts. Choosing what's right for real users is still my job.
AI Lab
A prompt is just words, and words are where every interface starts. Here's how I use AI workflows and tools to go from words to design to code, and the rules I keep so the result still feels human.
β― pyrus run --from words --to code
β research AI synthesised 12 interview notes β 4 themes
β ideate generated 10 user flows β kept the best 2
β design 3 layout variants in Figma β 1 refined by hand
β build <CheckoutStep /> + tests, reviewed line by line
βΈ test waiting for real humans to try itβ¦ π
# AI drafts, I decide. Done in days, not weeks.
// rules.md
AI is great at options and first drafts. Choosing what's right for real users is still my job.
AI can summarise research, but it can't replace watching a real person use the interface.
Generated code gets reviewed, tested and made accessible. If I ship it, I understand it.
// workflow.yml
Summarising interview notes, clustering feedback into themes and drafting research questions.
Talking to users, spotting what they don't say, and deciding which problem is worth solving.
Generating user flows, edge cases and "what if" variations I might not think of alone.
Sketching the flows that fit the product's goals and cutting the ones that don't.
Placeholder copy, image concepts, layout variations and checking colour contrast.
Visual hierarchy, the design system, and the details that make it feel crafted.
Scaffolding components, writing tests, refactoring and generating first-pass UI from a prompt.
Architecture, accessibility, performance and the motion that makes it feel alive.
Drafting test scripts, summarising session recordings and flagging accessibility issues.
Running sessions with real users and deciding what to change next.
// ai-toolbox.json
From the blog
I write about the AI workflows that work for me, the ones that didn't, and what they mean for UX.
My AI-powered design-to-code workflow