Alex uix

I help mid-level UX/UI designers stop prompting and hoping. A structured Claude-to-Figma workflow so you ship high-fidelity UI with speed...
2 joined
Profile picture
Alexandra I Digital Product Monetisation For CreatorsProfile picture@alex-v·Sep 10

Honestly I’m very proud for this moment! I launched my AI eBook. 

AI is here to stay, so I decided to write an eBook from my own experience as a Product designer using AI. The eBook, 4 Critical Steps for High-Fidelity Design with Claude to Figma roughly walks through how to let AI handle the heavy structural lifting so you can stay in your creative flow.

Hurray! This is so exciting!

Profile picture
Alexandra I Digital Product Monetisation For CreatorsProfile picture@alex-v·Sep 8

Why your Claude-to-Figma output looks generic (and the 4-step loop that fixes it)

Most mid-level designers I talk to are not bad at Figma. They are slow because they use AI like a slot machine.


They type “make a high-fidelity checkout screen.” Claude returns something that looks designed. Then they spend the evening rebuilding Auto Layout by hand, because the file is not actually a file — it is a guess.


Generic output is almost never a model problem. It is a context problem.


If you skip constraints, Claude invents them. If you skip personas, it designs for nobody. If you skip an audit, you polish hallucinations.


The loop that actually works:


  1. Boundaries first. Tell Claude what it is not allowed to do.

  2. Real context second. Scope, constraints, and the people who will use the product.

  3. Generate onto the canvas. Native, editable components — not a screenshot.

  4. Audit before polish. Catch the fake stuff, then use Figma as a scalpel for the last 10%.


If you have been prompting and hoping, stop adding more prompts. Add a process.


I wrote the full 4-step workflow here: