← Reddit

How do you stop AI-built websites from looking AI-built?

Reddit · Fantastic-Glass-5865 · June 5, 2026
A developer encountered persistent generic "polished AI" design aesthetics when building a tourism website using AI coding tools like Lovable and Codex, characterized by clean layouts with cards and rounded corners but lacking personality. The creator initially pursued a unique scrapbook-like visual style but found the AI tools unable to recreate detailed mockups with the desired aesthetic. After pivoting to a modern editorial direction, the developer remained uncertain whether the final design successfully avoided the typical appearance of AI-built websites.

Detailed Analysis

A developer building a local tourism and smart planning site for Banff, Canada has surfaced a tension that is becoming increasingly common among builders who use AI coding tools: the tendency for AI-assisted development to converge on a recognizable, homogenous visual aesthetic. The post, shared on Reddit's r/ClaudeAI community, describes using a stack of tools including Claude Code, Lovable, and Codex to construct the site banff.tips, only to find that despite considerable effort, the output consistently drifted toward what the author calls the "AI website look" — characterized by clean card layouts, generous spacing, rounded corners, and a polished but personality-free appearance. The developer had originally envisioned something more distinctive, likening the target aesthetic to a scrapbook or local field guide, and even used ChatGPT image generation to mock up that vision, only to find that translating it into functional code through AI tools proved elusive.

The core problem the developer identifies is that AI coding assistants are highly capable at producing functional, clean interfaces, but the design taste embedded in their outputs reflects training on broad datasets of contemporary web design — which means they tend toward competent genericism rather than distinctive character. Attempts to override this through detailed prompting, screenshot references, design documentation, and mockup analysis failed to fully break the AI's gravitational pull toward its default aesthetic sensibility. This is a meaningful distinction: the tools succeeded at their stated purpose of building a usable, clean website, but fell short of a higher-order creative goal that required capturing a specific, idiosyncratic visual identity. The developer eventually settled for a "modern editorial direction," acknowledging it as a practical compromise rather than the original vision.

This tension speaks to a broader structural limitation in current AI-assisted creative tooling. Large language models and code generation systems like Claude Code are optimized for correctness, coherence, and generalizability — properties that make them excellent at producing code that works but less suited to encoding the kind of opinionated, contextually rooted design decisions that give a project genuine character. Design systems in AI tools reflect aggregated consensus from thousands of existing sites, which means the output regresses toward the mean of contemporary web aesthetics. Overriding this requires either human designers inserting deliberate friction into the workflow — manually crafting components, enforcing non-standard style choices, or building custom design tokens before engaging AI tools — or developers with sufficient front-end fluency to fight the AI's defaults at a granular level.

The Reddit post also reflects a maturation in how practitioners are thinking about AI-assisted development workflows. Early discourse around tools like Lovable and Claude Code focused heavily on speed and accessibility — the promise that non-developers could build functional products quickly. The developer's account suggests that as these tools become more widely adopted, a second-order problem is emerging: how to use them to build things that don't look like they were built by everyone else using the same tools. This is the aesthetic equivalent of the SEO content problem that plagued AI-generated text — outputs that are technically correct but recognizably machine-produced in their patterns and defaults. The question of whether to lock in a design system before building, design pages manually first, or use specialized agents for design tasks is one that the broader AI-assisted development community has yet to resolve with any consistent methodology.

The Banff tips project ultimately illustrates the current boundary of what AI coding tools can reliably deliver versus what requires human creative judgment. Claude Code and similar tools have substantially lowered the floor for what an individual developer can build, enabling rapid iteration and functional complexity that would have taken far longer through traditional means. But the ceiling — meaning the capacity to produce work with a genuinely distinctive aesthetic identity — still appears to require deliberate human intervention to break free from the AI's embedded design conventions. As these tools continue to evolve, the degree to which they can accommodate idiosyncratic creative direction, rather than smoothing it out in favor of polished genericism, will be a meaningful differentiator.

Read original article →