I hope some members here have some UI design experience and have run into this issue before. So I use Claude Design and Open Design to create layouts for the web apps I build. Both tools generally design the interfaces with React Components. All cool, I use these as prototypes. The problem is I do not use React in my projects so I need to convert these designs to my stack. And this is were I run into a problem. No matter what I do during the conversion the designs are approximated and are not the same design by a long shot. I am stuck. If I can't figure out the prompts to make this work I cannot setup a ICM system to make this work reliably. My experience is literally the reference design is just a suggestion and not a source of truth no matter what prompts I use. This is the same for Codex and Claude Code. How do I fix this process? Anyone has encountered this before?

1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?

I've been playing around with Claude for a while, optimising workflows, supercharging a recent discovery sprint. But this week I actually shipped something. A simple idea capture tool for Mac. I used to use Things 3, and whilst the app structure never quite worked for me, I loved the quick capture feature. Keyboard shortcut, text input, thought saved. I've tried everything since: Apple Shortcuts to Reminders, Quick Notes, third-party apps. Nothing matched how I actually work. So I built my own. It's written in Swift, a language I've never touched before. I've been following development best practices as far as I remember them, pushing to a GitHub repo, branching for new features. Notes save as JSON that my ICM workspace can action, The whole thing was built with Claude. I haven't thought about anything else all weekend.
 Scope creep is real. It now has optional task types, a menu bar drop down with sync status, a live list of recent captures, inline editing, tagging. I drafted the initial design in Figma, then went back and forth between VS Code and Figma, designing where I needed to, tweaking code where I needed to. As a designer, syntax was always the wall between having an idea and building it. But working in a real codebase, you're closer to the actual product. It allows a level of finesse you can't achieve in Figma. Refining a micro interaction, adjusting an animation timing, polishing subtle UI details. I am very excited to make progress with my ICM workspace build out, lots of product ideas to be built!

You just watched the full 23-minute folder architecture walkthrough. Vote below, then drop your use case in the comments. What are you building this system around?

Intros for The Connection Hub - The Vault 👤 Who I am: (name + where you're based) 🛠️ What I actually do: (the specific work — not "I'm in real estate" but "I run a 3-agent team doing residential resale in Austin") 🤖 What I'm building with AI right now: (your current project, workflow, or the thing you're stuck on) 🎯 What I'm looking for connection-wise: (pick one or two) 💡 Someone who's solved [X] 🤝 A collaborator / accountability partner 👀 Just here to learn from people in my field 🧰 Trading workflows & systems 📬 Best way to reach me: (DM here / comment / link)