AI-DesignLock: Layout Fidelity Wrapper for Multi-Model AI Development

Whoa, that's a lot of ground to cover for a beginner. You've got the design side sorted which is a huge head start, most people skip that and end up with a functional but ugly mess. The disconnect between your ChatGPT designs and Claude's output is probably the biggest headache you'll face since Claude loves to "improve" things you didn't ask it to change I'd stick with Cursor over Claude Code for this, the visual feedback loop is way faster when you're learning. For the stack I'd go React Native with Expo since it handles a lot of the mobile config pain, Supabase for the backend (auth, database, storage all in one) and it's surprisingly beginner-friendly for real estate data with row-level security built in. Skip Replit and Bolt, they're fine for toy projects but you'll outgrow them fast with something this complex For the prompt problem, try feeding Claude your ChatGPT design as a strict reference image with something like "reproduce this exact layout pixel for pixel, do not modify colors spacing or component placement, flag any deviation you're considering before making it" and regenerate if it strays. Take screenshots of every completed screen and compile them into a design system doc you can attach to every new chat session, that's the only way I've found to keep things consistent across dozens of screens. Build the frontend with hardcoded data first until the navigation flow feels right, then wire up Supabase one feature at a time, way less overwhelming than trying to do it all at once

the list is the problem tbh. you've written out a staff engineer's job description and you're trying to solve all of it before you have a working screen, which is the thing that kills beginner projects way more often than any of the individual items on it. the security half especially. row level security, rate limiting, incident response, pen testing, none of that matters at zero users and all of it is much easier to reason about once you can see the actual data model. supabase gives you RLS out of the box, turn it on per table as you create each one and that covers most of what you listed for a long while. if you're on supabase then auth, storage and the database are already handled, so your stack decision is basically just which editor you sit in. pick one and stop evaluating, the switching cost between cursor and claude code is smaller than the week you'd spend comparing them. on the design consistency thing, the fix isn't a better prompt, it's building the components once. make your button, your card, your input as real reusable components early and then "reproduce this screenshot" becomes "assemble these three things i already have" and the model has far less room to reinvent your spacing. realistic version of this: get one screen rendering with fake data this week. everything on that list gets easier to answer once something exists.