## 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/omnea-co/444fd721-a6f8-467e-8179-cf278abe5ec1-1789142167-4.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/omnea-co/444fd721-a6f8-467e-8179-cf278abe5ec1-1789141735165-full.webp
- Component on Kage: https://kage.design/component/omnea-feature-grid-2

## Before you start
Ask what the user's product is, who it serves, and what its brand personality and primary conversion goal are. Then apply the following principles to that product rather than copying the reference.

Build a product capabilities section with a left-aligned editorial heading and a short statement about making complex work simpler. Place two large side-by-side feature tiles first, each using a realistic but invented UI mockup or abstract interface composition, a short overlay headline, and a supporting sentence. Follow with three smaller cards for integrations, existing-system actions, and proactive reminders. Use a near-white canvas, soft gray #f0f0ed borders, 6px corners, subtle shadows only where needed, and a restrained palette of charcoal plus pale green, blue, and peach accents. Keep visuals dominant but make all explanatory text accessible as HTML. Use CSS grid with a 2-column top row and 3-column lower row, collapsing to one column on mobile.

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