Skip to main content

Design System and Component Library

The component library is part of App Generation because it is the customer-visible output and reusable UI kit produced around ThorAPI models. ThorAPI generates the model/client foundation; App Generation decides how those models become usable forms, grids, dashboards, app templates, and polished vertical workflows.

Component Families

FamilyExamplesRole
Generated entity UIforms, lists, RB grids, permission dialogsCRUD and admin surfaces over generated ThorAPI objects.
Aurora/design surfacesAuroraHero, MagneticFeatureCard, OrbitalIconCloud, VelocityScrollPanelProduct and generated-app presentation components.
Dashboard and opsLCARS dashboard panels, workflow metrics, application wizard panelsOperational product shell for generated and managed services.
Gridheim/SheetsterGridheimSheet, FormulaBar, Cell, Demo componentsSpreadsheet-like editing and calculated field UX.
Vertical appsCRM, CMS, eCommerce, digital product pagesPrebuilt business capabilities that can be generated, customized, and deployed.
Agentic surfacesAgentDesigner, SageChat, Workflow Studio helpersUI for agent and workflow assisted creation.

Design Rules

  • Component docs live under App Generation because they are generated-app building blocks.
  • Aurora components are reusable app-generation affordances, not standalone marketing ornaments.
  • Gridheim components belong here as UI components, while Rune semantics belong under the Runes domain.
  • Generated entity components should expose RBAC-visible fields only and respect hidden/encrypted field contracts.
  • Persona mode may change default density, ordering, and complexity, but RBAC still decides what the user is allowed to access.

Asset Handoff

ValorIDE application generation

Generated apps should be usable in three modes:

  1. No-code guided build through Valor and the App Generation wizard.
  2. Low-code component assembly through OpenAPI Design Center, component previews, and bundled templates.
  3. Agentic coding through ValorIDE, which owns workspace code edits, tool use, tests, and publish-back workflows.

Canonical Locations

  • Component docs: Products/ValkyrAI/App Generation/Component Library
  • Runtime component source: web/typescript/valkyr_labs_com/src/components
  • Generated ThorAPI client library: web/typescript/valkyr_labs_com/src/thorapi
  • Component packaging scripts: web/typescript/valkyr_labs_com/scripts/package-component-library.mjs
  • Application wizard: web/typescript/valkyr_labs_com/src/components/ApplicationBuilder