## 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/formabledocs-com/3108c64d-0f5a-4f45-931d-d27909065482-1792440522-5.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/formabledocs-com/3108c64d-0f5a-4f45-931d-d27909065482-1792440481208-full.webp
- Component on Kage: https://kage.design/component/formabledocs-feature-grid-3

## Before you start
Ask what the user's product, audience, and brand are, then apply the following principles to that product rather than reproducing the reference.

Create a trust-focused feature panel with a two-column layout: a tall, softly rounded muted visual or abstract security graphic on the left, and an eyebrow, assertive headline, link, and low-density explanatory paragraph on the right. Keep the content inside a broad pale surface and vertically align the text to the visual's center. Use the panel to explain security, privacy, reliability, or compliance in plain language.

Use a very light background #f7f7f7, black text #17181b, muted copy #73757c, and a subtle #e5e5e6 border. Use 16px radii, 44–64px internal padding, a 40–48px heading, and generous separation between the promise and proof. The visual should be abstract or product-specific, not decorative noise. Stack columns on mobile.

### Never
- Never copy logos, product names, copy, illustrations, or imagery from the reference.
- Never make unsupported compliance claims.
- Never let the image overpower the security message.