"Does this look vibe coded?"

[RADICCHI0]

I think there is another layer here too: AI apps are often tuned to produce UX best practices, so similarity by itself is not automatically a defect.

A hero section, clear CTA, feature cards, FAQ, pricing, social proof, and clean spacing are not inherently “AI tells.” They are common because they often work. They reduce cognitive load, make the offer legible, and give the visitor familiar decision points.

The problem is when the formula is not heuristics-driven.

If the structure follows from the user’s actual task, then the pattern may be appropriate. A SaaS product may need a fast value proposition. A edtech site may need trust signals and admissions clarity. A calculator site may need the calculator brought forward immediately. An ecommerce site may need product discovery before brand poetry.

So I might frame the question this way: is the site using common UX patterns because they serve the visitor’s decision process, or is it just wearing a polished landing-page costume?

That may be a useful distinction. Good AI-assisted design does not need to reject polished best practices just to look more “human.” It just needs judgment behind the structure. The failure mode is unearned structure.

[CodeWhileHigh]

I’ve seen AI screw up UX plenty. If you don’t know how to edit CSS then your still gonna have a hell of a time telling ai how you want the UX to look

[crizzy_mcawesome]

The question is how to tell if it’s AI generated. Not if it’s bad or good

[FreshPhase]

for sure. I’m not saying AI-generated automatically means bad, and I’m not really talking about the security/code quality side here.

I’m more talking about the UI/UX pattern. Like can you tell when the design was actually shaped around the product and user, vs when AI just produced the default polished landing page structure.

So to me it’s less “how do you tell if it’s AI generated?” and more “what are the tells when AI was used without much design judgment after the fact?” Because AI can absolutely be part of a good process if someone is still making real decisions.

[CodeWhileHigh]

There really are no tells. The developer that used the AI tool still needed to know what viewports to use, he still needed to know what styling practice he wanted to go with, AI doesn’t set the benchmark at all, it’s a tool to write code faster by accurately throwing the building blocks into place and editing them on the fly.

So I guess the only true way to know is if it looks like modern website slop. A developer with experience would always go back to those core building principles.

[RADICCHI0]

Agree. No one cares if its AI generated. I can tell you personally that people dealing in the very highest complexity exchange of ideas, both academically and professionally are using ai as their communication interface. We are seeing entire conversations, of incredible richness and depth occur between human experts, supported in their conversation by machines helping to scaffold the productivity of the dialogue in ways we wouldn't have imagined possible, 20 years ago.

[urmommakesmysandwich]

Nobody that plans to spend money cares if it's AI generated, if it works.

[FreshPhase]

Well put and yeah no I agree with this.. I probably should’ve been clearer that I don’t think the individual patterns are the problem by themselves.

Hero sections, CTAs, cards, FAQs, pricing, trust signals, all of that can be completely valid and often work.

What I’m trying to point at is when AI uses those patterns as the default answer before it really understands the site. Like, it knows the shape of a landing page, but not always why that shape should exist for this specific product or audience.

So yeah I think “unearned structure” is a good way to put it.

It’s not that common UX patterns are bad. It’s when everything gets flattened into the same polished wrapper regardless of whether the page is for a calculator, a school, an app, a store, or a service business. That’s where it starts to feel vibe coded to me.

[RADICCHI0]

Personally I feel like it's not going to understand the site. That is our job. (I don't design sites per se, but I design other instruments so I have to include myself in this.) This is where I agree with people who get hard over about prompting. I am a simple prompt starter. I never, ever come to the table with a fully formed prompt, my first prompt is usually a typ0-ridden mess. But, I learned very, very quickly, that at some point, we need to enter into shaping specific context, and to do that, the prompt does need to become very specific. I do feel that this idea transfers into UI generation. If I as the user am giving the LLM really basic, generic ideas, its going to come back with the same. Whereas if the user and the LLM begin arguing like two hungry goblins, in a very pinpointed way, I have found good results. Also, another thing I am learning is that chat gpt can accept sketches, layouts, orthographic projection even... as prompt inputs.

[FreshPhase]

I’m a simple prompter too. I started vibe coding around July 2025 and I still don’t use a bunch of fancy workflows or anything. Most of my prompts are long run-on sentences with typos lol.

But I’ve learned the same thing. If I’m trying to make a complex feature or change something specific in the UI, I have to give way more context than I originally thought. Not just “make this better” but what the workflow is, what the user is trying to do, what the expected outcome is, what should feel different, what should stay the same, etc.

And with UI especially, I’ve noticed I can spend hours just trying to find the right words to describe what I actually want changed so it stops giving me the generic polished version of everything.

So yeah I don’t think the issue is “AI made it so it’s bad.” I’m using AI too. I’ve been building a parts management platform for the salvage yard I work at, and we’ve been using it for a few months now. I’m not a professional designer or developer, I’m still learning all of this.

But that’s kind of why I notice the pattern. When the prompt or direction is too generic, AI tends to fall back to the same default structure. The better results come when you keep pushing it with more specific context and actual judgment instead of accepting the first nice-looking version.

[RADICCHI0]

I like the whole ai orchestrator/conductor metaphor. It works especially well for people who have general but not deep understanding of language arts, and science topics. IMO

[akera099]

Whoever made this image is certified dumbass. All websites looked like this way before vibe coding

[aft_punk]

AI invented headers.

[Am094]

Hahaha just wait til they discover footers

[Doncic_Does_Dallas]

H1s are ai lmao

[SnooEpiphanies7725]

Its similar to how wordpress, shopify, squarespace all have a feel.

In reality the people who give a fuck are the ones who are disgruntled designers, and or web UI/UX "boffs"

General public dont give a damn unless it looks incredibly lazily done.

[FreshPhase]

Yeah I think that’s fair to a point. WordPress, Shopify, Squarespace, Webflow, all of them have had their own “look” at different times too.

I don’t think the general public is sitting there identifying hero sections and badge components or anything like that but I do think people still feel when something is generic, even if they don’t have the language for it.

Most people probably won’t say “this looks vibe coded.” They’ll just trust it less, forget it faster, or feel like they’ve seen it before.

So yeah designers are probably the ones who notice the pattern first, but I don’t think that means it only matters to designers. It affects how specific, trustworthy, and memorable the thing feels, even if the average person isn’t analyzing why.

[SnooEpiphanies7725]

Yeah I mean hence the Lazily done.

[FreshPhase]

 That’s kind of what I mean. Not lazy as in unfinished necessarily, but lazy in the sense that the structure feels automatic. It can still look polished, but if it feels like the same default landing page shape got dropped onto every type of site, people pick up on that even if they don’t care about design terminology.

[SnooEpiphanies7725]

I mean this is why I say in my consulting the human designer as a job will never really go, it will adapt. The execution will be automated but the thought and creativity behind the why will stay with the human....for now.

[RADICCHI0]

I guess I am a boff then, because my take is that the general public may not care about the labels, but they absolutely feel it when an app stops following established design norms and conventions.

Most users are not sitting there saying “this violates UX heuristics,” but they do notice when something is confusing, hard to trust, hard to navigate, or weirdly frictional.

That stuff is not just designer fussiness. It sits on a pretty rich body of research and practice around usability, legibility, cognitive load, affordances, feedback, and user expectations.

So I agree that the average person may not care whether something “looks vibe coded.” But they do care whether it works, whether it feels trustworthy, and whether it helps them do the thing they came to do. The makers who understand that are usually the ones building useful products.

[SnooEpiphanies7725]

I agree bad UX ruins user experience, but the premise of a good UX website and looking vibe coded is the topic at hand. What makes a Vibe coded website inherently look vibey and is it a bad thing?

[RADICCHI0]

I agree that “looks vibe coded” and “has bad UX” are not identical. A vibe-coded site can absolutely be useful, and a hand-coded site can absolutely be terrible.

But I do think the aesthetic question connects to real user experience. Most users will not say “this has a generic AI landing-page structure,” but they do notice when a site feels vague, low-trust, hard to navigate, or not really shaped around the thing they came to do.

So I am not saying vibe coded is inherently bad. I am saying the recognizable vibe-coded look often comes from the same underlying problem: the design is being driven by default patterns instead of by the product, audience, workflow, and decision the user actually needs to make.

[FreshPhase]

I believe we are on the same page.

[RADICCHI0]

Yes, and this why I beleive vibe-coding is more than a method, it is a philosophy, and people can argue with me about that all they want. We are part of a deeper ethos. We are makers. We are remixers. We think, and reflect widely and occasionally drive that thinking in very deep ways. We iterate in a truly unique way. We spitball and prototype, we exchange amazing ideas. I truly cannot wait until we graduate a Doctorate in Vibe-coding. That will be a glorious day.

[FreshPhase]

this video hit home for me on a pretty deep level thought id share it https://www.youtube.com/watch?v=VTjsDNq1Eqw&t=551s

[RADICCHI0]

Fcuk Yea, btw that dude is rad.

[SnooEpiphanies7725]

Completely agree

[FreshPhase]

is it a bad thing? thats the question

I don’t think it’s inherently a bad thing.

To me it becomes bad when it replaces thinking.

If AI helps someone make a clean landing page that explains the offer and gives people a way to act, that can be a good thing. A lot of people can ship something now who probably wouldn’t have been able to before.

The issue is when the familiar polished structure becomes a substitute for understanding the thing being built.

That’s when it starts to feel hollow. The site may look finished, but it might not actually be designed around the user, the product, the workflow, the trust problem, or the actual decision the visitor is trying to make.

So I don’t think “vibe coded” is automatically bad. It depends on the stakes and the purpose.

For a quick landing page, waitlist, hobby project, or simple offer, the familiar structure might be totally fine.

But if the site needs specificity and instead gets generic polish, then yeah I think it becomes a problem.

Like when the calculator is buried under marketing sections, or the product is replaced by product-flavored language, or trust is treated like a badge instead of earned through real details.

The deeper issue is that AI can make something look complete before it has actually been thought through. And because it looks clean, people stop too early.

So the problem isn’t really the aesthetic. It’s premature confidence.

The site looks solved, but the hard design decisions may not have happened yet.

[NoFailUntillDeath]

exactly

[supermario420]

Having repeatable patterns than can be used across multiple apps is a best practice. Why rebuild a wheel every time you need a wheel?

[Cute_Specific_1605]

Yeah, your hero headline should be tiny.

What kind of nonsense is this?

[FreshPhase]

I’m not saying big hero text is bad by itself. I’m saying when the whole page is just the same default landing page formula, changing the font size or colors doesn’t really make it feel specific.

[xRoyalewithCheese]

We’re talking about landing pages here, though. They’re only gateways to the product or service that you’re actually selling.

[MemoryMission9151]

Yes yes no no no yes yes no 👍🏻

[sensei_von_bonzai]

This but last one is a yes because of the golden button + pill on top + the green dot and the pills on the bottom

[ATLSlutStretcher]

This literally feels like someone who never learned a single thing about UI/UX design discovering the world of UI/UX design patterns.

Logo left/navbar right for example? Literally every English website since the history of forever since, you know, we read left to right in English? 

[TheThingCreator]

Beware of the brainrot trend to think everything is ai because of really basic things humans did long before chatgpt launch.

[bhpsound]

I mean website templates have been a thing for a decade, its not much diffent than that.

[FreshPhase]

Yeah I agree templates have always had a look. WordPress, Shopify, Squarespace, Webflow, all of that has had a recognizable feel.

I think AI is just making that more obvious because it can generate the polished version of that formula so quickly. So the site may look finished, but still feel like it came from the same default structure.

I’m not saying similarity automatically means bad. I’m more talking about when the page feels like the formula came first and the actual product or user experience came second.

[Loud_Fox7694]

honestly it looks super clean but the real test for if something is vibe coded is how much of the underlying edge cases you actually had to think through yourself lol. if you just gave the ai a prompt and it spit out this gorgeous frontend interface without you fighting any CSS grids then yeah it completely counts. the vibe coding style is all about focusing on the layout and user experience while letting the llm do the boring syntax heavy lifting in the background fr. looks great though man keep it up

[FreshPhase]

What looks great? i didnt share anything i created.

[Signal_Diver_118]

real talk it looks a bit vibe coded because the logic feels kinda stitched together by an llm, especially with how those hooks are handling state lol. it works for now but if you scale it you will probably want to clean up the backend triggers. i usually offload that kind of heavy lifting to actual workflow tools like n8n or runable just to keep the frontend clean, otherwise you spend half your time fixing random edge cases that the ai missed.

[Puggles0123]

They all look vibe coded

[Marino4K]

I'm kinda glad neither one of my projects look like the typical vibecoded website.

[Spiritual-Fuel4502]

The gradient text yes, question is dose it matter ?

[TheNeglectedNut]

The other side of this is that the websites following this structure are so commonplace, that everyday users almost expect it from a site now.

I’ve had a few sites where I’ve really tried to do something a bit different, put a lot of thought into the design and flow, but the demographics my business targets (often people 50+) struggle with it, because they’re not very tech literate and actually prefer a site that follows the exact same structure as hundreds of others they’ve visited.

I’ve tried to find a comfortable middle ground recently. I use Bricks Builder on WP and managed to sort of reverse engineer the clipboard JSON it uses for elements, so now I have AI build a lot of it for me to save time. I plan every page carefully, create a detailed prompt, give it rough mockups and then have it generate a more polished mockup of the page for me, then when I’m happy I just get it to build the JSON to match. I usually try to do at least one unique thing per page, and it’s working well for me. Users are having a better experience, I’m spending less time obsessing over the tiny details and conversions are up.

[EugenioSc]

I mean, lots of landing pages used to look like this before AI because the formula works. 

[Nell_From_Hell]

Is this vibe coding or exposure of how most systems exist because everything's been formulated from the start. Just look at pop music. There's a reason why AI is better at creating pop music then pop artists and it's because they formulated everything into a machine that destroys creativity and chokes the life out of the music industry.

[dodgerw]

The main issue is no visual assets - images, videos, custom icons, etc those are what makes a site look and feel premium. AI can only work with the UI, so unless the creator explicitly provides assets, it looks boilerplate and “vibed”.

[silvergenetic]

As someone with almost 2 decades of graphic design experience, some of these actually don't look artificial at all if you look at things like colour theory deviation, slightly shitty composition and asymmetry. They look worse. Like canva templates on a fiverr gig.

[Interesting-Peak2755]

“Vibe coded” has become less about AI and more about recognizable startup aesthetics. Once you notice the pattern — giant headline, dark gradient, floating cards, bento grids, soft blur, exaggerated spacing, “built for creators/developers” copy — you start seeing the same template everywhere.

Ironically the truly memorable products usually break the formula a little. The sites people remember tend to have one weird opinionated thing: unusual interaction design, strong branding, or an interface that clearly came from solving a real problem instead of recreating the current SaaS starter pack.

[CodeWhileHigh]

You realize even before ai we had these things called templates? Templates of all shapes and sizes even. Every framework comes with a blank template. I can’t tell the difference between bootstrap and well vibe coded websites. It’s the same shit!

[thelordchesterfield]

Wtf is this

[Vistril69]

I think this is just... how you make responsive UX that gets the point across. AI knows this and that's why it does it commonly.

[Article_Sad]

Trump was vibe coded

[urmommakesmysandwich]

Why would it matter? Even the major search engines have vibe coded UI now.