Σ SigmaUI 0.1 preview
SIGMAUI / DOCUMENTATION

Component authoring SDK

Component definitions belong to reviewed TypeScript source; editable instances belong to documents.

Authoring a supported definition

defineComponent validates and freezes purpose, editable fields, named slots, allowed child types, layout capabilities, responsive intent, theme bindings, data bindings, constraints and accessibility behavior. The compiled nativeDefinitions registry drives the renderer, inspector and agent context.

Extend in trusted source

Add a canonical type in names.ts, define its metadata in definitions.ts, declare its validated props in the core schema and implement its React/export adapter. Exercise the conformance suite before distributing it. Runtime JSON or agent output cannot inject executable component implementations.

Prove the editing cycle

Conformance tests cover developer-created instances, visual layout operations, reviewed agent content/responsive edits, inspector style changes, source export and JSON reopening. They verify binding, slot, identity, accessibility and layout preservation. Backend product records, prices and checkout callbacks are supplied through TrustedBindings rather than editable document fields.