Words.

Polishing a UI in the browser with Cursor composer is so much more satisfying than pushing pixels in Figma.

The argument for wireframes in the design process is usually that it's the fastest way to explore many different ideas. I'm not sure that's true anymore.

I can create a Claude artifact or Cursor prototype with about the same level of effort as writing this post.

And I can iterate through several ideas with more realistic fidelity in a just a few minutes.

Prototyping with Claude is great...until it isn't. Sometimes I get stuck in loops where it starts to forget what it's doing and I'm just clicking the "Try fixing with Claude" button until I hit my rate limit 😞

WIP: Staff member work schedule

https://paulstamatiou.com/the-startup-designer

I'm fairly technically inclined (for a designer), but one of the blockers for me getting into the codebase is dealing with dev environment errors.

Cursor removes most of that blocker for me. It usually gives me the command I need to run to fix dependency problems.

AI isn't a panacea. I still need humans to fix stuff sometimes. I will take the advice to "consult with your team" here.

I could potentially muddle through and figure out how to fix it. But there's a good chance that'll take me an hour or two. And simply pairing with a dev will probably resolve it in 5-10 minutes.

I've really been liking Claude Artifacts for knocking out simple prototypes. Prototyping anything with mild logic complexity is a PITA in Figma. Here's a quick example.