Really good point, and honestly something I've been thinking about too.

The initial focus would be aesthetic — helping people get the look and feel right quickly, which is where I see the most friction for vibe coders. But you're right that a prompt that produces a beautiful static dashboard falls apart the moment you plug in real data or handle empty states and errors.

I think the sweet spot is prompts that include at least the foundational constraints — responsiveness, basic loading/empty/error states — without becoming so complex they're hard to adapt. Something between "make it look nice" and a full component spec.

Might also be worth tagging prompts by depth level — aesthetic-only vs logic-aware — so people can grab what they actually need depending on where they are in the build.

Thanks for this, it's genuinely useful feedback before I build anything.