TechnicalCollectible prompt

Strip the AI-generated look from your site

Find the tells that make a site look vibe-coded, then fix each one with a specific design decision.

Lovablev0Cursor

Curated by Nvoka

0 saves · 3 views

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Strip the AI-generated look from your site

Act as a senior product designer who cleans up AI-built websites. This is the site for {{business_name}}, a {{business_type}}, for {{target_audience}}. Before changing anything, read the existing styles, components and pages, and tell me what you found. Step 1, audit. Go page by page and flag every tell of a vibe-coded site, with where it appears: - a purple-to-blue gradient on buttons, text or backgrounds - glass cards over blurred blobs; glows and shadows on everything - every section a centered heading plus three identical icon cards - icons in gradient circles, emoji as bullets - one font at one weight doing every job; gray text below 4.5:1 contrast - the same large radius on everything - a full-screen centered hero that says nothing specific - filler copy: "Unlock the power of", "Elevate", "Seamless", "Revolutionize" - testimonials, logos or stats with no real source - fade-ins on every element, pulsing dots, floating text Step 2, decide. Replace each tell with one specific decision, not a softer version of the same thing. For example: one solid brand accent with a darker hover; a heading and body pairing with three weights; layouts that vary by section (split, list, table, one wide image) based on the content; a 4px spacing scale; radius 6px on inputs, 12px on cards, 999px only on tags; motion limited to hover, focus and one hero reveal under 400ms, with reduced motion respected. Step 3, apply. Keep the framework, components, routes and content structure. Put the decisions into shared tokens, then fix each page. Mark fake proof for removal instead of inventing replacements. Stay at WCAG 2.2 AA: visible focus, 44px targets, no horizontal scroll at 360px. Finish with a table: the tell, where it was, what replaced it and why. Ask me up to 2 questions first, only if our brand colors or fonts are unclear.
0 saves · 3 viewsnvoka.com/library/nvoka-strip-the-ai-generated-look-from-your-siteScan to open
Technical

Strip the AI-generated look from your site

Find the tells that make a site look vibe-coded, then fix each one with a specific design decision.

Nvoka logo

Curated by Nvoka

3 viewsLovablev0CursorClaude Code
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 3 filled

Your prompt

Act as a senior product designer who cleans up AI-built websites. This is the site for {{business_name}}, a {{business_type}}, for {{target_audience}}. Before changing anything, read the existing styles, components and pages, and tell me what you found. Step 1, audit. Go page by page and flag every tell of a vibe-coded site, with where it appears: - a purple-to-blue gradient on buttons, text or backgrounds - glass cards over blurred blobs; glows and shadows on everything - every section a centered heading plus three identical icon cards - icons in gradient circles, emoji as bullets - one font at one weight doing every job; gray text below 4.5:1 contrast - the same large radius on everything - a full-screen centered hero that says nothing specific - filler copy: "Unlock the power of", "Elevate", "Seamless", "Revolutionize" - testimonials, logos or stats with no real source - fade-ins on every element, pulsing dots, floating text Step 2, decide. Replace each tell with one specific decision, not a softer version of the same thing. For example: one solid brand accent with a darker hover; a heading and body pairing with three weights; layouts that vary by section (split, list, table, one wide image) based on the content; a 4px spacing scale; radius 6px on inputs, 12px on cards, 999px only on tags; motion limited to hover, focus and one hero reveal under 400ms, with reduced motion respected. Step 3, apply. Keep the framework, components, routes and content structure. Put the decisions into shared tokens, then fix each page. Mark fake proof for removal instead of inventing replacements. Stay at WCAG 2.2 AA: visible focus, 44px targets, no horizontal scroll at 360px. Finish with a table: the tell, where it was, what replaced it and why. Ask me up to 2 questions first, only if our brand colors or fonts are unclear.
See all