Frontend Components

You inject the generated action (from useApiActions) rather than the component calling fetch itself. That keeps the component transport-agnostic and fully typed against your config, and lets it run behind your proxy/cookies. Each action exposes { start({ payload, onAfterHandle, onErrorHandle }), state }.

Each component family owns a store (useLoginStore, useUsersStore, useNotificationCenterStore, …) holding its form/UI state. You can read or drive it from outside for custom layouts without forking the component.

Appearance is a plain theme object. Use the exported default (loginPageTheme, notificationCenterTheme, …) as-is, or extendXTheme({ … }) to deep-merge overrides. Tailwind-class based, so it inherits your design tokens.

Most pages ship multiple layouts. Auth pages offer default / minimal / split; data and account pages have their own variants. Switch layout without touching logic.

Feature toggles (showRememberMe, password policy, channels…) live in a config object, and lifecycle hooks (onSuccess, onLogout, onForgotPassword…) let you own navigation. Sensible defaults mean the minimal wiring is just the action.

Sign-in and sign-up, with captcha, remember-me, a live password-strength meter and terms gating. See Auth Pages.

The full reset/recovery set, plus SetPasswordPage which doubles as the invite-acceptance / magic-link landing. Share one PasswordPolicy engine. See Auth Pages.

The pages a user lands on from a verification or magic-link email — they consume the token, call the verify action and render verifying / success / error states.

The signed-in user's profile with AddressCard, PhoneCard and ProfileHeader sub-components, hydrated from the ME response. Variants for compact vs full layouts.

Active sessions / devices with DeviceCard + revoke and revoke-all actions — the UI for the multi-device session surface documented under Authentication.

An admin user-management console (UserListItem + UserDetailPanel) over the admin user actions — list, inspect and act on users.

Client-side route protection and reactive UI gating by role/claim/scope, hydrated from the ME action. Has its own deep dive — see Auth Guard.

A full RBAC console: browse roles and claims and edit role→claim assignments visually. Backed by useAuthorizationStore with its own extendable theme — the admin UI for everything on the Authorization page.

A bell with an unread badge and a dropdown/drawer center, wired to NOTIFICATION_LIST / UNSEEN_COUNT / MARK_SEEN / MARK_ALL_SEEN. Variants and an extendable theme. See Notification.

A node-graph editor (NodePalette, StepFlowNode, VerifierFlowNode, NotificationFlowNode, PropertiesPanel, PendingTab) for authoring the approval flows the Verification engine runs — drag steps, verifiers and notification rules, then publish.

The approver-facing widgets: a panel to act on one record's pending verification, and a list of everything awaiting the current user — built on VERIFICATION_PENDING / STATUS / DECIDE.

The data engine: pass an entity + your apiActions and get items, pagination meta, isLoading, infinite loadMore (de-duplicated), addItem/updateItem/deleteItem, bulkAdd/bulkDelete, and search/sort/filter state — all routed through the generated CRUD actions for that table.

A sortable, filterable, paginated table that pairs with useNucleusEntity — column inference from the entity, row selection and bulk actions.

A batteries-included CRUD surface for an entity (list + create/edit forms + detail) — the fastest way to get an admin screen for any table you declared.

Renders a typed form from a field config / entity columns, with validation derived from the column definitions.

Themeable form and UI primitives with consistent styling hooks. Captcha is included for bot defence on auth forms.

The proof-of-work / challenge widget wired to CAPTCHA_GENERATE, used by LoginPage and RegisterPage but mountable anywhere.

A built-in component explorer (ComponentSidebar, ComponentCanvas, PropsPanel, createDefaultRegistry) — a living style guide for the kit, themeable like everything else.

cn() for class merging; column helpers (getColumnType, isReferenceColumn, shouldExcludeFromForm…); and endpoint-key generators (generateEntityEndpointKey, toUpperSnakeCase…) that map an entity to its generated action keys.