Personalized Communication Tags
Enhancing communication for autistic and ADHD individuals.
Made For Me is dedicated to improving interactions for autistic and ADHD individuals through personalized communication tags. Our innovative tags facilitate understanding and connection between children and others, providing them with a voice in conversations. Based in Australia, we strive to bridge communication gaps to foster a more inclusive environment.
Claude Code Master Build Prompt — V1 Australian Communication Tag E-Commerce Store Copy the prompt below into Claude Code to build the V1 website. PROJECT: Australian Communication Tags E-Commerce Website — V1 You are the lead full-stack developer, UI/UX designer, database architect and DevOps engineer. Build a complete, production-ready e-commerce website for an Australian business selling 3D-printed communication tags. The website should be inspired by the general customer experience and product-store structure of established communication-tag businesses such as Talkies Cards, but it MUST be an original website. Do not copy Talkies Cards' branding, logo, images, product photography, product descriptions, exact product designs, exact page layouts, CSS, icons or illustrations. Use only general e-commerce concepts as inspiration. The finished website must look like a professional independent Australian brand. 1. BUSINESS Working brand name: "Made 4 Me" Make the brand name easy to replace later. Business: Australian business selling practical 3D-printed communication tags and communication aids. Target customers: - Parents - Families - Teachers - Schools - Education assistants - Support workers - Disability-support customers - NDIS customers - People who benefit from visual communication tools Brand positioning: "Communication made easier." Brand personality: - Friendly - Modern - Professional - Accessible - Practical - Australian - High quality Do not make medical claims. Do not claim products diagnose, treat, prevent or cure any condition. Do not make unsupported claims such as "child-proof", "waterproof", "non-toxic" or "therapeutic". 2. CORE TECHNOLOGY Use: - Next.js - TypeScript - Tailwind CSS - Supabase - Stripe Checkout - Vercel - GitHub Use the current stable versions. Use App Router. Use server-side functionality where appropriate. Do not use unnecessary libraries. Keep the application modular and maintainable. 3. HOSTING ARCHITECTURE Customer → Vercel → Next.js → Supabase → Stripe Checkout → Customer payment → Business bank account Supabase: PostgreSQL database, product data, tags, collections, orders, customers, reviews, admin data and storage where appropriate. Stripe: Checkout and payment processing. Vercel: Hosting, deployment and HTTPS. Do not build your own credit-card payment system. 4. PROJECT STRUCTURE Create: /app /components /lib /types /public /styles /supabase /scripts Use reusable components: Header, MobileNavigation, Footer, ProductCard, ProductGrid, ProductGallery, ProductOptions, TagSelector, ColourSelector, AttachmentSelector, QuantitySelector, AddToCartButton, CartDrawer, CartPage, CheckoutButton, ReviewSection, FAQSection, NewsletterSignup, TrustBadges, SchoolCTA, NDISCTA, AdminSidebar, AdminHeader, AdminProductForm, AdminOrderTable, AdminTagManager. 5. BRAND DESIGN Create an original visual identity. Do not imitate Talkies' exact design. Colours: Background #FFFFFF Primary text #1F2937 Secondary text #6B7280 Primary brand #2563EB Secondary accent #F59E0B Light background #F8FAFC Border #E5E7EB Success #16A34A Error #DC2626 Use CSS variables/design tokens so colours can be changed globally. Typography: Inter or another clean modern sans-serif. Use large product photography, clean cards, rounded corners, generous spacing, strong CTA buttons, clear prices, excellent mobile layout and minimal animation. 6. NAVIGATION Desktop: LOGO SHOP - Communication Sets - Individual Tags - Regulation & Sensory - Build Your Own SCHOOLS & EDUCATORS NDIS ABOUT HELP CART Mobile: hamburger navigation, sticky header, cart quantity. 7. HOMEPAGE Create /. Hero: Headline: "Communication made easier." Subheading: "Practical communication tags designed for everyday moments at home, school and out and about." Buttons: SHOP COMMUNICATION SETS / BUILD YOUR OWN SET Best sellers: Everyday Communication Set — $39.95 AUD Regulation Set — $39.95 AUD Build Your Own Set — $49.95 AUD Create a prominent "Create a set that works for you" section. Trust cards: Australian business 3D printed in small batches Designed for everyday use Made with care School section: "Communication tools for classrooms" Buttons: VIEW SCHOOL PRODUCTS / BULK ORDERS NDIS section with factual, non-legal guidance. Reviews: Do not invent fake reviews. If none exist, display "Customer reviews coming soon." Email signup: "Stay in the loop" "Get product updates, new communication tags and special offers." 8. INITIAL PRODUCTS Product 1: Everyday Communication Set, $39.95 AUD. Tags: Drink, Eat, Toilet, Help, Break, Stop. Product 2: Regulation Set, $39.95 AUD. Tags: Break, Quiet, Help, Space, Calm, Finished. Product 3: Build Your Own Communication Set, $49.95 AUD. Customer selects six tags. 9. BUILD YOUR OWN CONFIGURATOR Create /products/build-your-own-communication-set. Step 1: Choose your 6 tags. Available tags: Drink, Eat, Toilet, Help, Break, Stop, Yes, No, More, Finished, Wait, Quiet, Space, Home, School, Pain, Water, Outside. Display each tag as a visual selectable card with icon placeholder, word and selected state. Show "0 of 6 selected". Prevent selecting more than six. Do not allow checkout unless exactly six are selected. Step 2: Choose attachment: O-ring, Keyring, Clip. Step 3: Choose colour: Black, White, Blue, Green, Yellow, Pink, Purple. Step 4: Summary showing six tags, attachment, colour, quantity and price. Add configuration as structured cart metadata. 10. INDIVIDUAL TAGS Create collection "Individual Communication Tags". Initial price $7.95 AUD. Allow tag, colour and attachment selection. Make extensible. 11. SHOP AND COLLECTIONS Create /shop with filters Category, Price, Product type; sorting Featured, Newest, Price low-high, Price high-low. Collections: /collections/communication-sets /collections/individual-tags /collections/regulation /collections/schools Data must come from Supabase. 12. PRODUCT PAGE Professional product page with image gallery, name, price, description, options, quantity, Add to Cart and Buy Now. Below: Description, What's Included, How It Works, Shipping, FAQ, Related Products. Consider sticky mobile Add to Cart. 13. IMAGE MANAGEMENT Use Supabase Storage. Products reference images from database. Support featured image, gallery images and alt text. Do not hard-code image URLs. 14. CART Create cart drawer and cart page. Show product, image, configuration, quantity, price, subtotal. Allow quantity changes/removal. Show subtotal, shipping and total. Checkout button. 15. STRIPE Use Stripe Checkout. Do not create a custom card form. Flow: Customer → Cart → Server validates cart → Server retrieves current product prices from Supabase → Server creates Stripe Checkout Session → Stripe hosted checkout → Payment → Stripe webhook → Supabase order. Never trust browser prices. Never expose STRIPE_SECRET_KEY. Verify webhook signatures. Do not mark an order paid merely because the customer reaches a success URL. 16. SUPABASE DATABASE Create: products product_variants tags collections product_collections orders order_items customers reviews newsletter_subscribers admin_profiles shipping_rates site_settings Products fields: id, name, slug, description, price, currency, featured, active, stock, created_at, updated_at. Tags fields: id, name, slug, description, icon, active, sort_order, created_at. Orders fields: id, order_number, stripe_checkout_session_id, stripe_payment_intent_id, customer_email, customer_name, shipping_address, subtotal, shipping, total, currency, payment_status, fulfilment_status, created_at, updated_at. Order items: id, order_id, product_id, product_name, quantity, unit_price, configuration, created_at. Configuration must store selected tags, colour and attachment. 17. ADMIN DASHBOARD Create /admin with authentication. Admin can: - View dashboard - View orders - Create/edit/archive products - Change prices and stock - Upload images - Manage tags - Manage collections - View customers - Manage reviews - Manage shipping - Manage settings Sidebar: Dashboard, Orders, Products, Tags, Collections, Customers, Reviews, Shipping, Settings. Dashboard cards: Orders today, Revenue, Products, Low stock, Recent orders. 18. ADMIN TAGS Admin can create, edit, deactivate and reorder tags. Build Your Own must automatically use active tags. Adding a new tag such as "Bus" through admin must make it available in the selector. 19. SHIPPING Initial Australian shipping: Standard $9.95 Free shipping over $100 Store values in Supabase and make them editable in Admin. Do not integrate Australia Post API in V1 unless credentials are provided. Design for future integration. 20. EMAIL Prepare transactional email using Resend or another reputable provider. Initial emails: order confirmation and order shipped. Use environment variables. 21. SEO Implement page titles, meta descriptions, Open Graph, canonical URLs, sitemap, robots.txt and appropriate product structured data. Do not create fake review ratings. 22. ACCESSIBILITY Target WCAG 2.2 AA where practical. Implement semantic HTML, keyboard navigation, visible focus states, accessible labels/forms/errors, good contrast, alt text and large touch targets. Tag configurator must be keyboard accessible. 23. MOBILE Mobile-first. Test 360px, 390px, 412px, 768px, 1024px and 1440px. Build-your-own configurator must work properly on phones. 24. SECURITY Use Supabase Row Level Security, server-side validation, secure authentication, Stripe webhook verification, input validation, no client-side secrets, no service-role key in browser and protected admin access. 25. ENVIRONMENT VARIABLES Create .env.example: NEXT_PUBLIC_SUPABASE_URL NEXT_PUBLIC_SUPABASE_ANON_KEY SUPABASE_SERVICE_ROLE_KEY STRIPE_SECRET_KEY STRIPE_WEBHOOK_SECRET NEXT_PUBLIC_SITE_URL RESEND_API_KEY Never commit actual credentials. 26. VERCEL Prepare deployment for Vercel. README must explain: 1. Create Supabase project 2. Configure database 3. Configure storage 4. Create Stripe account 5. Configure Stripe test mode 6. Add environment variables 7. Connect GitHub 8. Deploy to Vercel 9. Configure custom domain 10. Configure Stripe webhook 11. Create first admin account 27. DOMAIN Support a .com.au domain. Do not purchase it. Document how to connect the domain to Vercel. 28. LEGAL PAGES Create: /privacy /terms /shipping /returns /contact /faq /ndis Use clearly marked placeholder legal content where professional legal review is required. Do not invent legal guarantees. 29. ABOUT Create an original About page positioning the company as an Australian small business creating practical communication tools. Include mission, how products are made, quality approach and contact. No medical claims. 30. CONTACT Create fields: Name Email Order number Message Validate server-side. Prepare spam protection. 31. FAQ Initial questions: What are communication tags? How do I choose the right tags? Can I customise a set? How are the tags made? How should I clean them? How long does shipping take? Can schools order in bulk? How can I purchase using NDIS funding? Answers must be factual and avoid unsupported medical or funding advice. 32. DATABASE SEED Create seed data for: 3 products 18 tags 4 collections Shipping rates Site settings Use placeholder product images and clearly identify them. Do not use competitor images. 33. GITHUB Create .gitignore and README.md and .env.example. Never commit .env, .env.local, node_modules, credentials or secret keys. 34. ERROR HANDLING Create user-friendly states for payment failure, unavailable products, stock issues, invalid configuration, network errors and checkout errors. Do not expose stack traces to customers. 35. ANALYTICS Prepare for Google Analytics, Google Search Console and Meta Pixel. Do not add tracking requiring consent without appropriate consent handling. Keep analytics modular. 36. PERFORMANCE Optimize images, lazy loading, minimal JavaScript, caching where appropriate and Core Web Vitals. Avoid unnecessary animation. 37. ORIGINAL DESIGN The site should feel premium, friendly, accessible, clean and simple. Product photography should be the visual focus. 38. DEVELOPMENT PROCESS Do not simply provide instructions. Actually create the application. First: 1. Inspect repository 2. Create project architecture 3. Configure dependencies 4. Create Supabase schema 5. Create Supabase migrations 6. Create seed data 7. Create design system 8. Create header/footer 9. Create homepage 10. Create catalogue 11. Create product pages 12. Create Build Your Own configurator 13. Create cart 14. Create Stripe Checkout 15. Create Stripe webhook 16. Create order system 17. Create authentication 18. Create admin dashboard 19. Create shipping settings 20. Create SEO 21. Test 22. Fix errors 23. Prepare Vercel deployment After each major stage run TypeScript checks, lint and tests where available. Fix errors before proceeding. 39. DO NOT ASK UNNECESSARY QUESTIONS Use sensible defaults. Do not stop because photography is unavailable. Use placeholders. Use "Made 4 Me" temporarily and make it easy to change. Do not ask for Stripe production credentials; use Stripe TEST MODE. Do not deploy to production without explicit approval. 40. ACCEPTANCE TEST Verify: - Homepage works - Navigation works - Mobile menu works - Shop works - Collections work - Product pages work - Product images work - Build Your Own works - Exactly six tags can be selected - Seven tags cannot be selected - Attachment selection works - Colour selection works - Cart works - Cart quantity works - Cart removal works - Stripe TEST MODE checkout works - Stripe webhook works - Orders save to Supabase - Admin login works - Admin product creation/editing works - Admin tag creation works - New admin tag appears in Build Your Own - Admin order management works - Shipping settings work - SEO metadata exists - Sitemap works - robots.txt works - Mobile layout works - Accessibility basics work - TypeScript passes - Lint passes - Production build passes - No secrets are committed - No competitor copyrighted assets were copied 41. FINAL OUTPUT When complete, provide: 1. Summary of what was built 2. Project structure 3. Supabase tables 4. Environment variables 5. Local development instructions 6. Supabase setup instructions 7. Stripe setup instructions 8. Vercel deployment instructions 9. How to create first admin user 10. How to add products 11. How to add communication tags 12. How to change prices 13. How to change shipping 14. Remaining V1 limitations 15. Recommended V2 features IMPORTANT: Do not merely tell me how to build it. Build the actual working application. Start now by inspecting the repository and then implement V1.
Made For Me is dedicated to improving interactions for autistic and ADHD individuals through personalized communication tags. Our innovative tags facilitate understanding and connection between children and others, providing them with a voice in conversations. Based in Australia, we strive to bridge communication gaps to foster a more inclusive environment.
Claude Code Master Build Prompt — V1 Australian Communication Tag E-Commerce Store Copy the prompt below into Claude Code to build the V1 website. PROJECT: Australian Communication Tags E-Commerce Website — V1 You are the lead full-stack developer, UI/UX designer, database architect and DevOps engineer. Build a complete, production-ready e-commerce website for an Australian business selling 3D-printed communication tags. The website should be inspired by the general customer experience and product-store structure of established communication-tag businesses such as Talkies Cards, but it MUST be an original website. Do not copy Talkies Cards' branding, logo, images, product photography, product descriptions, exact product designs, exact page layouts, CSS, icons or illustrations. Use only general e-commerce concepts as inspiration. The finished website must look like a professional independent Australian brand. 1. BUSINESS Working brand name: "Made 4 Me" Make the brand name easy to replace later. Business: Australian business selling practical 3D-printed communication tags and communication aids. Target customers: - Parents - Families - Teachers - Schools - Education assistants - Support workers - Disability-support customers - NDIS customers - People who benefit from visual communication tools Brand positioning: "Communication made easier." Brand personality: - Friendly - Modern - Professional - Accessible - Practical - Australian - High quality Do not make medical claims. Do not claim products diagnose, treat, prevent or cure any condition. Do not make unsupported claims such as "child-proof", "waterproof", "non-toxic" or "therapeutic". 2. CORE TECHNOLOGY Use: - Next.js - TypeScript - Tailwind CSS - Supabase - Stripe Checkout - Vercel - GitHub Use the current stable versions. Use App Router. Use server-side functionality where appropriate. Do not use unnecessary libraries. Keep the application modular and maintainable. 3. HOSTING ARCHITECTURE Customer → Vercel → Next.js → Supabase → Stripe Checkout → Customer payment → Business bank account Supabase: PostgreSQL database, product data, tags, collections, orders, customers, reviews, admin data and storage where appropriate. Stripe: Checkout and payment processing. Vercel: Hosting, deployment and HTTPS. Do not build your own credit-card payment system. 4. PROJECT STRUCTURE Create: /app /components /lib /types /public /styles /supabase /scripts Use reusable components: Header, MobileNavigation, Footer, ProductCard, ProductGrid, ProductGallery, ProductOptions, TagSelector, ColourSelector, AttachmentSelector, QuantitySelector, AddToCartButton, CartDrawer, CartPage, CheckoutButton, ReviewSection, FAQSection, NewsletterSignup, TrustBadges, SchoolCTA, NDISCTA, AdminSidebar, AdminHeader, AdminProductForm, AdminOrderTable, AdminTagManager. 5. BRAND DESIGN Create an original visual identity. Do not imitate Talkies' exact design. Colours: Background #FFFFFF Primary text #1F2937 Secondary text #6B7280 Primary brand #2563EB Secondary accent #F59E0B Light background #F8FAFC Border #E5E7EB Success #16A34A Error #DC2626 Use CSS variables/design tokens so colours can be changed globally. Typography: Inter or another clean modern sans-serif. Use large product photography, clean cards, rounded corners, generous spacing, strong CTA buttons, clear prices, excellent mobile layout and minimal animation. 6. NAVIGATION Desktop: LOGO SHOP - Communication Sets - Individual Tags - Regulation & Sensory - Build Your Own SCHOOLS & EDUCATORS NDIS ABOUT HELP CART Mobile: hamburger navigation, sticky header, cart quantity. 7. HOMEPAGE Create /. Hero: Headline: "Communication made easier." Subheading: "Practical communication tags designed for everyday moments at home, school and out and about." Buttons: SHOP COMMUNICATION SETS / BUILD YOUR OWN SET Best sellers: Everyday Communication Set — $39.95 AUD Regulation Set — $39.95 AUD Build Your Own Set — $49.95 AUD Create a prominent "Create a set that works for you" section. Trust cards: Australian business 3D printed in small batches Designed for everyday use Made with care School section: "Communication tools for classrooms" Buttons: VIEW SCHOOL PRODUCTS / BULK ORDERS NDIS section with factual, non-legal guidance. Reviews: Do not invent fake reviews. If none exist, display "Customer reviews coming soon." Email signup: "Stay in the loop" "Get product updates, new communication tags and special offers." 8. INITIAL PRODUCTS Product 1: Everyday Communication Set, $39.95 AUD. Tags: Drink, Eat, Toilet, Help, Break, Stop. Product 2: Regulation Set, $39.95 AUD. Tags: Break, Quiet, Help, Space, Calm, Finished. Product 3: Build Your Own Communication Set, $49.95 AUD. Customer selects six tags. 9. BUILD YOUR OWN CONFIGURATOR Create /products/build-your-own-communication-set. Step 1: Choose your 6 tags. Available tags: Drink, Eat, Toilet, Help, Break, Stop, Yes, No, More, Finished, Wait, Quiet, Space, Home, School, Pain, Water, Outside. Display each tag as a visual selectable card with icon placeholder, word and selected state. Show "0 of 6 selected". Prevent selecting more than six. Do not allow checkout unless exactly six are selected. Step 2: Choose attachment: O-ring, Keyring, Clip. Step 3: Choose colour: Black, White, Blue, Green, Yellow, Pink, Purple. Step 4: Summary showing six tags, attachment, colour, quantity and price. Add configuration as structured cart metadata. 10. INDIVIDUAL TAGS Create collection "Individual Communication Tags". Initial price $7.95 AUD. Allow tag, colour and attachment selection. Make extensible. 11. SHOP AND COLLECTIONS Create /shop with filters Category, Price, Product type; sorting Featured, Newest, Price low-high, Price high-low. Collections: /collections/communication-sets /collections/individual-tags /collections/regulation /collections/schools Data must come from Supabase. 12. PRODUCT PAGE Professional product page with image gallery, name, price, description, options, quantity, Add to Cart and Buy Now. Below: Description, What's Included, How It Works, Shipping, FAQ, Related Products. Consider sticky mobile Add to Cart. 13. IMAGE MANAGEMENT Use Supabase Storage. Products reference images from database. Support featured image, gallery images and alt text. Do not hard-code image URLs. 14. CART Create cart drawer and cart page. Show product, image, configuration, quantity, price, subtotal. Allow quantity changes/removal. Show subtotal, shipping and total. Checkout button. 15. STRIPE Use Stripe Checkout. Do not create a custom card form. Flow: Customer → Cart → Server validates cart → Server retrieves current product prices from Supabase → Server creates Stripe Checkout Session → Stripe hosted checkout → Payment → Stripe webhook → Supabase order. Never trust browser prices. Never expose STRIPE_SECRET_KEY. Verify webhook signatures. Do not mark an order paid merely because the customer reaches a success URL. 16. SUPABASE DATABASE Create: products product_variants tags collections product_collections orders order_items customers reviews newsletter_subscribers admin_profiles shipping_rates site_settings Products fields: id, name, slug, description, price, currency, featured, active, stock, created_at, updated_at. Tags fields: id, name, slug, description, icon, active, sort_order, created_at. Orders fields: id, order_number, stripe_checkout_session_id, stripe_payment_intent_id, customer_email, customer_name, shipping_address, subtotal, shipping, total, currency, payment_status, fulfilment_status, created_at, updated_at. Order items: id, order_id, product_id, product_name, quantity, unit_price, configuration, created_at. Configuration must store selected tags, colour and attachment. 17. ADMIN DASHBOARD Create /admin with authentication. Admin can: - View dashboard - View orders - Create/edit/archive products - Change prices and stock - Upload images - Manage tags - Manage collections - View customers - Manage reviews - Manage shipping - Manage settings Sidebar: Dashboard, Orders, Products, Tags, Collections, Customers, Reviews, Shipping, Settings. Dashboard cards: Orders today, Revenue, Products, Low stock, Recent orders. 18. ADMIN TAGS Admin can create, edit, deactivate and reorder tags. Build Your Own must automatically use active tags. Adding a new tag such as "Bus" through admin must make it available in the selector. 19. SHIPPING Initial Australian shipping: Standard $9.95 Free shipping over $100 Store values in Supabase and make them editable in Admin. Do not integrate Australia Post API in V1 unless credentials are provided. Design for future integration. 20. EMAIL Prepare transactional email using Resend or another reputable provider. Initial emails: order confirmation and order shipped. Use environment variables. 21. SEO Implement page titles, meta descriptions, Open Graph, canonical URLs, sitemap, robots.txt and appropriate product structured data. Do not create fake review ratings. 22. ACCESSIBILITY Target WCAG 2.2 AA where practical. Implement semantic HTML, keyboard navigation, visible focus states, accessible labels/forms/errors, good contrast, alt text and large touch targets. Tag configurator must be keyboard accessible. 23. MOBILE Mobile-first. Test 360px, 390px, 412px, 768px, 1024px and 1440px. Build-your-own configurator must work properly on phones. 24. SECURITY Use Supabase Row Level Security, server-side validation, secure authentication, Stripe webhook verification, input validation, no client-side secrets, no service-role key in browser and protected admin access. 25. ENVIRONMENT VARIABLES Create .env.example: NEXT_PUBLIC_SUPABASE_URL NEXT_PUBLIC_SUPABASE_ANON_KEY SUPABASE_SERVICE_ROLE_KEY STRIPE_SECRET_KEY STRIPE_WEBHOOK_SECRET NEXT_PUBLIC_SITE_URL RESEND_API_KEY Never commit actual credentials. 26. VERCEL Prepare deployment for Vercel. README must explain: 1. Create Supabase project 2. Configure database 3. Configure storage 4. Create Stripe account 5. Configure Stripe test mode 6. Add environment variables 7. Connect GitHub 8. Deploy to Vercel 9. Configure custom domain 10. Configure Stripe webhook 11. Create first admin account 27. DOMAIN Support a .com.au domain. Do not purchase it. Document how to connect the domain to Vercel. 28. LEGAL PAGES Create: /privacy /terms /shipping /returns /contact /faq /ndis Use clearly marked placeholder legal content where professional legal review is required. Do not invent legal guarantees. 29. ABOUT Create an original About page positioning the company as an Australian small business creating practical communication tools. Include mission, how products are made, quality approach and contact. No medical claims. 30. CONTACT Create fields: Name Email Order number Message Validate server-side. Prepare spam protection. 31. FAQ Initial questions: What are communication tags? How do I choose the right tags? Can I customise a set? How are the tags made? How should I clean them? How long does shipping take? Can schools order in bulk? How can I purchase using NDIS funding? Answers must be factual and avoid unsupported medical or funding advice. 32. DATABASE SEED Create seed data for: 3 products 18 tags 4 collections Shipping rates Site settings Use placeholder product images and clearly identify them. Do not use competitor images. 33. GITHUB Create .gitignore and README.md and .env.example. Never commit .env, .env.local, node_modules, credentials or secret keys. 34. ERROR HANDLING Create user-friendly states for payment failure, unavailable products, stock issues, invalid configuration, network errors and checkout errors. Do not expose stack traces to customers. 35. ANALYTICS Prepare for Google Analytics, Google Search Console and Meta Pixel. Do not add tracking requiring consent without appropriate consent handling. Keep analytics modular. 36. PERFORMANCE Optimize images, lazy loading, minimal JavaScript, caching where appropriate and Core Web Vitals. Avoid unnecessary animation. 37. ORIGINAL DESIGN The site should feel premium, friendly, accessible, clean and simple. Product photography should be the visual focus. 38. DEVELOPMENT PROCESS Do not simply provide instructions. Actually create the application. First: 1. Inspect repository 2. Create project architecture 3. Configure dependencies 4. Create Supabase schema 5. Create Supabase migrations 6. Create seed data 7. Create design system 8. Create header/footer 9. Create homepage 10. Create catalogue 11. Create product pages 12. Create Build Your Own configurator 13. Create cart 14. Create Stripe Checkout 15. Create Stripe webhook 16. Create order system 17. Create authentication 18. Create admin dashboard 19. Create shipping settings 20. Create SEO 21. Test 22. Fix errors 23. Prepare Vercel deployment After each major stage run TypeScript checks, lint and tests where available. Fix errors before proceeding. 39. DO NOT ASK UNNECESSARY QUESTIONS Use sensible defaults. Do not stop because photography is unavailable. Use placeholders. Use "Made 4 Me" temporarily and make it easy to change. Do not ask for Stripe production credentials; use Stripe TEST MODE. Do not deploy to production without explicit approval. 40. ACCEPTANCE TEST Verify: - Homepage works - Navigation works - Mobile menu works - Shop works - Collections work - Product pages work - Product images work - Build Your Own works - Exactly six tags can be selected - Seven tags cannot be selected - Attachment selection works - Colour selection works - Cart works - Cart quantity works - Cart removal works - Stripe TEST MODE checkout works - Stripe webhook works - Orders save to Supabase - Admin login works - Admin product creation/editing works - Admin tag creation works - New admin tag appears in Build Your Own - Admin order management works - Shipping settings work - SEO metadata exists - Sitemap works - robots.txt works - Mobile layout works - Accessibility basics work - TypeScript passes - Lint passes - Production build passes - No secrets are committed - No competitor copyrighted assets were copied 41. FINAL OUTPUT When complete, provide: 1. Summary of what was built 2. Project structure 3. Supabase tables 4. Environment variables 5. Local development instructions 6. Supabase setup instructions 7. Stripe setup instructions 8. Vercel deployment instructions 9. How to create first admin user 10. How to add products 11. How to add communication tags 12. How to change prices 13. How to change shipping 14. Remaining V1 limitations 15. Recommended V2 features IMPORTANT: Do not merely tell me how to build it. Build the actual working application. Start now by inspecting the repository and then implement V1.