## 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/termsquad-com/d12b8131-9740-4063-aef8-780525dfffce-1789166958-2.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/termsquad-com/d12b8131-9740-4063-aef8-780525dfffce-1789166919347-full.webp
- Component on Kage: https://kage.design/component/termsquad-feature-grid

## Before you start
Ask what the user's product, audience, and brand are, then apply the principles below to their product rather than copying this reference.

Build a dark feature section explaining how the product continues working away from the user's main device. Start with a two-column heading area: an eyebrow and large stacked benefit headline on the left, concise explanatory copy on the right. Below it, place one large rounded demonstration panel showing an abstract device-to-browser or device-to-cloud relationship. Finish with a short caption and two subtle directional links. Use a 12-column grid, 36px side gutters, and generous vertical whitespace. Surfaces should be #0c1011 against #07090a, with #202726 borders, 18px panel radius, muted grey text #89918e, primary text #edf2ef, and a small mint #a9e9c0 status accent. Let the visual carry the section, keep labels tiny and technical, and make the panel responsive by stacking its panes on narrow screens.

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