Design analysis

The hero uses a dramatic editorial headline on the left and a large angled desktop-app preview on the right, followed by two clear actions and a compact trust/status row. A pale paper-like background and red annotation accents make the software feel crafted rather than generic.

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/moji/682da163-2f11-4698-8415-78d5458fc05f-1789193059-1.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/moji/682da163-2f11-4698-8415-78d5458fc05f-1789192951631-full.webp
- Component on Kage: https://kage.design/component/moji-hero

## Before you start
Ask what the user's product is, what its primary promise is, and which action matters most. Ask for the brand palette and preferred type style, then apply these principles to that product.

Create a two-column desktop hero with a left text block and a right product visual. Put a tiny eyebrow label above a very large 3–4 line editorial headline, a short readable paragraph, two CTAs (one filled dark, one outlined), and a small version/trust line. Show the product in a large, slightly tilted screenshot or UI mockup on the right, with one or two small floating status pills. Keep the section airy and approximately 650px tall, aligned to a max-width of about 830px. Use an ivory background #f7f6f1, near-black #191a1b, muted grey #6e6d68, and restrained vermilion #b42d27 for tiny labels or rules. Pair an expressive serif display face with a neutral sans-serif body. Use soft shadows, 12–18px radii, and avoid excessive decoration. Make both CTAs keyboard accessible and stack the layout on mobile.

Never: use logos, product names, copy, illustrations, or imagery from the reference.