lovable.dev
Design analysis
The section presents search optimization as an actionable product capability: explanatory copy on the left, a detailed audit interface on the right, and three proof cards below.
Prompt preview
## Reference images Study these alongside the description below: hierarchy, rhythm, spacing, colour. Build for the product you are asked about, using this design language. - Component: https://kage-design-assets.t3.tigrisfiles.io/components/lovable-growth-tools/9452fb95-0338-4269-a5da-8889e8804cc9-1792216984-5.webp - Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/lovable-growth-tools/9452fb95-0338-4269-a5da-8889e8804cc9-1792216920277-full.webp - Component on Kage: https://kage.design/component/lovable-growth-tools-feature-grid-3 ## Before you start Ask what the user's product and brand are, then apply these principles to that product rather than reproducing the reference. Build a product-capability section for discoverability. Use a two-column intro with a strong heading, explanatory paragraph, and dark text CTA on the left; on the right show a polished audit/checklist panel with grouped rows, status icons, and one blue or brand-colored action button. Below it, add three equal cards with short titles and supporting text. Use an off-white canvas, 1px borders (#e6e6e2), 10–14px radii, soft shadows only on the interface panel, and clear success/warning/error color semantics. Ensure the checklist is readable and keyboard accessible. Never: use logos, product names, copy, illustrations, or imagery from the reference.
kage