Acebuilder

Aceternity blocks lean hard on framer-motion and scroll-triggered reveals, and when I've had an agent stack several animated sections on one page, the IntersectionObserver entrances all fired on first scroll and the page janked with layout shift. Pulling from the real library instead of hallucinating fixes the component quality, but when your agent composes a page from multiple Pro components, does it stagger or dedupe those scroll animations, or do I get every block's entrance effect firing at once?

the custom-code and export questions above are the ones I'd want answered before committing to it. one more on the maintenance side: once a component is imported and customized in my project, is it a one-time snapshot, or does it stay linked to the Aceternity library so a future update to that component could touch my already-customized version? trying to picture whether "pull from the real library" means ongoing coupling or just a better starting point

Aceternity's components are gorgeous so this makes sense as a builder layer. what happens when I need something outside the component library though - can I drop in custom code, or am I stuck picking the closest preset and fighting it?

Importing from the real Aceternity Pro library instead of hallucinating layouts is the part that would actually keep me in it — most AI builders invent components that don't exist. When I export the code, is it clean React/Tailwind with the Aceternity components as real npm dependencies, or inlined source I then have to maintain by hand? And if I edit a block's code locally and re-import it, does the agent preserve my manual changes or regenerate over them?

The "AI generates beige generic sites" observation is spot-on — that's the same failure modeI keep seeing with Blazor SPA landing-page starters too. Curious how you're structuring theskill prompts to point the agent at specific components without hallucinating layout drift.Beta or not, congrats on shipping something opinionated.

Hey Product Hunt 👋

I'm the person behind Aceternity UI — if you've built a landing page in the last couple years, there's a decent chance you've used one of our components without knowing it (120k+ people have at this point).

The problem we kept running into: most AI website builders generate the same beige, generic-looking site no matter what you ask for. Meanwhile we had thousands of hand-designed templates and blocks just sitting in a library, mostly used one at a time by people copy-pasting code or with the CLI.

So we built Acebuilder to close that gap. You chat with an agent like you would with any AI builder, but it's pulling from our actual Pro template and component library instead of hallucinating a layout from nothing. Pull in a full page, drop in individual blocks, or start from a blank Next.js/Vite project.

The part I'm most proud of is skills: point the agent at a section that looks off, run a skill, and it'll push the design toward something sharper instead of the usual AI slop.

We're still in beta, so you'll hit rough edges, genuinely want to hear about them. Drop a comment or question below, I'll be in the thread all day.