Kage Design logo kage
lorikeetcx.ai
lorikeetcx.ai feature grid component

Design analysis

A large looping connector diagram visually explains how external tools feed into a central resolution workflow, while the centered copy remains the semantic anchor.

Prompt preview
## 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/lorikeetcx-ai/66a45b6c-3f5c-4089-bde2-7a0aa025402f-1789142170-8.webp
- Full page it was cut from: https://kage-design-assets.t3.tigrisfiles.io/screenshots/lorikeetcx-ai/66a45b6c-3f5c-4089-bde2-7a0aa025402f-1789141728989-full.webp
- Component on Kage: https://kage.design/component/lorikeetcx-feature-grid-3

## Before you start
Ask which integrations and workflow stages are real for the user's product, then build an original diagram using those relationships.

Create a systems-integration feature section with a central explanatory heading and a decorative but meaningful connector diagram around it. Show approved integration icons entering and leaving a central workflow, with the copy explaining the start-to-finish outcome.

Design rules:
- Layout: centered content block over a wide diagram canvas; connectors should sit behind or around the copy without obscuring it.
- Connectors: thin rounded paths in a restrained gradient such as violet #8B70D8 to yellow #E6C95A; use smooth loops rather than sharp technical wiring.
- Integration tiles: small white rounded squares, 42–52px, subtle border and shadow; use only approved icons.
- Typography: serif heading 32–42px, body sans-serif 13–15px, max-width 360–430px.
- Accessibility: provide a textual list of integrations and relationship description for screen readers.
- Responsive: simplify the diagram into a vertical flow on mobile.

Never:
- Never reuse the reference integrations, icons, product name, or copy.
- Never prioritize decorative lines over understanding.
- Never imply a live integration that the product does not have.

More components