## 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/lull/1eb36b3c-9a0d-499b-8ae4-8916c2d1f7b6-1789884098-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/lull/1eb36b3c-9a0d-499b-8ae4-8916c2d1f7b6-1789884066726-full.webp
- Component on Kage: https://kage.design/component/lull-cta

## Before you start
Ask what the user's primary conversion is, which platforms are supported, and what reassurance users need before taking action. Build a closing CTA around that product context.

Create a dark, centered conversion section with a short editorial serif heading at the top. Place a single realistic but brand-neutral device mockup or product preview beneath it, scaled large enough to understand but not so large that it dominates the page. Add platform download buttons in a compact row, then a brief low-pressure reassurance line and an optional small returning-user link. The hierarchy should be heading → preview → action buttons → reassurance. Make store buttons accessible, distinguish platform states, and keep the Android or secondary platform honest if it is not yet available.

Approximate language: background #101012, heading #f0ece5, body #aaa6a0, device frame #171719 with #050505 screen, buttons rgba(255,255,255,.09), border rgba(255,255,255,.13), 12–16px radius. Use 42–52px serif heading, 14px body, 44–52px button height, generous vertical spacing. Add subtle hover brightening and respect reduced-motion preferences.

### Never
- Never copy the reference phone screen, logo, product name, store artwork, or wording.
- Never claim platform availability that the user's product does not have.
- Never bury the primary action among unrelated links.