## 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/loqua/e5cf041a-edc7-487a-b4b8-8f4d563da4de-1789192874-6.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/loqua/e5cf041a-edc7-487a-b4b8-8f4d563da4de-1789192838731-full.webp
- Component on Kage: https://kage.design/component/loqua-form

## Before you start
Ask what the user's product should let a visitor try immediately and what safe sample input demonstrates its value. Build the interaction around that answer.

Create a “try it now” playground on the ivory page. Use a two-column layout with a large editorial heading on the left, a short explanation, and a softly highlighted sample transcript card in pale yellow (`#fff0a9`) with a small colored label. Place a large white input/output panel on the right with a soft shadow, 16px radius, generous empty space, and a subtle keyboard or microphone hint near its bottom edge. Add a compact control row or status indicator so the panel feels interactive. Include a small product illustration only if the user's brand supplies one; otherwise use abstract UI. Keep the section around 80–110px vertical padding and collapse to one column on mobile.

Never:
- use logos, product names, copy, illustrations, or imagery from the reference
- make the demo imply that user data is stored without explaining it
- use a fake input that looks interactive but does nothing