lovable-vibe-code-auditlisted

# Lovable Vibe-Code Audit Lovable (and similar AI builders) all draw from the same starter patterns, component defaults, and default brand colors. A project that skips a deliberate polish pass reads as obviously AI-generated to anyone who's seen a few of these sites — which undermines client trust even when the underlying functionality is solid. This skill is the checklist for catching those tells before a client or the public sees them. Every item below should be treated as **found → flag it → tell the user it should be removed/fixed**, not silently noted. The goal of the audit is a punch list, not a vibe check you keep to yourself. ## How to run the audit 1. **Fetch the live page**, not just the Lovable preview iframe — view-source or fetch the actual rendered HTML for `<title>`, favicon, and meta tags. 2. **Capture screenshots at three widths** — desktop (~1440px), tablet (~768px), mobile (~375px). Most responsiveness breaks only show up at the actual breakpoint, not a resized desktop browser window. 3. **Click every footer link** — Terms, Privacy, credits/attribution — confirm each lands on a real page with real content, not `#`, a 404, or a copy of the homepage. 4. **Read the hero and section copy out loud** — AI-formula phrasing is easier to hear than to spot by eye. 5. **Report findings grouped by category** (below), each with: what you saw, where (page/section), and what to change it to. ## Checklist ### Browser chrome / site identity - Default favicon (Vite/Rea