Why AI-built marketing sites look generated (and how to fix it)
Coding agents ship layouts fast, but the result reads as template soup. Here is what actually makes a marketing site look designed — and how Initium encodes it.
· Initium Team · 1 min read
Every dev who has asked a coding agent for a landing page knows the result: technically fine, visually forgettable. The spacing is uneven, the headline is generic, and every section looks like it came from a different site.
The three tells of a generated site
- No rhythm. Sections stack without alternation — no zigzag, no breathing room budget.
- Copy sized wrong for the layout. Headlines overflow their blocks or leave awkward gaps.
- Invented proof. Fake testimonials and made-up metrics that erode trust on sight.
What "designed" actually means
A designed page follows a system: one style preset, a headline budget per block, and sections chosen for the story they tell in sequence — not for how impressive each looks alone.
npx shadcn@latest add @initium/hero-section-1Initium ships that system as blocks, style presets, and agent skills — so the agent assembling your page follows the same rules a designer would.
Build a site that looks designed
Initium gives your coding agent the blocks, style presets, and skills behind everything on this blog.
Try for freeMore from the blog
shadcn registries explained: installing blocks you own
What a shadcn registry actually is, what happens when you run npx shadcn add, how namespaces and private registries work, and why agents like them.
6 min read
From zero to a full website with Initium: a walkthrough
Blank folder to deployed marketing site: shadcn init, the Initium registry, a style preset, strategy files, blocks, and the prompts that keep it designed.
6 min read
How to structure a SaaS landing page, section by section
A section order for a SaaS landing page, the reasoning behind each position, and how to assemble the page from shadcn blocks without padding it.
6 min read