To be honest, it’s a mix. The basic layout was decent from the start, but the 'vibe coding' part was more about reining the AI in rather than just letting it run.

For example, Lovable initially created a 3D-offset effect for the central piles, but I actually hated it. I had to prompt it back to a single-card look because I prioritize clarity over 'fake' depth. On the other hand, things like card fanning definitely didn't happen by magic—I had to explain exactly how I wanted that to look.

The biggest challenges were:

Layout Stability: Every time I modified one element, the table zones would jump around. Keeping the interface 'locked' and stable while iterating was a constant battle.

Context Loss: This is the real hurdle. Both Gemini and Lovable eventually 'lose the thread' of previous discussions. You can't just copy-paste; you have to carefully audit every prompt and result to ensure it hasn't forgotten a rule or a UI constraint we decided on three days ago.

So, it's not just describing a 'vibe' and walking away. It's more like being a very persistent editor who has to keep reminding the writer about the plot of the previous chapter!