@superblocksteam/vite-plugin-file-sync 1.99.99-next.2

package/dist/ai-service/prompts/generated/library-components/SbTextPropsDocs.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from SbTextPropsDocs.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.007Z
+export const content = "## SbText\n\nThe following is the type definition for the SbText component.\n\n```typescript\ninterface SbTextProps {\n  text?: string;\n  /** @default \"text\" */\n  textType?: \"text\" | \"number\" | \"currency\" | \"date\";\n  /** @default undefined */\n  textStyle?: Record<string, any>;\n  /** @default \"left\" */\n  textAlign?: \"left\" | \"center\" | \"right\";\n  /** @default \"center\" */\n  verticalAlign?: \"top\" | \"center\" | \"bottom\";\n  /** @default true */\n  wrapText?: boolean;\n  animateLoading?: boolean;\n  shouldScroll?: boolean;\n  icon?: string;\n  /** @default \"LEFT\" */\n  iconPosition?: \"left\" | \"right\";\n  textType?: string;\n  /** @default \"USD\" */\n  currency?: \"AED\" | \"AFN\" | \"ALL\" | \"AMD\" | \"ANG\" | \"AOA\" | \"ARS\" | \"AUD\" | \"AWG\" | \"AZN\" | \"BAM\" | \"BBD\" | \"BDT\" | \"BGN\" | \"BHD\" | \"BIF\" | \"BMD\" | \"BND\" | \"BOB\" | \"BOV\" | \"BRL\" | \"BSD\" | \"BTN\" | \"BWP\" | \"BYN\" | \"BZD\" | \"CAD\" | \"CDF\" | \"CHE\" | \"CHF\" | \"CHW\" | \"CLF\" | \"CLP\" | \"CNY\" | \"COP\" | \"COU\" | \"CRC\" | \"CUC\" | \"CUP\" | \"CVE\" | \"CZK\" | \"DJF\" | \"DKK\" | \"DOP\" | \"DZD\" | \"EGP\" | \"ERN\" | \"ETB\" | \"EUR\" | \"FJD\" | \"FKP\" | \"GBP\" | \"GEL\" | \"GHS\" | \"GIP\" | \"GMD\" | \"GNF\" | \"GTQ\" | \"GYD\" | \"HKD\" | \"HNL\" | \"HRK\" | \"HTG\" | \"HUF\" | \"IDR\" | \"ILS\" | \"INR\" | \"IQD\" | \"IRR\" | \"ISK\" | \"JMD\" | \"JOD\" | \"JPY\" | \"KES\" | \"KGS\" | \"KHR\" | \"KMF\" | \"KPW\" | \"KRW\" | \"KWD\" | \"KYD\" | \"KZT\" | \"LAK\" | \"LBP\" | \"LKR\" | \"LRD\" | \"LSL\" | \"LYD\" | \"MAD\" | \"MDL\" | \"MGA\" | \"MKD\" | \"MMK\" | \"MNT\" | \"MOP\" | \"MRU\" | \"MUR\" | \"MVR\" | \"MWK\" | \"MXN\" | \"MXV\" | \"MYR\" | \"MZN\" | \"NAD\" | \"NGN\" | \"NIO\" | \"NOK\" | \"NPR\" | \"NZD\" | \"OMR\" | \"PAB\" | \"PEN\" | \"PGK\" | \"PHP\" | \"PKR\" | \"PLN\" | \"PYG\" | \"QAR\" | \"RON\" | \"RSD\" | \"RUB\" | \"RWF\" | \"SAR\" | \"SBD\" | \"SCR\" | \"SDG\" | \"SEK\" | \"SGD\" | \"SHP\" | \"SLL\" | \"SOS\" | \"SRD\" | \"SSP\" | \"STN\" | \"SVC\" | \"SYP\" | \"SZL\" | \"THB\" | \"TJS\" | \"TMT\" | \"TND\" | \"TOP\" | \"TRY\" | \"TTD\" | \"TWD\" | \"TZS\" | \"UAH\" | \"UGX\" | \"USD\" | \"USN\" | \"UYI\" | \"UYU\" | \"UYW\" | \"UZS\" | \"VED\" | \"VES\" | \"VND\" | \"VUV\" | \"WST\" | \"XAF\" | \"XAG\" | \"XAU\" | \"XBA\" | \"XBB\" | \"XBC\" | \"XBD\" | \"XCD\" | \"XDR\" | \"XOF\" | \"XPD\" | \"XPF\" | \"XPT\" | \"XSU\" | \"XTS\" | \"XUA\" | \"XXX\" | \"YER\" | \"ZAR\" | \"ZMW\" | \"ZWL\";\n  /** @default \"standard\" */\n  notation?: \"unformatted\" | \"standard\" | \"compact\" | \"scientific\" | \"engineering\";\n  /** @default 1 */\n  minimumFractionDigits?: number;\n  /** @default 2 */\n  maximumFractionDigits?: number;\n  dateInputFormat?: \"undefined\" | \"X\" | \"x\" | \"MM-DD-YYYY\" | \"MM-DD-YYYY HH:mm\" | \"MM-DD-YYYY HH:mm:ss\" | \"MM-DD-YYYY hh:mm:ss a\" | \"MM-DD-YYYYTHH:mm:ss.sssZ\" | \"YYYY-MM-DD\" | \"YYYY-MM-DD HH:mm\" | \"YYYY-MM-DD HH:mm:ss\" | \"YYYY-MM-DD HH:mm:ssZ\" | \"YYYY-MM-DDTHH:mm:ss.sssZ\" | \"YYYY-MM-DD hh:mm:ss a\" | \"YYYY-MM-DDTHH:mm:ss\" | \"DD-MM-YYYY\" | \"DD-MM-YYYY HH:mm\" | \"DD-MM-YYYY HH:mm:ss\" | \"DD-MM-YYYY hh:mm:ss a\" | \"DD-MM-YYYYTHH:mm:ss.sssZ\" | \"Do MMM YYYY\" | \"MM/DD/YYYY\" | \"MM/DD/YYYY HH:mm\" | \"MM/DD/YYYY HH:mm:ss\" | \"MM/DD/YYYY hh:mm:ss a\" | \"MM/DD/YYYYTHH:mm:ss.sssZ\" | \"YYYY/MM/DD\" | \"YYYY/MM/DD HH:mm\" | \"YYYY/MM/DD HH:mm:ss\" | \"YYYY/MM/DD hh:mm:ss a\" | \"YYYY/MM/DDTHH:mm:ss\" | \"DD/MM/YYYY\" | \"DD/MM/YYYY HH:mm\" | \"DD/MM/YYYY HH:mm:ss\" | \"DD/MM/YYYY hh:mm:ss a\" | \"DD/MM/YYYYTHH:mm:ss.sssZ\";\n  dateOutputFormat?: \"X\" | \"x\" | \"MM-DD-YYYY\" | \"MM-DD-YYYY HH:mm\" | \"MM-DD-YYYY HH:mm:ss\" | \"MM-DD-YYYY hh:mm:ss a\" | \"MM-DD-YYYYTHH:mm:ss.sssZ\" | \"YYYY-MM-DD\" | \"YYYY-MM-DD HH:mm\" | \"YYYY-MM-DD HH:mm:ss\" | \"YYYY-MM-DD HH:mm:ssZ\" | \"YYYY-MM-DDTHH:mm:ss.sssZ\" | \"YYYY-MM-DD hh:mm:ss a\" | \"YYYY-MM-DDTHH:mm:ss\" | \"DD-MM-YYYY\" | \"DD-MM-YYYY HH:mm\" | \"DD-MM-YYYY HH:mm:ss\" | \"DD-MM-YYYY hh:mm:ss a\" | \"DD-MM-YYYYTHH:mm:ss.sssZ\" | \"Do MMM YYYY\" | \"MM/DD/YYYY\" | \"MM/DD/YYYY HH:mm\" | \"MM/DD/YYYY HH:mm:ss\" | \"MM/DD/YYYY hh:mm:ss a\" | \"MM/DD/YYYYTHH:mm:ss.sssZ\" | \"YYYY/MM/DD\" | \"YYYY/MM/DD HH:mm\" | \"YYYY/MM/DD HH:mm:ss\" | \"YYYY/MM/DD hh:mm:ss a\" | \"YYYY/MM/DDTHH:mm:ss\" | \"DD/MM/YYYY\" | \"DD/MM/YYYY HH:mm\" | \"DD/MM/YYYY HH:mm:ss\" | \"DD/MM/YYYY hh:mm:ss a\" | \"DD/MM/YYYYTHH:mm:ss.sssZ\";\n  width?: Dim;\n  height?: Dim;\n  minWidth?: Dim;\n  maxWidth?: Dim;\n  minHeight?: Dim;\n  maxHeight?: Dim;\n  /** @default {\"top\":{\"mode\":\"px\",\"value\":0},\"bottom\":{\"mode\":\"px\",\"value\":0},\"left\":{\"mode\":\"px\",\"value\":0},\"right\":{\"mode\":\"px\",\"value\":0}} */\n  margin?: { left: Dim; right: Dim; top: Dim; bottom: Dim };\n  /** @default true */\n  isVisible?: boolean;\n  collapseWhenInvisible?: boolean;\n  shouldScroll?: boolean;\n}\n```\n";
+//# sourceMappingURL=SbTextPropsDocs.js.map

package/dist/ai-service/prompts/generated/library-components/SbTextPropsDocs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"SbTextPropsDocs.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-components/SbTextPropsDocs.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,yCAAyC;AACzC,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,20JAA20J,CAAC"}

package/dist/ai-service/prompts/generated/library-components/index.d.ts

@@ -0,0 +1,17 @@
+export { content as SbButtonPropsDocs } from "./SbButtonPropsDocs.js";
+export { content as SbCheckboxPropsDocs } from "./SbCheckboxPropsDocs.js";
+export { content as SbColumnPropsDocs } from "./SbColumnPropsDocs.js";
+export { content as SbContainerPropsDocs } from "./SbContainerPropsDocs.js";
+export { content as SbDatePickerPropsDocs } from "./SbDatePickerPropsDocs.js";
+export { content as SbDropdownPropsDocs } from "./SbDropdownPropsDocs.js";
+export { content as SbIconPropsDocs } from "./SbIconPropsDocs.js";
+export { content as SbImagePropsDocs } from "./SbImagePropsDocs.js";
+export { content as SbInputPropsDocs } from "./SbInputPropsDocs.js";
+export { content as SbModalPropsDocs } from "./SbModalPropsDocs.js";
+export { content as SbPagePropsDocs } from "./SbPagePropsDocs.js";
+export { content as SbSectionPropsDocs } from "./SbSectionPropsDocs.js";
+export { content as SbSlideoutPropsDocs } from "./SbSlideoutPropsDocs.js";
+export { content as SbSwitchPropsDocs } from "./SbSwitchPropsDocs.js";
+export { content as SbTablePropsDocs } from "./SbTablePropsDocs.js";
+export { content as SbTextPropsDocs } from "./SbTextPropsDocs.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/ai-service/prompts/generated/library-components/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-components/index.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AAC5E,OAAO,EAAE,OAAO,IAAI,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AAC9E,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AACxE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC"}

package/dist/ai-service/prompts/generated/library-components/index.js

@@ -0,0 +1,19 @@
+// Auto-generated sub-index
+// Do not edit this file directly
+export { content as SbButtonPropsDocs } from "./SbButtonPropsDocs.js";
+export { content as SbCheckboxPropsDocs } from "./SbCheckboxPropsDocs.js";
+export { content as SbColumnPropsDocs } from "./SbColumnPropsDocs.js";
+export { content as SbContainerPropsDocs } from "./SbContainerPropsDocs.js";
+export { content as SbDatePickerPropsDocs } from "./SbDatePickerPropsDocs.js";
+export { content as SbDropdownPropsDocs } from "./SbDropdownPropsDocs.js";
+export { content as SbIconPropsDocs } from "./SbIconPropsDocs.js";
+export { content as SbImagePropsDocs } from "./SbImagePropsDocs.js";
+export { content as SbInputPropsDocs } from "./SbInputPropsDocs.js";
+export { content as SbModalPropsDocs } from "./SbModalPropsDocs.js";
+export { content as SbPagePropsDocs } from "./SbPagePropsDocs.js";
+export { content as SbSectionPropsDocs } from "./SbSectionPropsDocs.js";
+export { content as SbSlideoutPropsDocs } from "./SbSlideoutPropsDocs.js";
+export { content as SbSwitchPropsDocs } from "./SbSwitchPropsDocs.js";
+export { content as SbTablePropsDocs } from "./SbTablePropsDocs.js";
+export { content as SbTextPropsDocs } from "./SbTextPropsDocs.js";
+//# sourceMappingURL=index.js.map

package/dist/ai-service/prompts/generated/library-components/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-components/index.ts"],"names":[],"mappings":"AAAA,2BAA2B;AAC3B,iCAAiC;AAEjC,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,oBAAoB,EAAE,MAAM,2BAA2B,CAAC;AAC5E,OAAO,EAAE,OAAO,IAAI,qBAAqB,EAAE,MAAM,4BAA4B,CAAC;AAC9E,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AACxE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/Dim.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "## Dim\n\nThe `Dim` class is used to define dimensions for size properties in Superblocks (especially width and height). It has three main modes: `px`, `fit`, and `fill`.\n\n```typescript\nclass Dim {\n  mode: \"px\" | \"fit\" | \"fill\";\n  value?: number;\n}\n```\n";
+//# sourceMappingURL=Dim.d.ts.map

package/dist/ai-service/prompts/generated/library-typedefs/Dim.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Dim.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/Dim.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,gRAAgR,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/Dim.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from Dim.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.009Z
+export const content = "## Dim\n\nThe `Dim` class is used to define dimensions for size properties in Superblocks (especially width and height). It has three main modes: `px`, `fit`, and `fill`.\n\n```typescript\nclass Dim {\n  mode: \"px\" | \"fit\" | \"fill\";\n  value?: number;\n}\n```\n";
+//# sourceMappingURL=Dim.js.map

package/dist/ai-service/prompts/generated/library-typedefs/Dim.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"Dim.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/Dim.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,6BAA6B;AAC7B,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,6QAA6Q,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/SbEventFlow.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "## SbEventFlow\n\nThe `SbEventFlow` class is used to define responses to events triggered on components (like onClick) in Superblocks. It has a number of methods that can be chained together.\n\n```typescript\nclass SbEventFlow {\n  // Run custom JavaScript code\n  static runJS(\n    handler: (s: ScopedState, additionalProps?: Record<string, any>) => void,\n  ): SbEventFlow;\n  runJS(\n    handler: (s: ScopedState, additionalProps?: Record<string, any>) => void,\n  ): this;\n\n  // Navigation methods\n  static navigateTo(props: { url: string; newWindow?: boolean }): SbEventFlow;\n  navigateTo(props: { url: string; newWindow?: boolean }): this;\n\n  static navigateToApp(appId: string): SbEventFlow;\n  navigateToApp(appId: string): this;\n\n  static navigateToRoute(route: string): SbEventFlow;\n  navigateToRoute(route: string): this;\n\n  static setQueryParams(\n    params: Record<string, string>,\n    keepQueryParams?: boolean,\n  ): SbEventFlow;\n  setQueryParams(\n    params: Record<string, string>,\n    keepQueryParams?: boolean,\n  ): this;\n\n  // Control UI components\n  static controlSlideout(\n    slideoutId: string,\n    action: \"open\" | \"close\",\n  ): SbEventFlow;\n  controlSlideout(slideoutId: string, action: \"open\" | \"close\"): this;\n\n  static controlModal(modalId: string, action: \"open\" | \"close\"): SbEventFlow;\n  controlModal(modalId: string, action: \"open\" | \"close\"): this;\n\n  static controlTimer(\n    timerId: string,\n    action: \"start\" | \"stop\" | \"toggle\",\n  ): SbEventFlow;\n  controlTimer(timerId: string, action: \"start\" | \"stop\" | \"toggle\"): this;\n\n  // API methods\n  static runApis(\n    apis: SbApi[],\n    onSuccess?: SbEventFlow,\n    onError?: SbEventFlow,\n  ): SbEventFlow;\n  runApis(apis: SbApi[], onSuccess?: SbEventFlow, onError?: SbEventFlow): this;\n\n  static cancelApis(apiNames: string[], onCancel?: SbEventFlow): SbEventFlow;\n  cancelApis(apiNames: string[], onCancel?: SbEventFlow): this;\n\n  // Component and state manipulation\n  static resetComponent(\n    widget: { id: string },\n    propertyName: string,\n    resetChildren: boolean,\n  ): SbEventFlow;\n  resetComponent(\n    widget: { id: string },\n    propertyName: string,\n    resetChildren: boolean,\n  ): this;\n\n  static resetStateVar(state: { name: string }): SbEventFlow;\n  resetStateVar(state: { name: string }): this;\n\n  static setStateVar(name: string, value: any): SbEventFlow;\n  setStateVar(name: string, value: any): this;\n\n  static setComponentProperty(\n    widget: { id: string },\n    propertyName: string,\n    value: any,\n  ): SbEventFlow;\n  setComponentProperty(\n    widget: { id: string },\n    propertyName: string,\n    value: any,\n  ): this;\n\n  // Utility methods\n  static showAlert(\n    message: string,\n    alertType: \"info\" | \"success\" | \"warning\" | \"error\",\n  ): SbEventFlow;\n  showAlert(\n    message: string,\n    alertType: \"info\" | \"success\" | \"warning\" | \"error\",\n  ): this;\n\n  static setProfile(\n    profileId: string,\n    profileAction: \"set\" | \"unset\",\n  ): SbEventFlow;\n  setProfile(profileId: string, profileAction: \"set\" | \"unset\"): this;\n\n  static triggerEvent(\n    eventName: string,\n    eventData: Record<string, string>,\n  ): SbEventFlow;\n  triggerEvent(eventName: string, eventData: Record<string, string>): this;\n}\n```\n";
+//# sourceMappingURL=SbEventFlow.d.ts.map

package/dist/ai-service/prompts/generated/library-typedefs/SbEventFlow.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"SbEventFlow.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/SbEventFlow.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,4zGAA4zG,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/SbEventFlow.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from SbEventFlow.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.009Z
+export const content = "## SbEventFlow\n\nThe `SbEventFlow` class is used to define responses to events triggered on components (like onClick) in Superblocks. It has a number of methods that can be chained together.\n\n```typescript\nclass SbEventFlow {\n  // Run custom JavaScript code\n  static runJS(\n    handler: (s: ScopedState, additionalProps?: Record<string, any>) => void,\n  ): SbEventFlow;\n  runJS(\n    handler: (s: ScopedState, additionalProps?: Record<string, any>) => void,\n  ): this;\n\n  // Navigation methods\n  static navigateTo(props: { url: string; newWindow?: boolean }): SbEventFlow;\n  navigateTo(props: { url: string; newWindow?: boolean }): this;\n\n  static navigateToApp(appId: string): SbEventFlow;\n  navigateToApp(appId: string): this;\n\n  static navigateToRoute(route: string): SbEventFlow;\n  navigateToRoute(route: string): this;\n\n  static setQueryParams(\n    params: Record<string, string>,\n    keepQueryParams?: boolean,\n  ): SbEventFlow;\n  setQueryParams(\n    params: Record<string, string>,\n    keepQueryParams?: boolean,\n  ): this;\n\n  // Control UI components\n  static controlSlideout(\n    slideoutId: string,\n    action: \"open\" | \"close\",\n  ): SbEventFlow;\n  controlSlideout(slideoutId: string, action: \"open\" | \"close\"): this;\n\n  static controlModal(modalId: string, action: \"open\" | \"close\"): SbEventFlow;\n  controlModal(modalId: string, action: \"open\" | \"close\"): this;\n\n  static controlTimer(\n    timerId: string,\n    action: \"start\" | \"stop\" | \"toggle\",\n  ): SbEventFlow;\n  controlTimer(timerId: string, action: \"start\" | \"stop\" | \"toggle\"): this;\n\n  // API methods\n  static runApis(\n    apis: SbApi[],\n    onSuccess?: SbEventFlow,\n    onError?: SbEventFlow,\n  ): SbEventFlow;\n  runApis(apis: SbApi[], onSuccess?: SbEventFlow, onError?: SbEventFlow): this;\n\n  static cancelApis(apiNames: string[], onCancel?: SbEventFlow): SbEventFlow;\n  cancelApis(apiNames: string[], onCancel?: SbEventFlow): this;\n\n  // Component and state manipulation\n  static resetComponent(\n    widget: { id: string },\n    propertyName: string,\n    resetChildren: boolean,\n  ): SbEventFlow;\n  resetComponent(\n    widget: { id: string },\n    propertyName: string,\n    resetChildren: boolean,\n  ): this;\n\n  static resetStateVar(state: { name: string }): SbEventFlow;\n  resetStateVar(state: { name: string }): this;\n\n  static setStateVar(name: string, value: any): SbEventFlow;\n  setStateVar(name: string, value: any): this;\n\n  static setComponentProperty(\n    widget: { id: string },\n    propertyName: string,\n    value: any,\n  ): SbEventFlow;\n  setComponentProperty(\n    widget: { id: string },\n    propertyName: string,\n    value: any,\n  ): this;\n\n  // Utility methods\n  static showAlert(\n    message: string,\n    alertType: \"info\" | \"success\" | \"warning\" | \"error\",\n  ): SbEventFlow;\n  showAlert(\n    message: string,\n    alertType: \"info\" | \"success\" | \"warning\" | \"error\",\n  ): this;\n\n  static setProfile(\n    profileId: string,\n    profileAction: \"set\" | \"unset\",\n  ): SbEventFlow;\n  setProfile(profileId: string, profileAction: \"set\" | \"unset\"): this;\n\n  static triggerEvent(\n    eventName: string,\n    eventData: Record<string, string>,\n  ): SbEventFlow;\n  triggerEvent(eventName: string, eventData: Record<string, string>): this;\n}\n```\n";
+//# sourceMappingURL=SbEventFlow.js.map

package/dist/ai-service/prompts/generated/library-typedefs/SbEventFlow.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"SbEventFlow.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/SbEventFlow.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,qCAAqC;AACrC,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,yzGAAyzG,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/index.d.ts

@@ -0,0 +1,3 @@
+export { content as Dim } from "./Dim.js";
+export { content as SbEventFlow } from "./SbEventFlow.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/ai-service/prompts/generated/library-typedefs/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/index.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,OAAO,IAAI,GAAG,EAAE,MAAM,UAAU,CAAC;AAC1C,OAAO,EAAE,OAAO,IAAI,WAAW,EAAE,MAAM,kBAAkB,CAAC"}

package/dist/ai-service/prompts/generated/library-typedefs/index.js

@@ -0,0 +1,5 @@
+// Auto-generated sub-index
+// Do not edit this file directly
+export { content as Dim } from "./Dim.js";
+export { content as SbEventFlow } from "./SbEventFlow.js";
+//# sourceMappingURL=index.js.map

package/dist/ai-service/prompts/generated/library-typedefs/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/library-typedefs/index.ts"],"names":[],"mappings":"AAAA,2BAA2B;AAC3B,iCAAiC;AAEjC,OAAO,EAAE,OAAO,IAAI,GAAG,EAAE,MAAM,UAAU,CAAC;AAC1C,OAAO,EAAE,OAAO,IAAI,WAAW,EAAE,MAAM,kBAAkB,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/index.d.ts

@@ -0,0 +1,11 @@
+export { content as superblocks_api } from "./superblocks-api.js";
+export { content as superblocks_components_rules } from "./superblocks-components-rules.js";
+export { content as superblocks_custom_components } from "./superblocks-custom-components.js";
+export { content as superblocks_event_flow } from "./superblocks-event-flow.js";
+export { content as superblocks_layouts } from "./superblocks-layouts.js";
+export { content as superblocks_page } from "./superblocks-page.js";
+export { content as superblocks_routes } from "./superblocks-routes.js";
+export { content as superblocks_state } from "./superblocks-state.js";
+export { content as superblocks_theming } from "./superblocks-theming.js";
+export { content as system } from "./system.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/index.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,4BAA4B,EAAE,MAAM,mCAAmC,CAAC;AAC5F,OAAO,EAAE,OAAO,IAAI,6BAA6B,EAAE,MAAM,oCAAoC,CAAC;AAC9F,OAAO,EAAE,OAAO,IAAI,sBAAsB,EAAE,MAAM,6BAA6B,CAAC;AAChF,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AACxE,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,MAAM,EAAE,MAAM,aAAa,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/index.js

@@ -0,0 +1,13 @@
+// Auto-generated sub-index
+// Do not edit this file directly
+export { content as superblocks_api } from "./superblocks-api.js";
+export { content as superblocks_components_rules } from "./superblocks-components-rules.js";
+export { content as superblocks_custom_components } from "./superblocks-custom-components.js";
+export { content as superblocks_event_flow } from "./superblocks-event-flow.js";
+export { content as superblocks_layouts } from "./superblocks-layouts.js";
+export { content as superblocks_page } from "./superblocks-page.js";
+export { content as superblocks_routes } from "./superblocks-routes.js";
+export { content as superblocks_state } from "./superblocks-state.js";
+export { content as superblocks_theming } from "./superblocks-theming.js";
+export { content as system } from "./system.js";
+//# sourceMappingURL=index.js.map

package/dist/ai-service/prompts/generated/subprompts/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/index.ts"],"names":[],"mappings":"AAAA,2BAA2B;AAC3B,iCAAiC;AAEjC,OAAO,EAAE,OAAO,IAAI,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAClE,OAAO,EAAE,OAAO,IAAI,4BAA4B,EAAE,MAAM,mCAAmC,CAAC;AAC5F,OAAO,EAAE,OAAO,IAAI,6BAA6B,EAAE,MAAM,oCAAoC,CAAC;AAC9F,OAAO,EAAE,OAAO,IAAI,sBAAsB,EAAE,MAAM,6BAA6B,CAAC;AAChF,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AACpE,OAAO,EAAE,OAAO,IAAI,kBAAkB,EAAE,MAAM,yBAAyB,CAAC;AACxE,OAAO,EAAE,OAAO,IAAI,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AACtE,OAAO,EAAE,OAAO,IAAI,mBAAmB,EAAE,MAAM,0BAA0B,CAAC;AAC1E,OAAO,EAAE,OAAO,IAAI,MAAM,EAAE,MAAM,aAAa,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-api.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "### APIs\n\nThe Superblocks framework allows you to create backend APIs. The high level structure for creating APIs is as follows:\n\n1. APIs are defined using TypeScript files that live inside the apis directory inside the page they are scoped to. Example: /pages/Page1/apis/myApi.ts\n2. This pattern is a declarative workflow builder, where you define each API step, its configuration, and its execution order within the API workflow.\n3. To make the API available for use, you must import it into the scope file and register it with `SbApi()`, then import and destructure it in your page component for use.\n\n#### Example of creating and then registering a Superblocks API:\n\nCRITICAL: The name of the API must be consistent across the API's TypeScript definition, the API's file name, references in page files, and the key used to register it in the scope file. See the consistent use of 'myApi' below as an example.\n\nCreate the API by adding the myApi.ts file:\n\n```ts\n// Path to this API definition: /pages/Page1/apis/myApi.ts\n\nimport { Api, JavaScript } from \"@superblocksteam/library\";\n\nexport default new Api(\"myApi\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: \"ORD-001\",\n          customerName: \"John Smith\",\n          total: 149.99,\n        },\n        {\n          id: \"ORD-002\",\n          customerName: \"Sarah Jones\",\n          total: 89.5,\n        },\n      ];\n    },\n  }),\n]);\n```\n\nThen register the myApi API in the scope file:\n\n```ts\n// /pages/Page1/scope.ts\nimport { createSbScope, SbApi } from \"@superblocksteam/library\";\n\nexport const Page1Scope = createSbScope(\n  () => ({\n    // Register the API in the scope\n    myApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\nThen use the API in your page component:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport {\n  SbPage,\n  SbButton,\n  SbTable,\n  sbComputed,\n  SbEventFlow,\n} from \"@superblocksteam/library\";\nimport { registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  // Destructure the API from the scope entities to access its response\n  const { myApi } = Page1;\n\n  return (\n    <SbPage>\n      <SbButton\n        // APIs can be invoked with the SbEventFlow API\n        onClick={SbEventFlow.runApis([myApi])}\n        label=\"Fetch Data\"\n      />\n      {/* Access API response using sbComputed */}\n      <SbTable tableData={sbComputed(() => myApi.response)} />\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n#### Example 2: API where a step references the output of a previous step\n\nThink hard about how you access the output of previous steps. You MUST use the output property of the previous step variable. There is no other way to access the output of a previous step (other than using a Variable block, but that is not what you want in this case and should only be used in very specific cases).\n\n```ts\n// Path to this api would be: /pages/Page1/apis/getOrders.ts\n\nimport { JavaScript, Api } from \"@superblocksteam/library\";\n\nexport default new Api(\"getOrders\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: 1,\n          customer: \"John Smith\",\n          date: \"2024-01-15\",\n          total: 199.99,\n          status: \"Pending\",\n        },\n        {\n          id: 2,\n          customer: \"Jane Doe\",\n          date: \"2024-01-14\",\n          total: 149.99,\n          status: \"Shipped\",\n        },\n        {\n          id: 3,\n          customer: \"Bob Wilson\",\n          date: \"2024-01-13\",\n          total: 299.99,\n          status: \"Delivered\",\n        },\n      ];\n    },\n  }),\n  new JavaScript(\"format_orders\", {\n    fn: ({ retrieve_orders }) => {\n      return retrieve_orders.output.map((order) => ({\n        ...order,\n        date: new Date(order.date).toLocaleDateString(),\n      }));\n    },\n  }),\n]);\n```\n\nThen you would register the API in your scope file and use it in your page component:\n\n```ts\n// /pages/Page1/scope.ts\nexport const Page1Scope = createSbScope(\n  () => ({\n    getOrders: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\n// /pages/Page1/index.tsx\nimport { SbPage, SbTable, sbComputed } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const { getOrders } = Page1;\n\n  return (\n    <SbPage>\n      <SbTable tableData={sbComputed(() => getOrders.response)} />\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n#### The Superblocks API TypeScript Type\n\nBelow is the full TypeScript spec for the APIs you create:\n\n````ts\n// @superblocksteam/types\n\nexport type JsonValue =\n  | undefined\n  | null\n  | number\n  | string\n  | boolean\n  | JsonValue[]\n  | object;\nexport type State = { [key: string]: JsonValue };\nexport type Binding<T> = T | ((state: State) => T);\ntype Integrations = { id: string; description: string; metadata: JsonValue }[];\n\nclass Block {\n  constructor(name: string) {}\n  public run(): { output: JsonValue } {\n    /* ... */\n  }\n}\n\nclass Integration extends Block {\n  constructor(name: string, integration_id: string) {}\n}\n\ntype State = Record<string, JsonValue>;\n\nclass JavaScript extends Integration {\n  constructor(\n    name: string,\n    config: {\n      fn: (\n        {\n          /* ... */\n        },\n      ) => JsonValue;\n    },\n  ) {\n    super(name, \"javascript\");\n  }\n}\n\nclass Python extends Integration {\n  constructor(\n    name: string,\n    config: {\n      // We want to just put the python function body here. The scope is the same as it would be if it were a JavaScript integration.\n      fn: string;\n    },\n  ) {\n    super(name, \"python\");\n  }\n}\n\nclass Databricks extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass Snowflake extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass PostgreSQL extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass RestApi extends Integration {\n  constructor(\n    name: string,\n    config: {\n      method:\n        | \"GET\"\n        | \"POST\"\n        | \"PUT\"\n        | \"DELETE\"\n        | \"PATCH\"\n        | \"OPTIONS\"\n        | \"HEAD\"\n        | \"TRACE\"\n        | \"CONNECT\";\n      url:\n        | string\n        | ((\n            {\n              /* ... */\n            },\n          ) => string);\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Email extends Integration {\n  constructor(\n    name: string,\n    config: {\n      from: Binding<string>;\n      to: Binding<string>;\n      subject: Binding<string>;\n      cc?: Binding<string>;\n      bcc?: Binding<string>;\n      body?: Binding<string>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nexport type Condition = {\n  when: boolean | ((state: State) => boolean);\n  then: Block[];\n};\n\nexport type Conditions = {\n  if: Condition;\n  elif?: Condition[];\n  else?: Block[];\n};\n\nclass Conditional extends Block {\n  constructor(name: string, config: Conditions) {\n    super(name);\n  }\n}\n\nclass TryCatch extends Block {\n  constructor(\n    name: string,\n    config: {\n      try: Block[];\n      catch: Block[];\n      finally?: Block[];\n      variables: { error: string };\n    },\n  ) {\n    super(name);\n  }\n}\n\n/**\n * A Superblocks variable has the following access pattern:\n *\n * How to retrieve the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.value\n *\n * // INCORRECT\n * my_variable\n * ```\n *\n * How to set the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.set(value)\n *\n * // INCORRECT\n * my_variable = value\n * ```\n *\n */\n\nclass Variables extends Block {\n  constructor(\n    name: string,\n    variables: {\n      // The name of the variable.\n      key: string;\n      // The value of the variable.\n      value: Binding<JsonValue>;\n    }[],\n  ) {\n    super(name);\n  }\n}\n\nclass Loop extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n        // What the variable name for the current index is.\n        index: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Parallel extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Throw extends Block {\n  constructor(\n    name: string,\n    config: {\n      error: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Return extends Block {\n  constructor(\n    name: string,\n    config: {\n      data: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Api {\n  constructor(name: string, steps: Block[]) {}\n  public get response(): JsonValue {\n    /* ... */\n  }\n  public get error(): string | undefined {\n    /* ... */\n  }\n  public run(): void {\n    /* ... */\n  }\n  public cancel(): void {\n    /* ... */\n  }\n}\n````\n\n#### Example Usage\n\nBelow are examples of how you create Superblocks APIs, along with annotations to describe different pieces of functinality and expectations.\n\n##### Example 1: Simple API with conditional\n\n```ts\n// Path to this api would be: /pages/Page1/apis/getOrders.ts\n\nimport {\n  Conditional,\n  Condition,\n  PostgreSQL,\n  JavaScript,\n  Api,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"getOrders\", [\n  new Conditional(\"my_conditional\", {\n    if: {\n      when: true,\n      then: [\n        new PostgreSQL(\n          \"retrieve_orders\",\n          \"\" /* <- integration uuid goes here */,\n          {\n            statement: \"SELECT * FROM orders\",\n          },\n        ),\n      ],\n    },\n    else: [\n      new JavaScript(\"fallthrough\", {\n        fn: () => \"we did not execute the sql query\",\n      }),\n    ],\n  }),\n]);\n```\n\nTo run register and run the API we defined above:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport { SbPage, SbApi, SbTable, SbButton } from \"@superblocksteam/library\";\nimport { registerPage, showAlert } from \"@superblocksteam/library\";\n\nimport getOrders from \"./apis/getOrders\";\n\nconst Page1 = () => (\n  <SbPage>\n    <SbButton\n      // APIs can be invoked with the SBEventFlow API.\n      onClick={SbEventFlow.runApis([getOrders])}\n    />\n    // ...\n    <SbTable>\n      // APIs are part of the state object just like components. tableData=\n      {(state) => state.getOrders.response}\n    </SbTable>\n  </SbPage>\n);\n\nexport default registerPage(Page1, {\n  name: \"MyPage\",\n  // You register APIs just like you would SbVariables.\n  getOrders: SbApi(getOrders),\n});\n```\n\n#### Rules for using Superblocks APIs\n\nThink hard about the following important rules for correctly using Superblocks APIs:\n\n- You MUST use a destructured state object as the function parameter for dynamic block fields. The valid keys are (1) Superblocks entities (components, variables, etc) and (2) previous block outputs that are in the lexical scope. Example below:\n\n```ts\n// CORRECT: uses destructured state\n({ Dropdown1, TextInput1 }) => Dropdown1.selectedOptionsValue + TextInput1.value\n\n// INCORRECT: uses state object directly\n(state) => state.Dropdown1.selectedOptionsValue + state.TextInput1.value\n```\n\n- The result of each scope is the result of the last block in that scope. In the following example, the value of `sendEmail.response` is the result of the `return_summary` block. Use this information to carefully ensure that the last block in your API is the one that returns the value you want.\n\n```ts\nexport default new Api(\"sendEmail\", [\n  new Email(\"send_email\", {\n    from: \"noreply@company.com\",\n    to: \"test@test.com\",\n    subject: \"Test Email\",\n    body: \"This is a test email\",\n  }),\n  new JavaScript(\"return_summary\", {\n    fn: () => \"Email sent successfully!\",\n  }),\n]);\n```\n\n```tsx\nconst scope = createSbScope<{\n  Table1: any;\n}>({ sendEmail: SbApi({}) }, { name: \"Page1\" });\n\nexport default registerPage(\n  () => (\n    <SbPage /* ... */>\n      // ...\n      <SbTable\n        bind={scope.entities.Table1}\n        tableData={sbComputed(() => API1.response)}\n      />\n      // ...\n    </SbPage>\n  ),\n  scope,\n);\n```\n\n- Block outputs are immutable. Do not mutate the output of a block.\n\n- Do not reference variables that are not in scope. The ONLY things in scope in an API block are the outputs of previous steps and the state object.\n\n- Backend APIs CANNOT mutate frontend state inside of the API\n\n- APIs are registered in scope files using `SbApi()` and then accessed in page components by destructuring from the scope entities. Make sure you name the key used in registerScope the same as the imported API, but do not pass the imported Api into the SbApi() call.\n\n- To access API responses in your UI, use `sbComputed(() => apiName.response)` or `sbComputed(() => apiName.error)`.\n\n- You will not always be told which integrations to use in your API; you will have to determine that yourself based on the data you need to fetch.\n\n- Never add comments to code you (the ai) generate. User added comments are fine - leave those!\n";
+//# sourceMappingURL=superblocks-api.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-api.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-api.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-api.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,kkdAAkkd,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-api.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-api.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.006Z
+export const content = "### APIs\n\nThe Superblocks framework allows you to create backend APIs. The high level structure for creating APIs is as follows:\n\n1. APIs are defined using TypeScript files that live inside the apis directory inside the page they are scoped to. Example: /pages/Page1/apis/myApi.ts\n2. This pattern is a declarative workflow builder, where you define each API step, its configuration, and its execution order within the API workflow.\n3. To make the API available for use, you must import it into the scope file and register it with `SbApi()`, then import and destructure it in your page component for use.\n\n#### Example of creating and then registering a Superblocks API:\n\nCRITICAL: The name of the API must be consistent across the API's TypeScript definition, the API's file name, references in page files, and the key used to register it in the scope file. See the consistent use of 'myApi' below as an example.\n\nCreate the API by adding the myApi.ts file:\n\n```ts\n// Path to this API definition: /pages/Page1/apis/myApi.ts\n\nimport { Api, JavaScript } from \"@superblocksteam/library\";\n\nexport default new Api(\"myApi\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: \"ORD-001\",\n          customerName: \"John Smith\",\n          total: 149.99,\n        },\n        {\n          id: \"ORD-002\",\n          customerName: \"Sarah Jones\",\n          total: 89.5,\n        },\n      ];\n    },\n  }),\n]);\n```\n\nThen register the myApi API in the scope file:\n\n```ts\n// /pages/Page1/scope.ts\nimport { createSbScope, SbApi } from \"@superblocksteam/library\";\n\nexport const Page1Scope = createSbScope(\n  () => ({\n    // Register the API in the scope\n    myApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\nThen use the API in your page component:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport {\n  SbPage,\n  SbButton,\n  SbTable,\n  sbComputed,\n  SbEventFlow,\n} from \"@superblocksteam/library\";\nimport { registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  // Destructure the API from the scope entities to access its response\n  const { myApi } = Page1;\n\n  return (\n    <SbPage>\n      <SbButton\n        // APIs can be invoked with the SbEventFlow API\n        onClick={SbEventFlow.runApis([myApi])}\n        label=\"Fetch Data\"\n      />\n      {/* Access API response using sbComputed */}\n      <SbTable tableData={sbComputed(() => myApi.response)} />\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n#### Example 2: API where a step references the output of a previous step\n\nThink hard about how you access the output of previous steps. You MUST use the output property of the previous step variable. There is no other way to access the output of a previous step (other than using a Variable block, but that is not what you want in this case and should only be used in very specific cases).\n\n```ts\n// Path to this api would be: /pages/Page1/apis/getOrders.ts\n\nimport { JavaScript, Api } from \"@superblocksteam/library\";\n\nexport default new Api(\"getOrders\", [\n  new JavaScript(\"retrieve_orders\", {\n    fn: () => {\n      return [\n        {\n          id: 1,\n          customer: \"John Smith\",\n          date: \"2024-01-15\",\n          total: 199.99,\n          status: \"Pending\",\n        },\n        {\n          id: 2,\n          customer: \"Jane Doe\",\n          date: \"2024-01-14\",\n          total: 149.99,\n          status: \"Shipped\",\n        },\n        {\n          id: 3,\n          customer: \"Bob Wilson\",\n          date: \"2024-01-13\",\n          total: 299.99,\n          status: \"Delivered\",\n        },\n      ];\n    },\n  }),\n  new JavaScript(\"format_orders\", {\n    fn: ({ retrieve_orders }) => {\n      return retrieve_orders.output.map((order) => ({\n        ...order,\n        date: new Date(order.date).toLocaleDateString(),\n      }));\n    },\n  }),\n]);\n```\n\nThen you would register the API in your scope file and use it in your page component:\n\n```ts\n// /pages/Page1/scope.ts\nexport const Page1Scope = createSbScope(\n  () => ({\n    getOrders: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\n// /pages/Page1/index.tsx\nimport { SbPage, SbTable, sbComputed } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  const { getOrders } = Page1;\n\n  return (\n    <SbPage>\n      <SbTable tableData={sbComputed(() => getOrders.response)} />\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\n#### The Superblocks API TypeScript Type\n\nBelow is the full TypeScript spec for the APIs you create:\n\n````ts\n// @superblocksteam/types\n\nexport type JsonValue =\n  | undefined\n  | null\n  | number\n  | string\n  | boolean\n  | JsonValue[]\n  | object;\nexport type State = { [key: string]: JsonValue };\nexport type Binding<T> = T | ((state: State) => T);\ntype Integrations = { id: string; description: string; metadata: JsonValue }[];\n\nclass Block {\n  constructor(name: string) {}\n  public run(): { output: JsonValue } {\n    /* ... */\n  }\n}\n\nclass Integration extends Block {\n  constructor(name: string, integration_id: string) {}\n}\n\ntype State = Record<string, JsonValue>;\n\nclass JavaScript extends Integration {\n  constructor(\n    name: string,\n    config: {\n      fn: (\n        {\n          /* ... */\n        },\n      ) => JsonValue;\n    },\n  ) {\n    super(name, \"javascript\");\n  }\n}\n\nclass Python extends Integration {\n  constructor(\n    name: string,\n    config: {\n      // We want to just put the python function body here. The scope is the same as it would be if it were a JavaScript integration.\n      fn: string;\n    },\n  ) {\n    super(name, \"python\");\n  }\n}\n\nclass Databricks extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass Snowflake extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass PostgreSQL extends Integration {\n  static integrations: Integrations = [\n    /* ... */\n  ];\n\n  /**\n   * @param {string} name           The name of the block.\n   * @param {string} integration_id The id of the integration.\n   * @param {object} config         The config object.\n   * @returns {void}\n   */\n  constructor(\n    name: string,\n    integration_id: string,\n    config: {\n      statement: Binding<string>;\n    },\n  ) {\n    super(name, integration_id);\n  }\n}\n\nclass RestApi extends Integration {\n  constructor(\n    name: string,\n    config: {\n      method:\n        | \"GET\"\n        | \"POST\"\n        | \"PUT\"\n        | \"DELETE\"\n        | \"PATCH\"\n        | \"OPTIONS\"\n        | \"HEAD\"\n        | \"TRACE\"\n        | \"CONNECT\";\n      url:\n        | string\n        | ((\n            {\n              /* ... */\n            },\n          ) => string);\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Email extends Integration {\n  constructor(\n    name: string,\n    config: {\n      from: Binding<string>;\n      to: Binding<string>;\n      subject: Binding<string>;\n      cc?: Binding<string>;\n      bcc?: Binding<string>;\n      body?: Binding<string>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nexport type Condition = {\n  when: boolean | ((state: State) => boolean);\n  then: Block[];\n};\n\nexport type Conditions = {\n  if: Condition;\n  elif?: Condition[];\n  else?: Block[];\n};\n\nclass Conditional extends Block {\n  constructor(name: string, config: Conditions) {\n    super(name);\n  }\n}\n\nclass TryCatch extends Block {\n  constructor(\n    name: string,\n    config: {\n      try: Block[];\n      catch: Block[];\n      finally?: Block[];\n      variables: { error: string };\n    },\n  ) {\n    super(name);\n  }\n}\n\n/**\n * A Superblocks variable has the following access pattern:\n *\n * How to retrieve the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.value\n *\n * // INCORRECT\n * my_variable\n * ```\n *\n * How to set the value of a variable:\n * ```ts\n * CORRECT\n * my_variable.set(value)\n *\n * // INCORRECT\n * my_variable = value\n * ```\n *\n */\n\nclass Variables extends Block {\n  constructor(\n    name: string,\n    variables: {\n      // The name of the variable.\n      key: string;\n      // The value of the variable.\n      value: Binding<JsonValue>;\n    }[],\n  ) {\n    super(name);\n  }\n}\n\nclass Loop extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n        // What the variable name for the current index is.\n        index: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Parallel extends Block {\n  constructor(\n    name: string,\n    config: {\n      over: Binding<JsonValue[]>;\n      variables: {\n        // What the variable name for the current item is.\n        item: string;\n      };\n      blocks: Block[];\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Throw extends Block {\n  constructor(\n    name: string,\n    config: {\n      error: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Return extends Block {\n  constructor(\n    name: string,\n    config: {\n      data: Binding<JsonValue>;\n    },\n  ) {\n    super(name);\n  }\n}\n\nclass Api {\n  constructor(name: string, steps: Block[]) {}\n  public get response(): JsonValue {\n    /* ... */\n  }\n  public get error(): string | undefined {\n    /* ... */\n  }\n  public run(): void {\n    /* ... */\n  }\n  public cancel(): void {\n    /* ... */\n  }\n}\n````\n\n#### Example Usage\n\nBelow are examples of how you create Superblocks APIs, along with annotations to describe different pieces of functinality and expectations.\n\n##### Example 1: Simple API with conditional\n\n```ts\n// Path to this api would be: /pages/Page1/apis/getOrders.ts\n\nimport {\n  Conditional,\n  Condition,\n  PostgreSQL,\n  JavaScript,\n  Api,\n} from \"@superblocksteam/library\";\n\nexport default new Api(\"getOrders\", [\n  new Conditional(\"my_conditional\", {\n    if: {\n      when: true,\n      then: [\n        new PostgreSQL(\n          \"retrieve_orders\",\n          \"\" /* <- integration uuid goes here */,\n          {\n            statement: \"SELECT * FROM orders\",\n          },\n        ),\n      ],\n    },\n    else: [\n      new JavaScript(\"fallthrough\", {\n        fn: () => \"we did not execute the sql query\",\n      }),\n    ],\n  }),\n]);\n```\n\nTo run register and run the API we defined above:\n\n```tsx\n// /pages/Page1/index.tsx\n\nimport { SbPage, SbApi, SbTable, SbButton } from \"@superblocksteam/library\";\nimport { registerPage, showAlert } from \"@superblocksteam/library\";\n\nimport getOrders from \"./apis/getOrders\";\n\nconst Page1 = () => (\n  <SbPage>\n    <SbButton\n      // APIs can be invoked with the SBEventFlow API.\n      onClick={SbEventFlow.runApis([getOrders])}\n    />\n    // ...\n    <SbTable>\n      // APIs are part of the state object just like components. tableData=\n      {(state) => state.getOrders.response}\n    </SbTable>\n  </SbPage>\n);\n\nexport default registerPage(Page1, {\n  name: \"MyPage\",\n  // You register APIs just like you would SbVariables.\n  getOrders: SbApi(getOrders),\n});\n```\n\n#### Rules for using Superblocks APIs\n\nThink hard about the following important rules for correctly using Superblocks APIs:\n\n- You MUST use a destructured state object as the function parameter for dynamic block fields. The valid keys are (1) Superblocks entities (components, variables, etc) and (2) previous block outputs that are in the lexical scope. Example below:\n\n```ts\n// CORRECT: uses destructured state\n({ Dropdown1, TextInput1 }) => Dropdown1.selectedOptionsValue + TextInput1.value\n\n// INCORRECT: uses state object directly\n(state) => state.Dropdown1.selectedOptionsValue + state.TextInput1.value\n```\n\n- The result of each scope is the result of the last block in that scope. In the following example, the value of `sendEmail.response` is the result of the `return_summary` block. Use this information to carefully ensure that the last block in your API is the one that returns the value you want.\n\n```ts\nexport default new Api(\"sendEmail\", [\n  new Email(\"send_email\", {\n    from: \"noreply@company.com\",\n    to: \"test@test.com\",\n    subject: \"Test Email\",\n    body: \"This is a test email\",\n  }),\n  new JavaScript(\"return_summary\", {\n    fn: () => \"Email sent successfully!\",\n  }),\n]);\n```\n\n```tsx\nconst scope = createSbScope<{\n  Table1: any;\n}>({ sendEmail: SbApi({}) }, { name: \"Page1\" });\n\nexport default registerPage(\n  () => (\n    <SbPage /* ... */>\n      // ...\n      <SbTable\n        bind={scope.entities.Table1}\n        tableData={sbComputed(() => API1.response)}\n      />\n      // ...\n    </SbPage>\n  ),\n  scope,\n);\n```\n\n- Block outputs are immutable. Do not mutate the output of a block.\n\n- Do not reference variables that are not in scope. The ONLY things in scope in an API block are the outputs of previous steps and the state object.\n\n- Backend APIs CANNOT mutate frontend state inside of the API\n\n- APIs are registered in scope files using `SbApi()` and then accessed in page components by destructuring from the scope entities. Make sure you name the key used in registerScope the same as the imported API, but do not pass the imported Api into the SbApi() call.\n\n- To access API responses in your UI, use `sbComputed(() => apiName.response)` or `sbComputed(() => apiName.error)`.\n\n- You will not always be told which integrations to use in your API; you will have to determine that yourself based on the data you need to fetch.\n\n- Never add comments to code you (the ai) generate. User added comments are fine - leave those!\n";
+//# sourceMappingURL=superblocks-api.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-api.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-api.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-api.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,yCAAyC;AACzC,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,+jdAA+jd,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-components-rules.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "### Rules for using Superblocks components:\n\n- ENSURE THAT ALL PROPERTY VALUES COMPLY WITH THE SUPPLIED TYPES FOR EACH PROPERTY\n- NEVER use a component in this section in a custom component\n- SbModal components DO NOT need to have their own close button. The modal component comes with a close button by default.\n\nNOTES:\n\n- When you see _Border_, it's {width: Dim, style: string, color: string}\n- When you see _TextStyle_, it's a plain JS object with the following properties:\n  - variant: \"heading1\" | \"heading2\" | \"heading3\" | \"heading4\" | \"heading5\" | \"body1\" | \"body2\" | \"body3\" | \"label\" | \"inputLabel\" | \"code\"\n  - textColor: an object with only the following properties:\n    - default: string // the text color to use. A color value from the theme, or a hex code if necessary. ALWAYS wrap this property in sbComputed. Example: sbComputed(() => Theme.colors.neutral900), and remember to import sbComputed and globals from the library: import { sbComputed,Theme } from '@superblocksteam/library';\n- When you see _SbEventFlow_, use the SbEventFlow builder\n- Import all components you use from '@superblocksteam/library'; Example: `import { SbContainer, SbButton, sbComputed, ... } from '@superblocksteam/library';` If you don't import all components you use, the app will crash!\n- Don't add props to the Page component other than onLoad\n- SbContainer has a default style of \"card\" if you want to remove the style, set the style to \"none\"\n- When using dynamic values in component props, use `sbComputed` with the correct pattern:\n  - For scope entities (variables, APIs): `sbComputed(() => entityName.value)` (direct access)\n  - For bound components: `sbComputed(() => ComponentName.property)` (direct access after binding)\n  - For global access: `sbComputed(() => Global.user.name)` or `sbComputed(() => Theme.colors.primary)` (import globals from the library first: `import { Global, Theme, Embed, Env } from '@superblocksteam/library';`)\n- Use sbComputed ONLY when the value references dynamic data (state variables, API responses, component values, or theme)\n- Do NOT use sbComputed for static configuration like table columns, static dropdown options, or style objects that don't reference theme\n";
+//# sourceMappingURL=superblocks-components-rules.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-components-rules.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-components-rules.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-components-rules.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,ktEAAktE,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-components-rules.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-components-rules.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "### Rules for using Superblocks components:\n\n- ENSURE THAT ALL PROPERTY VALUES COMPLY WITH THE SUPPLIED TYPES FOR EACH PROPERTY\n- NEVER use a component in this section in a custom component\n- SbModal components DO NOT need to have their own close button. The modal component comes with a close button by default.\n\nNOTES:\n\n- When you see _Border_, it's {width: Dim, style: string, color: string}\n- When you see _TextStyle_, it's a plain JS object with the following properties:\n  - variant: \"heading1\" | \"heading2\" | \"heading3\" | \"heading4\" | \"heading5\" | \"body1\" | \"body2\" | \"body3\" | \"label\" | \"inputLabel\" | \"code\"\n  - textColor: an object with only the following properties:\n    - default: string // the text color to use. A color value from the theme, or a hex code if necessary. ALWAYS wrap this property in sbComputed. Example: sbComputed(() => Theme.colors.neutral900), and remember to import sbComputed and globals from the library: import { sbComputed,Theme } from '@superblocksteam/library';\n- When you see _SbEventFlow_, use the SbEventFlow builder\n- Import all components you use from '@superblocksteam/library'; Example: `import { SbContainer, SbButton, sbComputed, ... } from '@superblocksteam/library';` If you don't import all components you use, the app will crash!\n- Don't add props to the Page component other than onLoad\n- SbContainer has a default style of \"card\" if you want to remove the style, set the style to \"none\"\n- When using dynamic values in component props, use `sbComputed` with the correct pattern:\n  - For scope entities (variables, APIs): `sbComputed(() => entityName.value)` (direct access)\n  - For bound components: `sbComputed(() => ComponentName.property)` (direct access after binding)\n  - For global access: `sbComputed(() => Global.user.name)` or `sbComputed(() => Theme.colors.primary)` (import globals from the library first: `import { Global, Theme, Embed, Env } from '@superblocksteam/library';`)\n- Use sbComputed ONLY when the value references dynamic data (state variables, API responses, component values, or theme)\n- Do NOT use sbComputed for static configuration like table columns, static dropdown options, or style objects that don't reference theme\n";
+//# sourceMappingURL=superblocks-components-rules.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-components-rules.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-components-rules.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-components-rules.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,sDAAsD;AACtD,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,+sEAA+sE,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-custom-components.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Custom Components\n\n- ULTRA CRITICAL: NEVER use Superblocks components in a custom component.\n\n- CRITICAL: Use custom components sparingly.\n\n- CRITICAL: ONLY when all else fails and a component is not available in the Superblocks library, you may construct it out of external component libraries by installing them.\n\n- CRITICAL: ALWAYS import React using a namespace import: `import * as React from 'react'`.\n\nIn order to hook it up correctly, the platform needs to know what props the component exposes, their types, default values, and how they should be displayed to users.\n\nTo do this, you use the **`Prop` API** and **`registerComponent`** function.\n\n## Key Concepts\n\n- All custom components should live within the `components/` folder.\n- **`Prop`**: Defines a single editable property for your component.\n  - Can specify the data type (`string`, `number`, `boolean`, `event`, etc.).\n  - Can define a **default value**, **label** for the properties panel, and other validations.\n- **`registerComponent`**: Connects your React component with its editable schema (`properties`) so it appears correctly in the visual editor.\n- **`useUpdateProperties`**: A hook that lets your component programmatically update its properties during runtime (e.g., when a user interacts with it).\n\n---\n\n## Basic Example\n\n```tsx\nimport { Rate } from \"antd\";\nimport {\n  CustomComponentProps,\n  Prop,\n  registerComponent,\n  useUpdateProperties,\n} from \"@superblocksteam/library\";\n\n// 1. Define editable properties\nconst properties = {\n  value: Prop.number()\n    .default(3) // Default to 3 stars\n    .propertiesPanel({ label: \"Default value\" }), // Editor label\n  onChange: Prop.event().propertiesPanel({ label: \"On change\" }), // Editor label for event\n};\n\n// 2. Create typed props for your component\ntype ComponentProps = CustomComponentProps<typeof properties>;\n\n// 3. Build your React component\nconst Rating = ({ value, onChange }: ComponentProps) => {\n  const updateProperties = useUpdateProperties(); // Hook to update properties dynamically\n\n  return (\n    <div style={{ display: \"flex\" }}>\n      <Rate\n        value={value}\n        defaultValue={value}\n        onChange={(newValue) => {\n          updateProperties({ value: newValue }); // Update visual editor\n          onChange?.(); // Trigger custom event\n        }}\n      />\n    </div>\n  );\n};\n\n// 4. Register your component to make it available in the visual editor\nexport default registerComponent(\"Rating\", properties, Rating);\n```\n\n---\n\n## How `Prop` Works\n\nYou can define different types of props:\n\n- **`string`**: `Prop.string()`\n- **`number`**: `Prop.number()`\n- **`boolean`**: `Prop.boolean()`\n- **`event`**: `Prop.event()` (for user interactions like clicks)\n- **`any`**: `Prop.any()` (for any type)\n- **`composite`**: `Prop.composite({ x: Prop.number(), y: Prop.number() })` (for nested objects)\n- **`record`**: `Prop.record({...})` (for key-value maps)\n- **`union`**: `Prop.union({...})` (for multiple variants)\n\nYou can chain additional methods:\n\n- `.default(value)` \u2014 Sets a default value.\n- `.propertiesPanel({ label: \"Your Label\" })` \u2014 Controls how the prop appears in the editor.\n- `.validate(fn)` \u2014 Adds custom validation logic.\n- `.readable()`, `.writable()` \u2014 Control read/write capabilities.\n\n---\n\n## Typical Flow\n\n1. **Define** the **editable schema** (`properties`) with `Prop`.\n2. **Type** your component's props using `CustomComponentProps`.\n3. **Use** `useUpdateProperties` to sync UI interactions back to the editor.\n4. **Register** the component using `registerComponent`.\n\n---# Tips\n\n- All `registeredComponent`s automatically support width and height using the `Dim` object.\n  ```\n  <CustomSlider\n    width={Dim.fill(2)} // Fill available space with a weight of 2\n    height={Dim.px(100)} // Fixed height of 100 pixels\n  />\n  ```\n\n## When not to use custom components\n\n- If a user asks for something by name, like showing \"metrics\", and you do not find a \"metrics\" component in the Superblocks library, do not immediately assume you need to use a custom component. Instead consider using one of the pre-designed templates built from existing Superblocks components.\n\n## Pre-designed templates to use instead of custom components\n\n### Rules for using pre-designed templates\n\n- Use the pre-designed templates as a base to work from. You can make changes to the content, but generally you do not need to change the layout or styling. Example: below there are width and height properties set on the icons and you should NOT change these or you will break the layout.\n\n### Metrics template\n\nThis template is a row of three large numerical metrics with icons and annotation text.\n\nTemplate code below and a few notes to help explain usage:\n\n- We use the SbContainer component to layout the metrics in a row\n- We use the SbText component to show the numerical values and how we use the textStyle prop variant to make the text a big heading\n- We use the SbIcon component to show nice icons that make sense for the metric\n- We create a little \"badge\" using the SbContainer component to show small annotation text. Prefer this over using brackets in the main heading text. Example: Rather than \"32 (2m)\" we use \"32\" in the main heading text and then a badge with the \"2m\" text\n- Keep the icon sizing you see in this template unless you are explicitly asked to change it\n\n```tsx\nimport {\n  SbIcon,\n  SbText,\n  SbContainer,\n  sbComputed,\n  Dim,\n  Global,\n  Theme,\n  Embed,\n  Env,\n} from \"@superblocksteam/library\";\n\n<SbContainer\n  layout=\"horizontal\"\n  width={Dim.fill()}\n  height={Dim.fit()}\n  variant=\"none\"\n  spacing={Dim.px(12)}\n>\n  {/* First card */}\n  <SbContainer\n    layout=\"vertical\"\n    width={Dim.fill()}\n    height={Dim.fit()}\n    variant=\"card\"\n    spacing={Dim.px(6)}\n  >\n    <SbContainer\n      layout=\"horizontal\"\n      width={Dim.fill()}\n      height={Dim.fit()}\n      variant=\"none\"\n      horizontalAlign=\"space-between\"\n      spacing={Dim.px(6)}\n    >\n      <SbText\n        text=\"Avg delivery time (min)\"\n        textStyle={{\n          variant: \"body2\",\n          textColor: {\n            default: sbComputed(() => Theme.colors.neutral500),\n          },\n        }}\n      />\n      <SbIcon icon=\"route\" height={Dim.px(24)} width={Dim.fit()} />\n    </SbContainer>\n    <SbContainer\n      layout=\"horizontal\"\n      width={Dim.fill()}\n      height={Dim.fit()}\n      variant=\"none\"\n      horizontalAlign=\"left\"\n      spacing={Dim.px(6)}\n    >\n      <SbText\n        text=\"32\"\n        textStyle={{\n          variant: \"heading1\",\n        }}\n      />\n      {/* Smaller annotation badge, showing change. Container background color is green because the value change is considered \"good\" (lower delivery time is better) */}\n      <SbContainer\n        layout=\"horizontal\"\n        width={Dim.fit()}\n        height={Dim.fit()}\n        variant=\"none\"\n        spacing={Dim.px(2)}\n        horizontalAlign=\"center\"\n        verticalAlign=\"center\"\n        backgroundColor=\"#c4e1af\"\n        padding={{\n          top: Dim.px(3),\n          right: Dim.px(6),\n          bottom: Dim.px(3),\n          left: Dim.px(6),\n        }}\n        borderRadius={{\n          topLeft: Dim.px(20),\n          topRight: Dim.px(20),\n          bottomRight: Dim.px(20),\n          bottomLeft: Dim.px(20),\n        }}\n      >\n        <SbIcon\n          icon=\"arrow_downward_alt\"\n          height={Dim.px(24)}\n          width={Dim.fit()}\n        />\n        <SbText\n          text=\"2m\"\n          width={Dim.fit()}\n          textStyle={{\n            variant: \"body2\",\n          }}\n        />\n      </SbContainer>\n    </SbContainer>\n  </SbContainer>\n</SbContainer>;\n```\n";
+//# sourceMappingURL=superblocks-custom-components.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-custom-components.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-custom-components.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-custom-components.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,qvPAAiuP,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-custom-components.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-custom-components.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "# Custom Components\n\n- ULTRA CRITICAL: NEVER use Superblocks components in a custom component.\n\n- CRITICAL: Use custom components sparingly.\n\n- CRITICAL: ONLY when all else fails and a component is not available in the Superblocks library, you may construct it out of external component libraries by installing them.\n\n- CRITICAL: ALWAYS import React using a namespace import: `import * as React from 'react'`.\n\nIn order to hook it up correctly, the platform needs to know what props the component exposes, their types, default values, and how they should be displayed to users.\n\nTo do this, you use the **`Prop` API** and **`registerComponent`** function.\n\n## Key Concepts\n\n- All custom components should live within the `components/` folder.\n- **`Prop`**: Defines a single editable property for your component.\n  - Can specify the data type (`string`, `number`, `boolean`, `event`, etc.).\n  - Can define a **default value**, **label** for the properties panel, and other validations.\n- **`registerComponent`**: Connects your React component with its editable schema (`properties`) so it appears correctly in the visual editor.\n- **`useUpdateProperties`**: A hook that lets your component programmatically update its properties during runtime (e.g., when a user interacts with it).\n\n---\n\n## Basic Example\n\n```tsx\nimport { Rate } from \"antd\";\nimport {\n  CustomComponentProps,\n  Prop,\n  registerComponent,\n  useUpdateProperties,\n} from \"@superblocksteam/library\";\n\n// 1. Define editable properties\nconst properties = {\n  value: Prop.number()\n    .default(3) // Default to 3 stars\n    .propertiesPanel({ label: \"Default value\" }), // Editor label\n  onChange: Prop.event().propertiesPanel({ label: \"On change\" }), // Editor label for event\n};\n\n// 2. Create typed props for your component\ntype ComponentProps = CustomComponentProps<typeof properties>;\n\n// 3. Build your React component\nconst Rating = ({ value, onChange }: ComponentProps) => {\n  const updateProperties = useUpdateProperties(); // Hook to update properties dynamically\n\n  return (\n    <div style={{ display: \"flex\" }}>\n      <Rate\n        value={value}\n        defaultValue={value}\n        onChange={(newValue) => {\n          updateProperties({ value: newValue }); // Update visual editor\n          onChange?.(); // Trigger custom event\n        }}\n      />\n    </div>\n  );\n};\n\n// 4. Register your component to make it available in the visual editor\nexport default registerComponent(\"Rating\", properties, Rating);\n```\n\n---\n\n## How `Prop` Works\n\nYou can define different types of props:\n\n- **`string`**: `Prop.string()`\n- **`number`**: `Prop.number()`\n- **`boolean`**: `Prop.boolean()`\n- **`event`**: `Prop.event()` (for user interactions like clicks)\n- **`any`**: `Prop.any()` (for any type)\n- **`composite`**: `Prop.composite({ x: Prop.number(), y: Prop.number() })` (for nested objects)\n- **`record`**: `Prop.record({...})` (for key-value maps)\n- **`union`**: `Prop.union({...})` (for multiple variants)\n\nYou can chain additional methods:\n\n- `.default(value)` — Sets a default value.\n- `.propertiesPanel({ label: \"Your Label\" })` — Controls how the prop appears in the editor.\n- `.validate(fn)` — Adds custom validation logic.\n- `.readable()`, `.writable()` — Control read/write capabilities.\n\n---\n\n## Typical Flow\n\n1. **Define** the **editable schema** (`properties`) with `Prop`.\n2. **Type** your component's props using `CustomComponentProps`.\n3. **Use** `useUpdateProperties` to sync UI interactions back to the editor.\n4. **Register** the component using `registerComponent`.\n\n---# Tips\n\n- All `registeredComponent`s automatically support width and height using the `Dim` object.\n  ```\n  <CustomSlider\n    width={Dim.fill(2)} // Fill available space with a weight of 2\n    height={Dim.px(100)} // Fixed height of 100 pixels\n  />\n  ```\n\n## When not to use custom components\n\n- If a user asks for something by name, like showing \"metrics\", and you do not find a \"metrics\" component in the Superblocks library, do not immediately assume you need to use a custom component. Instead consider using one of the pre-designed templates built from existing Superblocks components.\n\n## Pre-designed templates to use instead of custom components\n\n### Rules for using pre-designed templates\n\n- Use the pre-designed templates as a base to work from. You can make changes to the content, but generally you do not need to change the layout or styling. Example: below there are width and height properties set on the icons and you should NOT change these or you will break the layout.\n\n### Metrics template\n\nThis template is a row of three large numerical metrics with icons and annotation text.\n\nTemplate code below and a few notes to help explain usage:\n\n- We use the SbContainer component to layout the metrics in a row\n- We use the SbText component to show the numerical values and how we use the textStyle prop variant to make the text a big heading\n- We use the SbIcon component to show nice icons that make sense for the metric\n- We create a little \"badge\" using the SbContainer component to show small annotation text. Prefer this over using brackets in the main heading text. Example: Rather than \"32 (2m)\" we use \"32\" in the main heading text and then a badge with the \"2m\" text\n- Keep the icon sizing you see in this template unless you are explicitly asked to change it\n\n```tsx\nimport {\n  SbIcon,\n  SbText,\n  SbContainer,\n  sbComputed,\n  Dim,\n  Global,\n  Theme,\n  Embed,\n  Env,\n} from \"@superblocksteam/library\";\n\n<SbContainer\n  layout=\"horizontal\"\n  width={Dim.fill()}\n  height={Dim.fit()}\n  variant=\"none\"\n  spacing={Dim.px(12)}\n>\n  {/* First card */}\n  <SbContainer\n    layout=\"vertical\"\n    width={Dim.fill()}\n    height={Dim.fit()}\n    variant=\"card\"\n    spacing={Dim.px(6)}\n  >\n    <SbContainer\n      layout=\"horizontal\"\n      width={Dim.fill()}\n      height={Dim.fit()}\n      variant=\"none\"\n      horizontalAlign=\"space-between\"\n      spacing={Dim.px(6)}\n    >\n      <SbText\n        text=\"Avg delivery time (min)\"\n        textStyle={{\n          variant: \"body2\",\n          textColor: {\n            default: sbComputed(() => Theme.colors.neutral500),\n          },\n        }}\n      />\n      <SbIcon icon=\"route\" height={Dim.px(24)} width={Dim.fit()} />\n    </SbContainer>\n    <SbContainer\n      layout=\"horizontal\"\n      width={Dim.fill()}\n      height={Dim.fit()}\n      variant=\"none\"\n      horizontalAlign=\"left\"\n      spacing={Dim.px(6)}\n    >\n      <SbText\n        text=\"32\"\n        textStyle={{\n          variant: \"heading1\",\n        }}\n      />\n      {/* Smaller annotation badge, showing change. Container background color is green because the value change is considered \"good\" (lower delivery time is better) */}\n      <SbContainer\n        layout=\"horizontal\"\n        width={Dim.fit()}\n        height={Dim.fit()}\n        variant=\"none\"\n        spacing={Dim.px(2)}\n        horizontalAlign=\"center\"\n        verticalAlign=\"center\"\n        backgroundColor=\"#c4e1af\"\n        padding={{\n          top: Dim.px(3),\n          right: Dim.px(6),\n          bottom: Dim.px(3),\n          left: Dim.px(6),\n        }}\n        borderRadius={{\n          topLeft: Dim.px(20),\n          topRight: Dim.px(20),\n          bottomRight: Dim.px(20),\n          bottomLeft: Dim.px(20),\n        }}\n      >\n        <SbIcon\n          icon=\"arrow_downward_alt\"\n          height={Dim.px(24)}\n          width={Dim.fit()}\n        />\n        <SbText\n          text=\"2m\"\n          width={Dim.fit()}\n          textStyle={{\n            variant: \"body2\",\n          }}\n        />\n      </SbContainer>\n    </SbContainer>\n  </SbContainer>\n</SbContainer>;\n```\n";
+//# sourceMappingURL=superblocks-custom-components.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-custom-components.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-custom-components.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-custom-components.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,uDAAuD;AACvD,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,8tPAA8tP,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-event-flow.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Event handlers with SbEventFlow\n\nRather than using standard browser event handlers, Superblocks provides a structured event handler action flow that allows you to run a series of events within the Superblocks system.\n\nImporting SbEventFlow:\n\n```jsx\nimport { SbEventFlow } from \"@superblocksteam/library\";\n```\n\nAll event handlers MUST be written using the `SbEventFlow` object.\n\nFor example, here we set the `isReady` state variable to `true` when the button is clicked:\n\n```jsx\n<SbButton onClick={SbEventFlow.setStateVar(\"isReady\", true)} />\n```\n\n## SbEventFlow builder pattern\n\n`SbEventFlow` provides a number of functions that can be chained together using `SbEventFlow` which correspond to actions in the Superblocks system.\n\nYou should always use these dedicated functions for individual and sequential actions.\n\nImportant: DO NOT use .run() at the end of a chain of SbEventFlow functions, it is not needed and it will throw an error.\n\n```jsx\n<SbButton\n  onClick={SbEventFlow.setQueryParams({ filter: \"active\" }, true)\n    .setStateVar(\"isReady\", true)\n    .controlModal(\"loginModal\", \"close\")\n\n    // run APIs allows you to run Superblocks APIs by name using string arrays\n    // Each runAPIs call executes the list of API names supplied in parallel\n    .runApis([getUserData, getPermissions])\n\n    // set a state variable's value\n    .showAlert(\"Workflow complete\", \"success\")\n    .navigateTo({ url: \"/dashboard\", newWindow: false })}\n/>\n```\n\n#### Using RunJS (only when needed)\n\n`SbEventFlow` also has a special `runJS` event type that allows you to run any JavaScript in the browser.\n\nThis allows you to write more complex logic such as control flow.\n\nImportant:\n\n- The only things you can do in runJS is set state variables or set the public state of components, like modal.isOpen.\n- You CANNOT use SbEventFlow inside of a SbEventFlow.runJS function. If you do this, it won't work!\n- **State access in runJS**: Scope entities are accessible directly by their names, global state is accessible via imported globals (Global, Theme, Embed, Env).\n\nExample accessing scope entities:\n\n```jsx\n<SbButton\n  label=\"Enable\"\n  buttonStyle={\"SECONDARY_BUTTON\"}\n  onClick={SbEventFlow.runJS(() => {\n    // Scope entities (variables, bound components) are accessible directly in runJS\n    if (isUserAdmin.value) {\n      // isUserAdmin is a bound component from scope\n      myStateVar.value = true; // myStateVar is a state variable from scope\n      myModal.isOpen = false; // myModal is a bound component from scope\n    } else {\n      console.log(\"This user was not an admin\");\n    }\n  })}\n/>\n```\n\nExample accessing global state when needed:\n\n```jsx\n<SbButton\n  label=\"Personalized Action\"\n  onClick={SbEventFlow.runJS(() => {\n    // Import globals and access directly\n    if (Global.user.role === \"admin\") {\n      // Also access scope entities (bound components) directly\n      adminPanel.isVisible = true; // adminPanel is a bound component from scope\n    }\n    console.log(`Welcome ${Global.user.name}!`);\n  })}\n/>\n```\n\nAs mentioned above, you should only use `runJS` when the flow is too complex to represent using only chained event flow actions.\n\n### SbEvent Flow Usage Examples\n\n```typescript\nimport { SbEventFlow, sbComputed } from \"@superblocksteam/library\";\nimport { Page1 } from \"./scope\";\n\nconst { fetchUserData, saveUserData, userDataVariable } = Page1;\n\n// Navigation example\nSbEventFlow.navigateTo({ url: \"https://example.com\", newWindow: true });\n\n// Control UI components example\nSbEventFlow.controlModal(\"myModal\", \"open\");\n\n// State management example\nSbEventFlow.setStateVar(\"userProfile\", { name: \"John\", role: \"Admin\" });\n\n// Chaining multiple actions\nSbEventFlow.runApis([fetchUserData])\n  .setStateVar(\n    \"userDataVariable\",\n    sbComputed(() => {\n      fetchUserData.response;\n    }),\n  )\n  .showAlert(\"Data loaded successfully\", \"success\");\n\n// Conditional flow with success/error handlers\nconst successFlow = SbEventFlow.showAlert(\"Success!\", \"success\");\nconst errorFlow = SbEventFlow.showAlert(\"An error occurred\", \"error\");\nSbEventFlow.runApis([saveUserData], successFlow, errorFlow);\n```\n\n**SbEventFlow: Managing Events and Side Effects in Superblocks**\n\n## Important Syntax Rules\n\n- Always use function braces with SbEventFlow.runJS. Example: `SbEventFlow.runJS(() => { someFunction(); })` not `SbEventFlow.runJS(() => someFunction())`\n- SbEventFlow.runApis() accepts an array of direct API entity references. Example: `SbEventFlow.runApis([fetchUserData, saveUserData])`\n";
+//# sourceMappingURL=superblocks-event-flow.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-event-flow.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-event-flow.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-event-flow.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,slJAAslJ,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-event-flow.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-event-flow.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "# Event handlers with SbEventFlow\n\nRather than using standard browser event handlers, Superblocks provides a structured event handler action flow that allows you to run a series of events within the Superblocks system.\n\nImporting SbEventFlow:\n\n```jsx\nimport { SbEventFlow } from \"@superblocksteam/library\";\n```\n\nAll event handlers MUST be written using the `SbEventFlow` object.\n\nFor example, here we set the `isReady` state variable to `true` when the button is clicked:\n\n```jsx\n<SbButton onClick={SbEventFlow.setStateVar(\"isReady\", true)} />\n```\n\n## SbEventFlow builder pattern\n\n`SbEventFlow` provides a number of functions that can be chained together using `SbEventFlow` which correspond to actions in the Superblocks system.\n\nYou should always use these dedicated functions for individual and sequential actions.\n\nImportant: DO NOT use .run() at the end of a chain of SbEventFlow functions, it is not needed and it will throw an error.\n\n```jsx\n<SbButton\n  onClick={SbEventFlow.setQueryParams({ filter: \"active\" }, true)\n    .setStateVar(\"isReady\", true)\n    .controlModal(\"loginModal\", \"close\")\n\n    // run APIs allows you to run Superblocks APIs by name using string arrays\n    // Each runAPIs call executes the list of API names supplied in parallel\n    .runApis([getUserData, getPermissions])\n\n    // set a state variable's value\n    .showAlert(\"Workflow complete\", \"success\")\n    .navigateTo({ url: \"/dashboard\", newWindow: false })}\n/>\n```\n\n#### Using RunJS (only when needed)\n\n`SbEventFlow` also has a special `runJS` event type that allows you to run any JavaScript in the browser.\n\nThis allows you to write more complex logic such as control flow.\n\nImportant:\n\n- The only things you can do in runJS is set state variables or set the public state of components, like modal.isOpen.\n- You CANNOT use SbEventFlow inside of a SbEventFlow.runJS function. If you do this, it won't work!\n- **State access in runJS**: Scope entities are accessible directly by their names, global state is accessible via imported globals (Global, Theme, Embed, Env).\n\nExample accessing scope entities:\n\n```jsx\n<SbButton\n  label=\"Enable\"\n  buttonStyle={\"SECONDARY_BUTTON\"}\n  onClick={SbEventFlow.runJS(() => {\n    // Scope entities (variables, bound components) are accessible directly in runJS\n    if (isUserAdmin.value) {\n      // isUserAdmin is a bound component from scope\n      myStateVar.value = true; // myStateVar is a state variable from scope\n      myModal.isOpen = false; // myModal is a bound component from scope\n    } else {\n      console.log(\"This user was not an admin\");\n    }\n  })}\n/>\n```\n\nExample accessing global state when needed:\n\n```jsx\n<SbButton\n  label=\"Personalized Action\"\n  onClick={SbEventFlow.runJS(() => {\n    // Import globals and access directly\n    if (Global.user.role === \"admin\") {\n      // Also access scope entities (bound components) directly\n      adminPanel.isVisible = true; // adminPanel is a bound component from scope\n    }\n    console.log(`Welcome ${Global.user.name}!`);\n  })}\n/>\n```\n\nAs mentioned above, you should only use `runJS` when the flow is too complex to represent using only chained event flow actions.\n\n### SbEvent Flow Usage Examples\n\n```typescript\nimport { SbEventFlow, sbComputed } from \"@superblocksteam/library\";\nimport { Page1 } from \"./scope\";\n\nconst { fetchUserData, saveUserData, userDataVariable } = Page1;\n\n// Navigation example\nSbEventFlow.navigateTo({ url: \"https://example.com\", newWindow: true });\n\n// Control UI components example\nSbEventFlow.controlModal(\"myModal\", \"open\");\n\n// State management example\nSbEventFlow.setStateVar(\"userProfile\", { name: \"John\", role: \"Admin\" });\n\n// Chaining multiple actions\nSbEventFlow.runApis([fetchUserData])\n  .setStateVar(\n    \"userDataVariable\",\n    sbComputed(() => {\n      fetchUserData.response;\n    }),\n  )\n  .showAlert(\"Data loaded successfully\", \"success\");\n\n// Conditional flow with success/error handlers\nconst successFlow = SbEventFlow.showAlert(\"Success!\", \"success\");\nconst errorFlow = SbEventFlow.showAlert(\"An error occurred\", \"error\");\nSbEventFlow.runApis([saveUserData], successFlow, errorFlow);\n```\n\n**SbEventFlow: Managing Events and Side Effects in Superblocks**\n\n## Important Syntax Rules\n\n- Always use function braces with SbEventFlow.runJS. Example: `SbEventFlow.runJS(() => { someFunction(); })` not `SbEventFlow.runJS(() => someFunction())`\n- SbEventFlow.runApis() accepts an array of direct API entity references. Example: `SbEventFlow.runApis([fetchUserData, saveUserData])`\n";
+//# sourceMappingURL=superblocks-event-flow.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-event-flow.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-event-flow.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-event-flow.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,gDAAgD;AAChD,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,mlJAAmlJ,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-layouts.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "### Layout and Sizing in Superblocks\n\nAll layouts in Superblocks are configured through the `SbContainer` component.  \n`SbContainer` provides both layout and optional visual styling.\n\n```jsx\n<SbContainer\n  variant=\"card\" | \"none\" // default is \"none\"\n  layout=\"vertical\" | \"horizontal\" | \"freeform\" // default is \"vertical\"\n>\n  {/* Children here */}\n</SbContainer>\n```\n\nWe have three main layout options in Superblocks:\n\n- Vertical Stack (`vertical`)\n- Horizontal Stack (`horizontal`)\n- Freeform (`freeform`)\n\nFor new designs, we recommend using Stacks for most use cases.\n\nThe `variant` prop is optional and can be set to `\"card\"` or `\"none\"`. Default is `\"none\"`.\n`\"card\"` applies a card-like visual style to the container, such as rounded corners, white background, and padding.\n\n---\n\n### Height and Width Options\n\nAll Superblocks components support width and height. They take in a `Dim` object, which has 3 main options:\n\n- `Dim.fit()`: Fit to content size, this is the default behavior and can be omitted.\n- `Dim.px(100)`: Fixed pixel size.\n- `Dim.fill()` or `Dim.fill(2)`: Fill available space with an optional weight.\n\n> IMPORTANT: Prefer using `Dim.fit()` over `Dim.px()` for height and width unless you have a specific reason to use fixed pixel sizes. This is extra true for containers\n> IMPORTANT: Prefer using `Dim.fill()` or `Dim.fit()` over `Dim.px()` for width unless you have a specific reason to use fixed pixel sizes.\n\n**Examples**:\n\n```jsx\n<SbText width={Dim.px(2)}>Hello</SbText>   // 2 pixels\n<SbText width={Dim.fit()}>Hello</SbText>   // Fit to content (default)\n<SbText width={Dim.fill()}>Hello</SbText>  // Fill available space, no weight (aka 1)\n<SbText width={Dim.fill(2)}>Hello</SbText> // Fill available space, with weight of 2\n```\n";
+//# sourceMappingURL=superblocks-layouts.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-layouts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-layouts.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-layouts.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,yyDAAyyD,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-layouts.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-layouts.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "### Layout and Sizing in Superblocks\n\nAll layouts in Superblocks are configured through the `SbContainer` component.  \n`SbContainer` provides both layout and optional visual styling.\n\n```jsx\n<SbContainer\n  variant=\"card\" | \"none\" // default is \"none\"\n  layout=\"vertical\" | \"horizontal\" | \"freeform\" // default is \"vertical\"\n>\n  {/* Children here */}\n</SbContainer>\n```\n\nWe have three main layout options in Superblocks:\n\n- Vertical Stack (`vertical`)\n- Horizontal Stack (`horizontal`)\n- Freeform (`freeform`)\n\nFor new designs, we recommend using Stacks for most use cases.\n\nThe `variant` prop is optional and can be set to `\"card\"` or `\"none\"`. Default is `\"none\"`.\n`\"card\"` applies a card-like visual style to the container, such as rounded corners, white background, and padding.\n\n---\n\n### Height and Width Options\n\nAll Superblocks components support width and height. They take in a `Dim` object, which has 3 main options:\n\n- `Dim.fit()`: Fit to content size, this is the default behavior and can be omitted.\n- `Dim.px(100)`: Fixed pixel size.\n- `Dim.fill()` or `Dim.fill(2)`: Fill available space with an optional weight.\n\n> IMPORTANT: Prefer using `Dim.fit()` over `Dim.px()` for height and width unless you have a specific reason to use fixed pixel sizes. This is extra true for containers\n> IMPORTANT: Prefer using `Dim.fill()` or `Dim.fit()` over `Dim.px()` for width unless you have a specific reason to use fixed pixel sizes.\n\n**Examples**:\n\n```jsx\n<SbText width={Dim.px(2)}>Hello</SbText>   // 2 pixels\n<SbText width={Dim.fit()}>Hello</SbText>   // Fit to content (default)\n<SbText width={Dim.fill()}>Hello</SbText>  // Fill available space, no weight (aka 1)\n<SbText width={Dim.fill(2)}>Hello</SbText> // Fill available space, with weight of 2\n```\n";
+//# sourceMappingURL=superblocks-layouts.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-layouts.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-layouts.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-layouts.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,6CAA6C;AAC7C,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,syDAAsyD,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-page.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "### How to use SbPage\n\n- A page is a file that exports a default React component through the `registerPage` function.\n- Each page consists of two files: `index.tsx` (the page component) and `scope.ts` (the entity definitions).\n- For `export default registerPage(Page1, Page1Scope)`, Page1 is a function that returns a React component, and Page1Scope is the scope containing all entities.\n- A project consists of one or more pages. Each page is a directory in the `pages` directory.\n- Pages are registered in the `routes.json` file.\n\n### Page Structure\n\nEach page should have the following structure:\n\n**scope.ts** - Contains all entity definitions (variables, APIs, etc.):\n\n```ts\nimport {\n  createSbScope,\n  SbVariable,\n  SbVariablePersistence,\n  SbApi,\n  SbText,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createSbScope<{\n  Text1: any;\n}>(\n  {\n    // Define your entities here\n    myVariable: SbVariable({\n      defaultValue: \"initial value\",\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n    myApi: SbApi({}),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n**index.tsx** - Contains the page component:\n\n```tsx\nimport { SbPage, SbText, registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nfunction Page() {\n  // Destructure entities from the scope for easy access\n  const { Text1, myVariable, myApi } = Page1;\n\n  return (\n    <SbPage>\n      {/* Use entities in your components */}\n      <SbText bind={Text1} text={sbComputed(() => myVariable.value)} />\n    </SbPage>\n  );\n}\n\nexport default registerPage(Page, Page1Scope);\n```\n\n## How component bindings work\n\nIf you need to reference a component directly to get access to some of its state, you must use a binding inside the page scope.\n\nComponent bindings allow you to:\n\n- Access component properties and state from other components and APIs\n- Create reactive relationships between components\n- Reference component values in `sbComputed` expressions\n\n### Setting up component bindings\n\n1. **Define the binding type in your scope**: Add the component type to the scope's type definitions:\n\n```ts\nexport const Page1Scope = createSbScope<{\n  Text1: any;\n  UserInput: any;\n}>(\n  {\n    // Your other entities (variables, APIs, etc.)\n    myVariable: SbVariable({ defaultValue: \"Hello\" }),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n2. **Bind the component in your JSX**: Use the `bind` prop to connect the component to the binding:\n\n```tsx\nfunction Page() {\n  const { Text1, UserInput, myVariable } = Page1;\n\n  return (\n    <SbPage>\n      <SbInput bind={UserInput} placeholder=\"Enter your name\" />\n      <SbText\n        bind={Text1}\n        text={sbComputed(() => `Hello, ${UserInput.value}!`)}\n      />\n    </SbPage>\n  );\n}\n```\n\n3. **Access component state**: Use `sbComputed` to access properties of bound components:\n\n```tsx\n// Access input value\ntext={sbComputed(() => UserInput.value)}\n\n// Access text content\ntext={sbComputed(() => Text1.text)}\n\n// Combine with other state\ntext={sbComputed(() => `${myVariable.value}: ${UserInput.value}`)}\n```\n\n### Common binding use cases\n\n- **Form inputs**: Access user input values to display or validate\n- **Dynamic content**: Reference one component's state to update another\n- **Conditional rendering**: Use component state to control visibility or styling\n\n### Page load events\n\nYou can fire callbacks when a page is loaded using the onLoad property of the Page component. You must use the SbEventFlow API for any actions you want to run inside onLoad.\n\nExample:\n\n```tsx\nimport {\n  registerPage,\n  SbEventFlow,\n  SbPage,\n  sbComputed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return (\n    <SbPage\n      onLoad={SbEventFlow.runJS(() => {\n        console.log(\"Page loaded\");\n      })}\n    >\n      ...\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nA very common and helpful usage of this callback is to run APIs using SbEventFlow to fetch data when the page loads. Example:\n\n```tsx\nimport {\n  SbPage,\n  registerPage,\n  SbEventFlow,\n  sbComputed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return <SbPage onLoad={SbEventFlow.runApis([getOrders])}>...</SbPage>;\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nIn this example, the `getOrders` API would be defined in the scope.ts file like this:\n\n```ts\n// In scope.ts\n\n// We register the api in createSbScope by creating a key\n// with the same name as the file, and SbApi({}) with an empty object\n// Note: We DO NOT import the api file. It's not necessary.\nexport const Page1Scope = createSbScope(\n  () => ({\n    getOrders: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n";
+//# sourceMappingURL=superblocks-page.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-page.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-page.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-page.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,47JAA47J,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-page.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-page.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "### How to use SbPage\n\n- A page is a file that exports a default React component through the `registerPage` function.\n- Each page consists of two files: `index.tsx` (the page component) and `scope.ts` (the entity definitions).\n- For `export default registerPage(Page1, Page1Scope)`, Page1 is a function that returns a React component, and Page1Scope is the scope containing all entities.\n- A project consists of one or more pages. Each page is a directory in the `pages` directory.\n- Pages are registered in the `routes.json` file.\n\n### Page Structure\n\nEach page should have the following structure:\n\n**scope.ts** - Contains all entity definitions (variables, APIs, etc.):\n\n```ts\nimport {\n  createSbScope,\n  SbVariable,\n  SbVariablePersistence,\n  SbApi,\n  SbText,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createSbScope<{\n  Text1: any;\n}>(\n  {\n    // Define your entities here\n    myVariable: SbVariable({\n      defaultValue: \"initial value\",\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n    myApi: SbApi({}),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\n**index.tsx** - Contains the page component:\n\n```tsx\nimport { SbPage, SbText, registerPage } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nfunction Page() {\n  // Destructure entities from the scope for easy access\n  const { Text1, myVariable, myApi } = Page1;\n\n  return (\n    <SbPage>\n      {/* Use entities in your components */}\n      <SbText bind={Text1} text={sbComputed(() => myVariable.value)} />\n    </SbPage>\n  );\n}\n\nexport default registerPage(Page, Page1Scope);\n```\n\n## How component bindings work\n\nIf you need to reference a component directly to get access to some of its state, you must use a binding inside the page scope.\n\nComponent bindings allow you to:\n\n- Access component properties and state from other components and APIs\n- Create reactive relationships between components\n- Reference component values in `sbComputed` expressions\n\n### Setting up component bindings\n\n1. **Define the binding type in your scope**: Add the component type to the scope's type definitions:\n\n```ts\nexport const Page1Scope = createSbScope<{\n  Text1: any;\n  UserInput: any;\n}>(\n  {\n    // Your other entities (variables, APIs, etc.)\n    myVariable: SbVariable({ defaultValue: \"Hello\" }),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n2. **Bind the component in your JSX**: Use the `bind` prop to connect the component to the binding:\n\n```tsx\nfunction Page() {\n  const { Text1, UserInput, myVariable } = Page1;\n\n  return (\n    <SbPage>\n      <SbInput bind={UserInput} placeholder=\"Enter your name\" />\n      <SbText\n        bind={Text1}\n        text={sbComputed(() => `Hello, ${UserInput.value}!`)}\n      />\n    </SbPage>\n  );\n}\n```\n\n3. **Access component state**: Use `sbComputed` to access properties of bound components:\n\n```tsx\n// Access input value\ntext={sbComputed(() => UserInput.value)}\n\n// Access text content\ntext={sbComputed(() => Text1.text)}\n\n// Combine with other state\ntext={sbComputed(() => `${myVariable.value}: ${UserInput.value}`)}\n```\n\n### Common binding use cases\n\n- **Form inputs**: Access user input values to display or validate\n- **Dynamic content**: Reference one component's state to update another\n- **Conditional rendering**: Use component state to control visibility or styling\n\n### Page load events\n\nYou can fire callbacks when a page is loaded using the onLoad property of the Page component. You must use the SbEventFlow API for any actions you want to run inside onLoad.\n\nExample:\n\n```tsx\nimport {\n  registerPage,\n  SbEventFlow,\n  SbPage,\n  sbComputed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return (\n    <SbPage\n      onLoad={SbEventFlow.runJS(() => {\n        console.log(\"Page loaded\");\n      })}\n    >\n      ...\n    </SbPage>\n  );\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nA very common and helpful usage of this callback is to run APIs using SbEventFlow to fetch data when the page loads. Example:\n\n```tsx\nimport {\n  SbPage,\n  registerPage,\n  SbEventFlow,\n  sbComputed,\n} from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nconst Page1Component = () => {\n  return <SbPage onLoad={SbEventFlow.runApis([getOrders])}>...</SbPage>;\n};\n\nexport default registerPage(Page1Component, Page1Scope);\n```\n\nIn this example, the `getOrders` API would be defined in the scope.ts file like this:\n\n```ts\n// In scope.ts\n\n// We register the api in createSbScope by creating a key\n// with the same name as the file, and SbApi({}) with an empty object\n// Note: We DO NOT import the api file. It's not necessary.\nexport const Page1Scope = createSbScope(\n  () => ({\n    getOrders: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n";
+//# sourceMappingURL=superblocks-page.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-page.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-page.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-page.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,0CAA0C;AAC1C,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,y7JAAy7J,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-routes.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "- The `routes.json` file maps URLs to pages.\n  Example routes.json file content:\n\n```json\n{\n  \"/\": {\n    \"file\": \"Page1/index.tsx\"\n  },\n  \"/projects\": {\n    \"file\": \"Page2/index.tsx\"\n  }\n}\n```\n\nIn the above example, the '/' route maps to Page1 and '/projects' route maps to Page2.\n\nCritical: Page paths in `routes.json` are relative to the 'pages/' directory. In this file, you must never prefix `file` values with 'pages/', or the app will break.\n";
+//# sourceMappingURL=superblocks-routes.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-routes.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-routes.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-routes.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,keAAke,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-routes.js

@@ -0,0 +1,6 @@
+/* eslint-disable */
+// Auto-generated from superblocks-routes.md
+// Do not edit this file directly
+// Generated at: 2025-06-09T20:52:37.005Z
+export const content = "- The `routes.json` file maps URLs to pages.\n  Example routes.json file content:\n\n```json\n{\n  \"/\": {\n    \"file\": \"Page1/index.tsx\"\n  },\n  \"/projects\": {\n    \"file\": \"Page2/index.tsx\"\n  }\n}\n```\n\nIn the above example, the '/' route maps to Page1 and '/projects' route maps to Page2.\n\nCritical: Page paths in `routes.json` are relative to the 'pages/' directory. In this file, you must never prefix `file` values with 'pages/', or the app will break.\n";
+//# sourceMappingURL=superblocks-routes.js.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-routes.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-routes.js","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-routes.ts"],"names":[],"mappings":"AAAA,oBAAoB;AACpB,4CAA4C;AAC5C,iCAAiC;AACjC,yCAAyC;AAEzC,MAAM,CAAC,MAAM,OAAO,GAAG,+dAA+d,CAAC"}

package/dist/ai-service/prompts/generated/subprompts/superblocks-state.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "**Superblocks State System**\n\nThe Superblocks state system is built around scopes that contain entities (variables, APIs, components). Here's how it works:\n\n### 1. Scopes\n\nScopes are defined in separate `scope.ts` files for each page and contain all the page's entities.\n\n- **Page scopes** are visible only within the current page\n- **App scopes** can be shared across pages (though you should primarily use page scopes)\n- Entities are accessed by importing and destructuring from the scope\n\n> **Parent \u2192 child rule**: Child scopes can read & write parent entities, but parents cannot reach into children.\n\n### 2. Scope Structure\n\nEach page has its own scope file that defines all entities:\n\n```ts\n// pages/Page1/scope.ts\nimport {\n  createSbScope,\n  SbVariable,\n  SbVariablePersistence,\n  SbApi,\n  sbComputed,\n} from \"@superblocksteam/library\";\n\nexport const Page1Scope = createSbScope<{\n  OrdersTable: any;\n}>(\n  ({ entities: { counter } }) => ({\n    // Static state variable with a simple default value\n    counter: SbVariable({\n      defaultValue: 0,\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n    // State variable with computed default value from other entities\n    doubledCounter: SbVariable({\n      defaultValue: sbComputed(() => counter.value * 2),\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n    myApi: SbApi({}),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n\nexport const Page1 = Page1Scope.entities;\n```\n\nThen in your page component, you import and destructure the entities:\n\n```tsx\n// pages/Page1/index.tsx\nimport { SbPage, SbText, SbButton, sbComputed } from \"@superblocksteam/library\";\nimport { Page1, Page1Scope } from \"./scope\";\n\nfunction Page() {\n  // Destructure entities for easy access\n  const { counter, doubledCounter, myApi, OrdersTable } = Page1;\n\n  return (\n    <SbPage>\n      <SbText text={sbComputed(() => `Count: ${counter.value}`)} />\n      <SbButton onClick={SbEventFlow.setStateVar(\"counter\", 5)} />\n    </SbPage>\n  );\n}\n\nexport default registerPage(Page, Page1Scope);\n```\n\n_You should NOT create any extra scopes other than page scopes in most cases._\n\n### 3. Computed Default Values\n\nState variables can have their `defaultValue` computed from other entities in the same scope at initialization time.\n\n**Static default value:**\n\n```ts\nstaticVar: SbVariable({\n  defaultValue: \"Hello World\",\n});\n```\n\n**Computed default value:**\n\n```ts\n({ entities: { Input1, staticVar } }) => ({\n  computedVar: SbVariable({\n    defaultValue: sbComputed(() => `${staticVar.value} - ${Input1.value}`),\n  }),\n});\n```\n\nWrap the entire scope object with the entities function and destructure needed entities from the `entities` parameter. This only sets the initial value - it doesn't create ongoing updates.\n\n### 4. Entity Types\n\n- **Component state**\n\n  - Declared by defining the component type in the scope and using the `bind` prop\n  - Accessed by destructuring the component entity and using `sbComputed(() => ComponentName.prop)`\n  - Writable if the prop is marked writable in the schema\n\n- **State variable**\n\n  - Declared with `SbVariable({ defaultValue })` or within `(({ entities }) => ({ ... }))` wrapper for computed defaults\n  - `defaultValue` sets the initial value when the application loads\n  - For static variables: Only JSON parsable data structures, no functions\n  - For computed variables: Use `sbComputed` within defaultValue to reference other entities\n  - Do not call `defaultValue` like a function. Set values with `SbEventFlow.setStateVar()` or read with `sbComputed(() => varName.value)`\n  - Accessed with `sbComputed(() => varName.value)` \u2014 **always include `.value`**\n  - Writable through SbEventFlow\n\n- **API**\n  - Declared with `SbApi({})` in the scope file.\n  - Accessed with `sbComputed(() => apiName.response)` or `sbComputed(() => apiName.error)`\n  - Read\u2011only\n\n### 5. Reading State with sbComputed\n\n**CRITICAL**: There are two different patterns for accessing data in `sbComputed` depending on what you're accessing:\n\n#### 5.1. Scope Entities (Direct Access)\n\nFor entities defined in your scope file (variables, APIs, components), access them **directly** after destructuring:\n\n```tsx\nconst { UserSearchInput, myVariable, myApi } = Page1;\n\n// \u2705 CORRECT - Direct access for scope entities\n<SbText text={sbComputed(() => `Search: ${UserSearchInput.value}`)} />\n<SbText text={sbComputed(() => myVariable.value)} />\n<SbTable tableData={sbComputed(() => myApi.response)} />\n```\n\n#### 4.2. Global State (Import Access)\n\nFor global state like globals, theme, environment, and embedded data, import the globals directly from the library:\n\n```tsx\n// \u2705 CORRECT - Import globals directly\n<SbText\n  text={sbComputed(() => `Welcome ${Global.user.name}!`)}\n  textStyle={{\n    textColor: {\n      default: sbComputed(() => Theme.colors.neutral900)\n    }\n  }}\n/>\n<SbContainer backgroundColor={sbComputed(() => Theme.colors.primary)} />\n```\n\n#### 5.3. Mixed Access\n\nWhen you need both scope entities and global state in the same `sbComputed`:\n\n```tsx\nconst { orders } = Page1;\n\n// \u2705 CORRECT - Combine direct entity access with imported globals\n<SbText\n  text={sbComputed(() => `${orders.length} orders for ${Global.user.name}`)}\n/>;\n```\n\n### 6. Writing State\n\nPreferred approach:\n\n```tsx\nSbEventFlow.setStateVar(\"pageSize\", 50);\n```\n\nFallback for complex operations:\n\n```tsx\nSbEventFlow.runJS(() => {\n  // Direct assignment works within SbEventFlow.runJS\n  pageSize.value = 50;\n});\n```\n\n### 7. CRITICAL Rules\n\n1. **Use component state directly**; NEVER create a state variable for a value that is available directly from a component property.\n2. Use component bindings by defining component types in your scope and using the `bind` prop.\n3. Keep logic declarative \u2014 derive UI from state using `sbComputed` instead of mutating props at runtime.\n4. Always destructure entities from your scope for clean access patterns.\n5. **Use the correct sbComputedz pattern**: Direct access for scope entities, import globals (Global, Theme, Embed, Env) for global access.\n6. Always complete implement all features, don't stub out or skip anything.\n\n**\u2705 Example**\n\n```tsx\n// In your scope.ts file\nexport const Page1Scope = createSbScope<{\n  ApplicantSelector: any;\n}>(\n  {\n    applicants: SbVariable({ defaultValue: [] }),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\n// In your page component after destructuring entities\nconst { ApplicantSelector, applicants } = Page1;\n\n<SbDropdown bind={ApplicantSelector} options={/* ... */} />\n<SbTable tableData={sbComputed(() => applicants[ApplicantSelector.selectedOptionValue])} />\n```\n\n```tsx\n// In your scope.ts file\nexport const Page1Scope = createSbScope<{\n  Country: any;\n}>(\n  {\n    applicants: SbVariable({ defaultValue: [] }),\n  },\n  FirstName: typeof SbInput;\n  LastName: typeof SbInput;\n}>(\n  ({ entities: { FirstName, LastName } }) => ({\n    fullName: SbVariable({\n      defaultValue: sbComputed(() =>\n        `${FirstName.value} ${LastName.value}`.trim(),\n      ),\n    }),\n  }),\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\nconst { FirstName, LastName, fullName } = Page1;\n\n<SbInput bind={FirstName} placeholder=\"First name\" />\n<SbInput bind={LastName} placeholder=\"Last name\" />\n<SbText text={sbComputed(() => `Welcome ${fullName.value}!`)} />\n```\n\n```tsx\n{\n  /* The user types in the search input, and the value is displayed */\n}\n// In your scope.ts file\nexport const Page1Scope = createSbScope<{\n  searchTerm: any;\n}>(\n  {},\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\nconst { searchTerm } = Page1;\n\n<SbInput bind={searchTerm} />\n<SbText text={sbComputed(() => searchTerm.value)} />\n```\n\n```tsx\n{\n  /* Switch to change into admin mode */\n}\n// In your scope.ts file\nexport const Page1Scope = createSbScope<{\n  isAdmin: any;\n}>(\n  {},\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\nconst { isAdmin } = Page1;\n\n<SbSwitch bind={isAdmin} label=\"Use Admin Mode\" defaultChecked={false} />;\n{\n  /* Only enable the delete button when switched into Admin mode */\n}\n<SbButton\n  disabled={sbComputed(() => !isAdmin.isChecked)}\n  label=\"Delete profile\"\n/>;\n```\n\n\u2705 ALWAYS USE DIRECT COMPONENT STATE ACCESS WITH sbComputed:\n\n```tsx\n// GOOD - DO THIS\n// In your scope.ts file\nexport const Page1Scope = createSbScope<{\n  UserNameInput: any;\n}>(\n  {},\n  {\n    name: \"Page1\",\n  },\n);\n```\n\n```tsx\nconst { UserNameInput } = Page1;\n\n<SbTextInput bind={UserNameInput} />\n<SbText text={sbComputed(() => `Hello, ${UserNameInput.value}!`)} />\n```\n\n\u274C NEVER CREATE REDUNDANT STATE VARIABLES:\n\n```tsx\n// WRONG - DON'T DO THIS\n<SbTextInput bind={UserNameInput} onChange={SbEventFlow.setStateVar('userNameVar', 'myValue')} />\n<SbText text={sbComputed(() => `Hello, ${userNameVar.value}!`)} />\n...\n// And then in scope.ts:\n{\n  userNameVar: SbVariable({ defaultValue: \"\" }),\n}\n```\n\nTo reference a property of a component using `sbComputed`, the component must have a binding defined in your scope.\n\nThat's why you should ALWAYS define component bindings in your scope for the following component types when you need to access their state:\n\n- SbInput\n- SbDropdown\n- SbDatePicker\n- SbCheckbox\n- SbSwitch\n- SbForm\n- SbRadio\n- SbRichText\n- SbFilePicker\n- SbCodeEditor\n- SbChat\n\n\u274C DO NOT USE STATE VARIABLES AS FUNCTIONS:\n\nState variables are not functions. You cannot call them or store functions in defaultValue.\n\n```tsx\n// WRONG - DON'T DO THIS\nfunction Page1() {\n  const { customerNameFilter, filterOrders } = Page1;\n\n  return (\n    <SbPage width={Dim.fill()}>\n      <SbInput\n        bind={customerNameFilter}\n        label=\"Customer Name\"\n        placeholder=\"Filter by customer name\"\n        width={Dim.fill()}\n        onTextChanged={SbEventFlow.runJS(() => {\n          // This is wrong - you cannot call filterOrders as a function\n          filterOrders();\n        })}\n      />\n    </SbPage>\n  );\n}\n\n// And in scope.ts (WRONG):\n{\n  filterOrders: SbVariable({\n    defaultValue: () => {\n      // This doesn't work - state variables are not functions\n      const customerNameFilter = customerNameFilter.value.toLowerCase();\n      // ... more logic\n    },\n  });\n}\n```\n\nInstead do the following:\n\n\u2705 COMPUTE VALUES WITH sbComputed AND SET STATE WITH SbEventFlow:\n\n```tsx\n// CORRECT - DO THIS\nfunction Page1() {\n  const { customerNameFilter, filteredOrders, orders } = Page1;\n\n  return (\n    <SbPage width={Dim.fill()}>\n      <SbInput\n        bind={customerNameFilter}\n        label=\"Customer Name\"\n        placeholder=\"Filter by customer name\"\n        width={Dim.fill()}\n        onTextChanged={SbEventFlow.runJS(() => {\n          // Repeat the filtering logic inline - do NOT create helper functions\n          const filtered = orders.value.filter((order) => {\n            return (\n              !customerNameFilter.value ||\n              order.customerName\n                .toLowerCase()\n                .includes(customerNameFilter.value.toLowerCase())\n            );\n          });\n\n          // Set the state variable with the computed result\n          filteredOrders.value = filtered;\n        })}\n      />\n      {/* If you need the same filtering logic elsewhere, repeat it inline */}\n      <SbButton\n        label=\"Apply Filter\"\n        onClick={SbEventFlow.runJS(() => {\n          // Repeat the same filtering logic here - code repetition is preferred\n          const filtered = orders.value.filter((order) => {\n            return (\n              !customerNameFilter.value ||\n              order.customerName\n                .toLowerCase()\n                .includes(customerNameFilter.value.toLowerCase())\n            );\n          });\n\n          filteredOrders.value = filtered;\n        })}\n      />\n      <SbTable tableData={sbComputed(() => filteredOrders.value)} />\n    </SbPage>\n  );\n}\n\nexport default registerPage(Page1, Page1Scope);\n```\n\nAnd in your scope.ts file:\n\n```ts\nexport const Page1Scope = createSbScope<{\n  customerNameFilter: any;\n}>(\n  {\n    orders: SbVariable({\n      defaultValue: [\n        {\n          id: \"ORD-1001\",\n          customerName: \"John Smith\",\n          orderType: \"Grocery Delivery\",\n        },\n        {\n          id: \"ORD-1002\",\n          customerName: \"Emily Johnson\",\n          orderType: \"Express Delivery\",\n        },\n      ],\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n    filteredOrders: SbVariable({\n      defaultValue: [],\n      persistence: SbVariablePersistence.TEMPORARY,\n    }),\n  },\n  {\n    name: \"Page1\",\n  },\n);\n```\n";
+//# sourceMappingURL=superblocks-state.d.ts.map

package/dist/ai-service/prompts/generated/subprompts/superblocks-state.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"superblocks-state.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/prompts/generated/subprompts/superblocks-state.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,OAAO,gpZAAolZ,CAAC"}