Expert React/TypeScript Developer Needed to Rebuild AI Artwork Wizard for Lovable App

I have a Lovable-built web app connected to GitHub and need an experienced React/TypeScript developer to clean up the customer artwork wizard and customer portal. This is not a basic website job. The app already exists and the general business flow is working, but Lovable has struggled with the more detailed UI, image, wizard and AI prompt logic. Business overview: MySignSells is a subscription signage platform. Customers subscribe to a plan, receive an A-frame sign, and use a customer portal to request new promotional artwork. The customer selects a layout, enters promotion details, uploads logos/images if needed, generates artwork with AI, approves it, and then the artwork moves into an admin/production workflow. The current app includes: - public website - customer portal - artwork jobs - upcoming artwork schedule / entitlements - layout gallery - AI artwork generation wizard - logo upload / AI logo generation - QR code option - claims/support areas - admin CRM - artwork queue - production/shipping workflow - Stripe billing - GitHub sync from Lovable Main problem: The customer artwork wizard and layout system need to be rebuilt properly. Lovable has created inconsistent results and the wizard logic is not reliable enough. Main areas needing work: 1. Artwork wizard cleanup - Fix “Continue with this layout” scroll behaviour so it scrolls to the opened wizard panel, not the footer or wrong part of the page. - Improve layout selection state. - Ensure wizard state is reliable. - Ensure required/complete fields show correctly. - Keep mobile/tablet responsive. 2. Multiple Requests mode rebuild The customer can choose either Standard Request or Multiple Requests. Standard Request should remain more AI-led. Multiple Requests should become a structured, customer-controlled mode where the selected layout is split into numbered content areas. For Multiple Requests: - show the selected layout preview on the left - show numbered markers that point to real editable text/content areas - use dotted leader lines from the number to the exact text/content section - do not place numbers randomly - do not place numbers on QR codes - do not invent fields that do not exist in the layout - if the layout has no hero image, do not show a hero image field - show matching numbered input fields on the right - allow exact customer text - allow a small camera-icon upload where an optional small logo/image is relevant - uploaded images/logos should be treated as required/hard content if supplied 3. QR handling QR areas must be reserved for the QR step. If a selected layout contains a QR code area: - do not treat the QR code as an editable text/image slot - do not ask the customer to fill the QR code area manually - do not let AI generate fake QR codes - reserve the QR area for the app to insert the real QR code later 4. AI prompt logic The AI prompt builder needs to pass structured data, not vague notes. The AI prompt should include: - request mode: Standard or Multiple Requests - selected layout ID and name - layout composition rules - required content slots - optional slots - QR reserved area if applicable - customer-entered text - uploaded logo/image references - selected colour/theme - website/brand context - industry - product/service - offer/promotion message Rules: - Standard Request = AI has creative freedom but must follow selected layout, colour, website/brand, logo and customer inputs. - Multiple Requests = selected layout and numbered customer content are mandatory. AI can polish the design, but must not ignore or replace customer content. 5. Layout preview images There are approximately 24 layout preview cards. They need to be consistent and professional: - same A-frame shell - same frame/handle/wheels - same camera angle - same background - same shadow - same crop - same resolution - no artwork bleeding outside the black frame - crisp high-quality previews Only the poster/artwork area inside the sign should change. 6. Customer portal polish The customer portal should feel more modern, premium, fun, and simple. Current areas include: - dashboard cards - artwork jobs - upcoming artwork schedule - purchase additional artwork button - claims - support tickets - account The first priority is functional reliability, not a full redesign. Technical stack / likely tools: - React - TypeScript - Tailwind CSS - Vite - Supabase or Lovable Cloud - GitHub - Stripe - AI image generation / prompt-building logic - file uploads - responsive UI Important: Do not change billing, Stripe, signing, production, shipping, entitlement logic, or database schema unless specifically agreed. GitHub workflow: The project is connected to GitHub. Please do not work directly on main. Create a branch, make changes, and open a pull request for review. Suggested first milestone: I would like to start with a paid code review / audit. Milestone 1: - review the existing customer portal and artwork wizard code - identify where layout data, wizard state, AI prompt logic and uploads are handled - identify the cause of the scroll issue - recommend the cleanest implementation approach - provide an estimate for the build work Estimated audit: 5–8 hours. Potential later milestones: - wizard bug fixes - Multiple Requests structured slot rebuild - AI prompt builder cleanup - 24 layout preview cleanup/rebuild - customer portal UI polish Please apply with: 1. Examples of React/TypeScript apps you have worked on. 2. Whether you have worked with Lovable-generated code. 3. Whether you have worked with Supabase. 4. Whether you have worked with AI prompt-building or image generation workflows. 5. How you would approach fixing the artwork wizard. 6. Estimated hours for the first audit. 7. Your hourly rate. 8. Confirmation you will work on a GitHub branch and open a pull request.