## 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/inflight/ac6190d7-6ca0-4ac1-9ff1-df4f4b5185a3-1792562738-4.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/inflight/ac6190d7-6ca0-4ac1-9ff1-df4f4b5185a3-1792562711335-full.webp
- Component on Kage: https://kage.design/component/inflight-feature-grid

## Before you start
Ask what the user's product is and what its brand personality should be, then apply the principles below to that product.

Build a light feature section for a software workflow. Start with a left-aligned section heading and supporting paragraph in a max-width container. Follow with three vertically stacked feature rows: each row should contain a soft-gray rounded product UI preview on one side and a concise heading plus explanatory copy on the other, alternating or maintaining a consistent media/text rhythm. Use near-black #101216 text, gray #666a70 body copy, pale backgrounds around #f1f3f5, 12–16px radii, and roughly 80–120px between rows. On mobile, stack media above text. The UI previews should be abstract, custom placeholders that communicate the feature without reproducing a reference screen.

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