## 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-1792440521-2.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-hero-2

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

Build a product showcase section with a short, centered or narrow-column problem statement followed by a large, centered interface mockup. Introduce the feature with a small uppercase eyebrow, a bold benefit-led heading, concise explanatory copy, and a secondary demo link. Make the interface the visual anchor: use a bright document workspace, a clear side panel, highlighted analysis controls, and a small optional watch-demo pill. Keep the page background calm and let the product frame carry detail.

Use the same pale cool background #eeeef4, white UI surfaces #ffffff, soft gray borders #e2e3e8, blue interaction accents around #3157ee, and dark text #17181d. Use 12px uppercase eyebrow text, a 40–52px heading, 16px supporting copy, and broad vertical spacing. Add subtle shadowing and 12px radii to the mockup. If animated, reveal annotations or highlights progressively, but respect reduced-motion settings.

### Never
- Never copy logos, product names, copy, illustrations, or imagery from the reference.
- Never make the screenshot more prominent than the feature's user benefit.
- Never add illegible tiny UI merely to simulate complexity.