## 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/jurniti/cfab9c3f-60ef-4e80-9a31-cc939c39468c-1789538635-7.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/jurniti/cfab9c3f-60ef-4e80-9a31-cc939c39468c-1789538542122-full.webp
- Component on Kage: https://kage.design/component/jurniti-feature-grid-6

## Before you start
Ask what persistent data, memory, or saved state means for the user's product and what brand conventions to apply. Build a distinct module section, not a replica.

### Design language
- Start with a centered eyebrow, 36–48px headline, and concise 14–16px supporting copy.
- Use three equal cards in a responsive row, with blush background #fce9df, subtle border #ecd1c7, 10px radius, and 24px padding.
- Give each card a small icon, a compact uppercase badge in a pale yellow/peach pill, a 16px title, and 12–14px descriptive copy.
- Keep the optional note or link centered beneath the cards with a tiny icon and muted text.
- Use enough top and bottom padding to make the section feel like a standalone product capability.

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