How I designwith AI.
How AI fits into my design work, from a fuzzy spec to a merged pull request.
When code gets cheap, user experience and taste become the last moat.
Solving the wrong problem faster
AI can ship the wrong thing in a day instead of a month. It's still the wrong thing.
Solving the right problem
Knowing what people need and making it feel right. That's the part that can't be generated.
You've got to start with the customer experience and work backwards to the technology.
Steve Jobs · WWDC 1997Research with AI
Learn with Artifacts
Quick Prototype
Experience it
Edge cases & stress-test
Collect Feedback
Ship & measure
Research warms up Claude Code, and me.
An agent doesn't know the nitty-gritty of my problem and can't one-shot a solution. I steer it with context.
every AI agent, before warm upContext inputs · I steer
- Problem
- who it hurts, and when
- Users
- what they already do today
- Data
- what the numbers say
- Limits
- tech, time, business rules
- Decided
- answers, in my words
- Trade-offs
- what we give up, and why
- Open
- unknowns still being chased
Warmed up
Starts from my problem, not a guess.
Can explain it before I design it.
Artifacts turn complex information into consumable, interactive diagrams.
Claude explains the code as a page I can click and play with. It warms me up, far faster than reading files cold.
Creative ideas show up on an
interactive prototype, not a static screen.
Claude Code builds a rough working version. I use it like a user, and each gap I feel becomes the next idea. First Rank Pro's detail page, live:
AI imagines the edge cases I'd miss. Each one becomes a test.
What files could someone use to break this converter?
../../evil.txt/tmp/etc/passwd→ 9 hostile files, generated on every test run
SUSPICIOUS_RATIO“The archive expands far more than a normal archive (possible zip bomb).”
Caught from the packing list, before anything is unpacked.For UX, AI plays the user who pushes it off-brand.
How will people push this off-brand, or break it?
→ each one gets a designed answer
badge.color#00ff00→400 empty_prompt
2,000 characterscut to 500
enum · const · additionalProperties: falseAn off-brand colour, a made-up component or a magic pixel can't even be written.
The schema decides, not the prompt.The edge case I never thought of: right-to-left.
What kind of storefront could break an embedded widget?
!important on every class it uses→ 9 stress pages, each states its own pass test
- Nothing past the edgemeasuring…
- Toast stays on screenmeasuring…
- No clipped textmeasuring…
It mirrors itself: the CSS uses padding-inline-start and inset-inline-start, never left or right.
Prompting all day doesn't earn a pull request. Knowing Git does.
Understand
An artifact of the module I'm changing.
Pull
The latest from main.
git pullBranch
One branch per feature.
checkout -bBuild
With Claude Code, in the real repo.
claudeTest
On localhost, plus the stress suite.
npm run devPush
The branch, small commits.
git pushPull request
Developers review it like any other.
gh pr create
AI can mess up how it writes a feature. So I read the code.
Not a vibe coder. Certified in the languages my developers write, so I can read every diff before I push it.
I built the analytics dashboard, then hand AI the real numbers.
Every converter and every format pair gets its own real page, so ChatGPT always has an exact page to link.
Every failed conversion becomes a record. AI triages, I decide.
ERR-0031Samsung Galaxy S26 RAW photos could not be converteddeployedERR-0028Server results lost when a phone reloads the tabdeployedERR-0022XCF → PNG on phones: the engine never finished downloadingdeployedERR-0021A 39,883-page PDF ran out of memory, reported as “damaged”deployedERR-0016Visitors could not find where to type an archive's passwordverifiedERR-0010Uploads over 1 GB were read for 30 minutes before refusalverifiedERR-0007A real .deb opened as emptyverifiedERR-0018JPG → PNG: the file is not a JPEGexpectedERR-0016newrecommendedapprovedpr_opendeployedverifiedRAR → ZIP refused 4 times with ENCRYPTED, two iPhone visitors, same file. The refusal was right. So why four tries?
“The ENCRYPTED error did not lead the visitor to the password field.”
On ENCRYPTED, Options opens by itself with the password field. A wrong password asks again.
AI widens what I can do. It doesn't decide what's worth doing.
You've got to start with the customer experience and work backwards to the technology. You can't start with the technology and try to figure out where you're going to try to sell it.
Steve Jobs · WWDC 1997


