## 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/descript-com/c210b18a-1678-4bef-91b5-c444a8589f04-1789146911-3.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/descript-com/c210b18a-1678-4bef-91b5-c444a8589f04-1789146857587-full.webp
- Component on Kage: https://kage.design/component/descript-feature-grid

## Before you start
Ask what the user's core workflow is and which features deserve the strongest proof. Adapt the component to those answers and the user's brand.

Build a dark, editorial feature area in two layers. First, center a large section heading, then provide a compact horizontal tab row for stages such as capture, edit, refine, share, or equivalent stages for the product. Show one selected tab with a filled pill and a large rounded panel underneath: explanatory heading and body copy on the left, a compact checklist or metadata list below, and a product visual on the right. Add restrained previous/next controls at the panel edges. Second, introduce a new heading and a large two-column feature spotlight. Put the feature title, short paragraph, and one coral CTA on the left, with a framed interface visual on the right. Use deep near-black burgundy #21040b, panel burgundy #5d0b28, accent coral #ff4d4d, and warm white #fff5f0. Use 56–88px section padding, 40–56px internal gaps, 16px panel radius, and thin translucent borders. Tabs must be keyboard accessible, and arrows should update the selected panel with a subtle transition.

### Never
- Never copy the reference's tab labels, product UI, feature names, copy, or imagery.
- Never present every feature with equal visual weight; establish a clear active state.