Example Smart Components is a collection of production-quality Smart Component templates maintained by Unqork. Each template is a concrete example of what the Build Agent can produce: well-built, accessible, and themeable components that follow the patterns the agent uses when authoring from scratch.
Example Smart Components illustrates common patterns. It is not a catalog of what the Build Agent can create. The Build Agent can produce a far wider range of components based on what Creators describe. Use Example Smart Components to learn how Smart Components are structured and to get started quickly, not as a ceiling on what is possible.
Templates are read-only and serve as a starting point. Copy one to the library and it becomes an independently owned component. Creators can rename it, re-theme it, extend it, or hand it to the Build Agent for further changes.
Example Smart Components are available in the Smart Components Hub under Example Smart Components in the Explorer panel.
Opening an Example Smart Component
- Select
Library in the global header, then select 
Smart Components Hub. - In the Explorer panel, select Example Smart Components to expand the section.
- Select a template to open it in the Smart Component Editor.
Example Smart Components open in read-only mode. The full editor experience is available, including visual preview (for UI templates), Logic View, typed interface, and description, but the template cannot be edited.
Copying a Template to the Library
Select Copy to Library, available at the top of the read-only editor or from the template's 
(ellipsis) menu in the Explorer, to create an independently owned Smart Component. The copy opens in the Smart Component Editor immediately.
The copy has no link back to the original template. Unqork updates to Example Smart Components never affect copies in the library. From that point Creators can rename it, re-theme it, extend it, or ask the Build Agent to make changes.
Available Templates
Fourteen templates are available at 9.0.
| Template | Description |
|---|---|
| TextField | A labeled text input with validation and help text. |
| Number | A labeled numeric input. |
| Checkbox | A single checkbox with a label. |
| DatePicker | A date selection input. |
| Combobox | A searchable select with filtered options. |
| Radio | A radio button group. |
| Button | A configurable action button. |
| Card | A surface container for grouped content. |
| CardWithChildren | A card with a typed slot for child components. |
| Drawer | A slide-in panel with a typed content slot. |
| Toast | A transient notification component. |
| Carousel | A horizontally scrollable content container. |
| Skeleton | A loading placeholder that matches a content layout. |
| Dashboard | A dashboard layout with composable regions. |
Example Smart Components vs. Legacy Components
Example Smart Components is not a one-to-one reimplementation of the legacy component catalog and is not trying to be. It demonstrates reference patterns: how to structure a labeled input with validation, how to build a composable card, how to handle loading states, and how to assemble a dashboard layout. Creators can study, copy, and extend each.
The practical difference from a legacy component is what happens when a template does not do exactly what is needed. A legacy component is fixed; the only recourse is a support request. An Example Smart Component is a starting point Creators can change in minutes using the Build Agent. If none of the templates match a use case, describe the component to the Build Agent and it will create one.
Changelog
| Date | Change |
|---|---|
| 2026-09-08 | Corrected Explorer section label from "Starter Kit" to "Example Smart Components" — confirmed in source (EN-8038). |
| 2026-09-04 | Initial publication (EN-8038). |