Act as a senior product designer who also codes. The site for {{business_name}} started from a starter template or an AI builder's first draft, and it still looks like one. Make it ours. The look: {{visual_style}}. Fonts: {{brand_fonts}}. Colors: {{brand_colors}}. Keep the framework and routes; change what makes it generic. 1. Inventory the leftovers. Read the project and list: placeholder and lorem ipsum text, demo pages and unused routes, sample images and avatars, the template's logo, favicon and share image, default page titles, dummy testimonials, logos and stats, unused components and packages, demo API keys or analytics IDs, and template comments or README sections. 2. Remove or replace each one, and confirm nothing links to deleted pages. 3. Replace the template's look with tokens: our fonts (two families at most, a scale from a 16px body, tighter letter-spacing on big headings), color roles with 4.5:1 text contrast, an 8px spacing scale, and our own radius and shadow choices. Apply them through the existing styling system, not one-off overrides. 4. Break the template's layout habits: the full-screen centered hero with nothing in it, every section as a heading plus three icon cards, gradient blobs, glass cards and the same heavy rounding on everything. Give each key page a layout that fits its content. 5. Make the content real: our own headline, photos, proof we can back up, and contact details. Mark what I need to supply instead of inventing it. 6. Housekeeping: our own favicon set, a 1200 by 630px share image, page titles, a 404 page, and license notes for any fonts or images kept from the template. Return the change list with a reason for each, and the items I still need to provide.