Next I set up the Figma x Cursor MCP bridge that lets cursor directyl read Figma frames. This took some back and forth. I didn’t want new type styles or colors cluttering up the codebase. My prompts explicitly referenced the existing theme and typography kotlin files.

Reply to this note

Please Login to reply.

Discussion

Instead of trying to one-shot entire screens, I took a component-based approach. I exported individual components like buttons, input fields, and balance displays separately. Cursor generated Kotlin code for each component.

My favorite discovery: Android Studio’s Compose Preview. Seeing components live was a huge productivity unlock. The Kotlin code spit out by Figma x Cursor MCP often needed adjustments. Spacing, borders, etc... but instant visual feedback made fine tuning much faster.

After lots of re-prompting, troubleshooting, tweaking designs, I got a working wallet prototype. Still some bugs, but it’s live, and it’s pretty functional. https://blossom.primal.net/3a7e9ee284afc948066d0d84d56f5bdb5f0e7c6e722e80971dc24cb5d62b4c3b.mp4

Still a WIP but I’d love feedback. Full post with all workflow details here.

https://open.substack.com/pub/orangewindjammer/p/vibe-designing-a-bitchat-cashu-wallet

Nice! Is there an SDK or github link?

Neermind...see it at the bottom of the substack.