whenever i tell someone i'm all in on vibe coding, they ask:  

"what are you building?"

wrong question. i'm building everything i can think of.

the biggest opportunity right now is learning how to go from idea to execution as quickly as possible.

it's actually a disadvantage to focus on a single idea.

why?

the experiences you can create in 12-18 months will look nothing like the apps we're used to. 

we are, without a doubt, in the skeuomorphic phase of post-AI product design right now.

fixating on a single idea and app form factor is putting yourself at risk of quickly becoming obsolete. we're about to enter a time where something you ship can become antiquated in a matter of days.

here's what i think is worth focusing on:

1. process and workflow with AI code generators
2. falling in love with a problem (not a solution)

the goal is to be in a position to ship something useful as fast as you can write a tweet.

i'm also curious to see how you incorporate your designs into vibecoded projects 

design + cursor aren't always so compatible 

still use chatgpt to create visual assets

i hear you

part of the fun of vibecoding, for me, is approaching it more as a product builder/designer, and you can do a lot with gestures, interactive buttons, and simple animations 

it's still pretty challenging to *vibe design* at a high quality without babysitting chatgpt

i haven't really spent much time designing lately. mostly prompting and using design MCPs like Magic MCP.

at some point, when i feel more confident about executing, i'll think about this more deeply.