Patterns
How to build common product surfaces from Inceptor's primitives — the layer above components.
Components tell you how to import a control. Patterns tell you when and
how to build a surface out of them. This is the layer
Cloudscape leans on hardest, and the one
that multiplies a kit’s value — see docs/CLOUDSCAPE-GAP-ROADMAP.md
Epic B.
Every pattern below is built from primitives that already ship in the
gallery and is demonstrated by a live page under /demos/.
The catalog
| Pattern | Build it from | Live demo |
|---|---|---|
| Listing | useListing + DataTable + PropertyFilter + EmptyState/ErrorState | /demos/data/large/ |
| Create flow | Wizard (multi-step) or Form (single-page) + Zod | /gallery/wizard/ |
| Details page | DetailsPageSimple / DetailsPageWithTabs + AppLayout | /gallery/resource-details/ |
| Delete with confirmation | AlertDialog + Flashbar | /gallery/overlays/ |
| Empty / error / loading states | Skeleton, EmptyState, ErrorState, useListing | /demos/dashboard/ |
The rule of thumb
Reach for a pattern, not a raw component, when a surface recurs: a list of things, a form that creates a thing, a page that shows a thing, a destructive action. The patterns encode the decisions (which empty state? confirm how hard? validate when?) so each new surface is a fill-in-the-blanks, not a redesign.