Viktor.comAn AI coworker that actually does the work
Acebuilder
Build landing pages with Aceternity UI
225 followers
Build landing pages with Aceternity UI
225 followers
Acebuilder is an AI website builder from the team behind Aceternity UI. Instead of generating generic layouts from scratch, it pulls from Aceternity's actual Pro template and component library — you import a full page or a single block, then reshape the copy, layout, and structure by chatting with the agent. Generate images without leaving the chat. Run design "skills" on any section to push the agent past generic filler toward sharper layout. Export your code as a zip. You own what you build.
Aceternity UI Pro
Content Writing Jobs
@manuarora looks awesome! Congrats on the launch!
@manuarora frontend engineering is officially dead with this, jokes apart congrats pajji for new product
@manuarora Congrats on the launch! Quick question: when the agent pulls from your Pro template library, how does it balance preserving a template's original visual language versus adapting components to a user's brand (colors, typography, spacing)?
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 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 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 "AI generates beige generic sites" observation is spot-on — that's the same failure mode
I keep seeing with Blazor SPA landing-page starters too. Curious how you're structuring the
skill prompts to point the agent at specific components without hallucinating layout drift.
Beta or not, congrats on shipping something opinionated.
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?