## 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-1789192873-3.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-feature-grid

## Before you start
Ask which platforms and environments the user's product genuinely supports, and what proof of breadth matters to its buyers. Reinterpret this section for that ecosystem.

Create a full-width dark feature panel with a very large corner radius around 30–36px, using near-black `#171815` and cream text. Center a serif or editorial headline of roughly 27–34px, followed by one muted explanatory line. Below it, arrange supported integrations as compact rounded chips in several evenly spaced rows; each chip can include a tiny abstract colored mark and 11–12px label. Finish with two large light pill buttons for the primary operating-system or platform choices. Keep the panel padded generously and ensure chips wrap cleanly. Use subtle charcoal borders on chips and strong contrast on the platform buttons.

Never:
- use logos, product names, copy, illustrations, or imagery from the reference
- claim integrations that do not exist
- crowd the panel with more chips than users can scan