Post · 3 November 2026
A moment of silence for “make it look premium”
Start with a layout, browse component libraries and choose what fits before your agent builds the page.
I think a lot of AI websites look like slop because we let the agent start writing code before we’ve decided what the page should look like. It builds components from scratch, or reaches for the same familiar defaults, and the rest of the conversation becomes an attempt to explain what “more premium” means.
Here’s how I’d fix it. Start by asking your agent to work out the layout and what each part of the page needs to do. Then have it browse component libraries and bring back a few working demos for you to choose from.
Some places to look for components and animation:
- React Bits for animated React components and backgrounds.
- Anime.js for JavaScript animation, including scroll effects and draggable elements.
- 21st.dev for community-built components, templates and themes.
- Motion for layout, scroll and gesture animation.
Open the demos and try them yourself. Pick the components you’d like on your page, then tell the agent what you want to keep or change. It’s much easier to explain what you want when you both have something specific to look at.
Good prebuilt components often come with responsive layouts and accessibility support already built in. You still need to verify that they work at different screen sizes and meet WCAG requirements on your finished page, but you’re starting with work someone has already done. That can save a lot of time otherwise spent getting your agent to build and fix every detail from scratch.
To complement this, you can also give your agent a design skill:
If I had to choose one thing to improve agent-driven web design, I’d have the agent browse component libraries and show me options. I’d pick that over adding a design skill.