## 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-1789166957-1.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-hero

## 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.

Create a centered hero for a developer-focused SaaS product. Place a large responsive headline in two lines, a narrow supporting paragraph below it, then a primary light button and secondary outlined button. Add a small compatibility or integration strip beneath the actions, followed by a wide framed product preview that visually demonstrates the promise. Use a black-to-charcoal background with a very subtle green atmospheric glow, white headline text around #f1f3f1, muted copy around #929896, mint accent around #aef0c7, and surfaces around #0c1010. Keep the hero vertically spacious, with the visual beginning below the CTA row; use 16–20px outer radius, faint 1px borders, soft shadows, and restrained glow. The headline should be 48–72px desktop with tight line-height and scale smoothly on mobile. Buttons should have strong contrast, 12px radius, and arrow affordances; the preview may show abstract panes, status indicators, and agent activity without relying on literal screenshots.

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