@superblocksteam/vite-plugin-file-sync 2.0.170 → 2.0.171-next.0

package/dist/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "Use icons from Lucide React library:\n\n```tsx\nimport { Icon } from \"@/components/ui/icon\";\n<Icon icon=\"heart\" />;\n\nimport { Button } from \"@/components/ui/button\";\n<Button>\n  <Icon icon=\"plus\" /> Add Item\n</Button>;\n```\n\n**Always use icons rather than emojis unless explicitly requested.**\n\nUse current Lucide icon names, not stale aliases: use `house` instead of `home`, `life-buoy` instead of `help-circle` or `circle-help`, and `chart-column-big` instead of `bar-chart-3`.\n\nWhen storing icon names as data (arrays/objects), type them with `IconName`. **`IconName` is a TYPE-only export \u2014 you MUST import it with the `type` keyword.** A value import compiles but CRASHES the app at runtime (`does not provide an export named 'IconName'`) and leaves the preview blank, which blocks UI verification. If you hit that error, read `skills/system/common-import-issues/SKILL.md`.\n\n```tsx\n// \u2705 CORRECT \u2014 type-only import\nimport type { IconName } from \"lucide-react/dynamic\";\n\nconst navItems: { icon: IconName; label: string }[] = [\n  { icon: \"house\", label: \"Home\" },\n  { icon: \"settings\", label: \"Settings\" },\n];\n\n// \u274C WRONG \u2014 value import crashes the app at runtime and blanks the preview\nimport { IconName } from \"lucide-react/dynamic\";\n```\n";
+//# sourceMappingURL=icons-wrapper.generated.d.ts.map

package/dist/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"icons-wrapper.generated.d.ts","sourceRoot":"","sources":["../../../../../../src/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,qyCA8BnB,CAAC"}

package/dist/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.js

@@ -0,0 +1,34 @@
+// Auto-generated from src/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.md
+// Do not edit directly - edit the .md file instead
+export const content = `Use icons from Lucide React library:
+
+\`\`\`tsx
+import { Icon } from "@/components/ui/icon";
+<Icon icon="heart" />;
+
+import { Button } from "@/components/ui/button";
+<Button>
+  <Icon icon="plus" /> Add Item
+</Button>;
+\`\`\`
+
+**Always use icons rather than emojis unless explicitly requested.**
+
+Use current Lucide icon names, not stale aliases: use \`house\` instead of \`home\`, \`life-buoy\` instead of \`help-circle\` or \`circle-help\`, and \`chart-column-big\` instead of \`bar-chart-3\`.
+
+When storing icon names as data (arrays/objects), type them with \`IconName\`. **\`IconName\` is a TYPE-only export — you MUST import it with the \`type\` keyword.** A value import compiles but CRASHES the app at runtime (\`does not provide an export named 'IconName'\`) and leaves the preview blank, which blocks UI verification. If you hit that error, read \`skills/system/common-import-issues/SKILL.md\`.
+
+\`\`\`tsx
+// ✅ CORRECT — type-only import
+import type { IconName } from "lucide-react/dynamic";
+
+const navItems: { icon: IconName; label: string }[] = [
+  { icon: "house", label: "Home" },
+  { icon: "settings", label: "Settings" },
+];
+
+// ❌ WRONG — value import crashes the app at runtime and blanks the preview
+import { IconName } from "lucide-react/dynamic";
+\`\`\`
+`;
+//# sourceMappingURL=icons-wrapper.generated.js.map

package/dist/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"icons-wrapper.generated.js","sourceRoot":"","sources":["../../../../../../src/ai-service/skills/system/superblocks-frontend/_variants/icons-wrapper.generated.ts"],"names":[],"mappings":"AAAA,mGAAmG;AACnG,mDAAmD;AAEnD,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8BtB,CAAC"}

package/dist/ai-service/skills/system/superblocks-frontend/skill.generated.d.ts

@@ -1,2 +1,2 @@
-export declare const content = "---\nname: superblocks-frontend\ndescription: |\n  Build frontend UI using React, Tailwind CSS, and Superblocks components. Essential for connecting Superblocks UIs with APIs.\n  Use when creating pages, components, handling user interactions, or working with the design system.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# Superblocks Frontend Development\n\nThis skill covers building frontend UI for Superblocks applications using React, Tailwind CSS v4, and the Superblocks component library.\n\n## Platform Overview\n\nThis is a React-based web application platform. Use standard React patterns:\n\n- `useState`, `useEffect`, `useCallback`, `useMemo`\n- Event handlers and controlled components\n- JSX with Tailwind CSS classes\n\n## Using APIs from Frontend\n\n<!-- API_PRIMITIVE_IMPORT_GUIDANCE -->\n\n- **`useApiData`** \u2014 declarative reads with SWR caching (preferred for data loading)\n- **`useApi`** \u2014 imperative mutations (for event-driven actions)\n- **`executeApi`** \u2014 plain Promise outside React (utility functions, event handlers without hooks)\n\n**Data loading** \u2014 auto-fetches on mount and when inputs change (preferred for reads):\n\n```typescript\n// Auto-fetches when email or name changes. No useEffect or HMR guards needed.\n// IMPORTANT: Always use `fetching` to show a loading indicator during refetches.\nconst { data, loading, fetching, isError, error } = useApiData(\"GetUsers\", {\n  email,\n  name,\n});\n```\n\n**Mutations** \u2014 call `run()` manually (for event-driven actions like form submissions):\n\n```typescript\nimport { toast } from \"sonner\";\n\nconst { run: createOrder, loading } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder]);\n```\n\n**Outside React** \u2014 call APIs as a plain Promise (utility functions, event handlers):\n\n```typescript\nconst result = await executeApi(\"GetUsers\", { email });\n```\n\n`useApiData` returns `{ data, loading, fetching, isError, isSuccess, isStale, error, status, fetchStatus, refetch, cancel }`. `data` persists across background refetches (stale-while-revalidate). `loading` is true on first fetch with no cached data. `fetching` is true during any fetch including background refetch. `status` is `\"pending\"` | `\"success\"` | `\"error\"`. `fetchStatus` is `\"idle\"` | `\"fetching\"`. `cancel()` is synchronous (returns `void`).\n\n`useApi` returns `{ run, cancel, reset, loading, data, error, status, variables }`. `data` persists across re-runs (shows previous result while loading). `error` holds the most recent failure, or `undefined` on success. `status` is `\"idle\"` | `\"pending\"` | `\"success\"` | `\"error\"`. `variables` holds the inputs from the most recent `run()`. `reset()` clears all state back to idle. HMR double-fetch prevention is built in \u2014 no `useRef` guard needed.\n\n### useApiData Options\n\n```typescript\nconst { data } = useApiData(\"GetUsers\", { email }, {\n  enabled: true,           // Skip fetching when false (conditional fetching)\n  staleTime: 0,            // Ms before cached data is considered stale (0 = always refetch)\n  retry: 3,                // Retry attempts on failure (false to disable)\n  retryDelay: (n) => ...,  // Custom delay strategy (default: exponential backoff, max 30s)\n  refetchOnWindowFocus: false, // Refetch when tab regains focus\n  refetchOnReconnect: true,    // Refetch when network reconnects\n  refetchInterval: false,      // Polling interval in ms (false = disabled)\n  structuralSharing: false,    // Deep-compare to preserve object identity\n  placeholderData: undefined,  // Shown while the first fetch is in progress\n});\n```\n\n### Cache invalidation and optimistic updates\n\n**Same scope as the read**: After a mutation, prefer `refetch()` from the `useApiData` that loads the data (same component or wherever you can pass `refetch`).\n\n```typescript\nimport { toast } from \"sonner\";\n\nconst { data: orders, refetch } = useApiData(\"GetOrders\", { status });\nconst { run: createOrder } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n    await refetch();\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder, refetch]);\n```\n\n**Cross-scope or broad invalidation**: Use `queryClient.invalidateQueries` when you cannot call that `refetch` (mutation in a different place than the `useApiData`, or you need every cached variant of an API to refetch). For **`queryClient.invalidateQueries`, `buildCacheKey`, `setQueryData`, and any other `queryClient` usage, always import `queryClient` from `@superblocksteam/library`**.\n\n```typescript\nimport { queryClient } from \"@superblocksteam/library\";\nimport { toast } from \"sonner\";\n\nconst { run: createOrder } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n    await queryClient.invalidateQueries(\"GetOrders\");\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder]);\n```\n\n```typescript\n// Optimistic update: set cached data without refetching\nimport { queryClient } from \"@superblocksteam/library\";\n\nconst cacheKey = queryClient.buildCacheKey(\"GetOrders\", { status: \"active\" });\nqueryClient.setQueryData(cacheKey, (old) => ({\n  ...old,\n  orders: [...old.orders, newOrder],\n}));\n```\n\n### Critical API Rules\n\n<!-- API_NAME_GUIDANCE -->\n\n2. **Use `useApiData` for data loading, `useApi` for mutations**: For data fetching, use `useApiData(\"GetUsers\", { email })`. Only use `useApi` for event-driven actions (button clicks, form submissions). Use `executeApi` for API calls outside React components.\n3. **Use the hook's state fields**: Do NOT create separate `useState` for loading or response data \u2014 the hooks manage this for you\n4. **ALWAYS check API interfaces**: NEVER guess the response structure\n5. **Include all parameters**: Even optional ones should be passed as `null`\n6. **ALWAYS use try/catch**: In imperative mode, APIs throw errors when they fail - wrap ALL `run()` calls in try/catch blocks. In declarative mode, check the `error` field for failure details.\n\n### File Handling\n\n**CRITICAL: Files must be wrapped in `{ files: [...] }` format:**\n\n```tsx\n// \u2705 CORRECT - Frontend: wrap files in { files: [...] }\nconst response = await runUploadApi({ userFile: { files: selectedFiles } });\n\n// \u274C WRONG - backend cannot process unwrapped files\nconst response = await runUploadApi({ userFile: selectedFiles });\n```\n\n## Platform Hooks and Functions\n\nAvailable hooks and functions from `@superblocksteam/library`:\n\n### User and Group Context\n\n```typescript\nimport {\n  useSuperblocksUser,\n  useSuperblocksGroups,\n} from \"@superblocksteam/library\";\n\n// Get current user info\nconst user = useSuperblocksUser();\n// user.name, user.email, user.id, user.groups, user.username, user.metadata\n\n// Get organization groups\nconst groups = useSuperblocksGroups();\n```\n\n### Environments and Data Tags\n\nConcepts & terminology:\n\n- `Data tags` are labels for different data segments, such as `Staging`, `Production`, or `us-east`.\n- `Profiles` is the legacy term for the same concept. If a user asks about profiles, treat that as data tags.\n- `Environments` are `Edit`, `Preview`, and `Production`, and each data tag is allowed in one or more of those environments.\n- Clark operates in `Edit` mode, so the data tags visible in app context represent the tags available in `Edit`; do not assume this is the same set that will be available in `Preview` or `Production`.\n- When implementing app code, prefer `useSuperblocksDataTags()`, `dataTags`, and `setDataTag()`.\n\nThe `DataTag` type has these fields (it is an alias for `Profile` from `@superblocksteam/shared`):\n\n```typescript\ntype DataTag = {\n  id: string;\n  key: string;\n  displayName: string; // human-readable label \u2014 use this for display, NOT \"name\"\n  description: string;\n  type: \"RESERVED\" | \"CUSTOM\";\n};\n```\n\nRelevant hooks and functions:\n\n```typescript\nimport { useSuperblocksDataTags, getAppMode } from \"@superblocksteam/library\";\nimport type { DataTag, DataTags } from \"@superblocksteam/library\";\n\n// Manage data tags\nconst { dataTags, setDataTag } = useSuperblocksDataTags();\n// dataTags.available: DataTag[]   \u2014 all tags in the current environment\n// dataTags.selected:  DataTag | undefined \u2014 currently active tag (may be undefined)\n// dataTags.default:   DataTag     \u2014 the default tag\n// setDataTag(dataTag.key)         \u2014 switch the active tag by key\n\n// Read the current app mode when reasoning about environment-specific behavior\nconst appMode = getAppMode();\n```\n\nExample \u2014 data tag switcher using a Select:\n\n```tsx\nconst { dataTags, setDataTag } = useSuperblocksDataTags();\n\n<Select value={dataTags?.selected?.key} onValueChange={setDataTag}>\n  {dataTags?.available.map((tag) => (\n    <SelectItem key={tag.key} value={tag.key}>\n      {tag.displayName}\n    </SelectItem>\n  ))}\n</Select>;\n```\n\n### Embedded Applications\n\n**For embedded applications**, see the `references/embedding.md` file for `useEmbedProperties`, `useEmbedEvent`, and `useEmitEmbedEvent` hooks.\n\n## Logging Out of Integrations\n\nWhen building a \"Log out\" or \"Sign out\" button for apps that use OAuth-like integrations, use `logoutIntegrations` from the library to clear OAuth tokens:\n\n```typescript\nimport { logoutIntegrations } from \"@superblocksteam/library\";\n\nconst handleLogout = async () => {\n  await logoutIntegrations();\n  // Optionally redirect or show confirmation\n};\n```\n\n## Application Architecture\n\n### {{ui}}App.tsx Layout Structure\n\n**For single-page applications:**\n\n- Put all content in `{{ui}}pages/<pageName>/index.tsx`\n- Use components to compose and build the page\n- Keep `{{ui}}App.tsx` minimal with just `<AppProvider>` and `<Outlet />`\n\n**For multi-page applications:**\n\n- Put shared navigation/layout in `{{ui}}App.tsx` (sidebars, headers, footers)\n- Always include `<Outlet />` for page content\n- Always include `<AppProvider />` wrapper\n- Individual pages focus on content, not layout\n\n```tsx\n// \u2705 CORRECT - Multi-page {{ui}}App.tsx layout\n<AppProvider>\n  <div className=\"flex flex-row size-screen\">\n    {/* Sidebar - persistent across all pages */}\n    <div className=\"flex bg-sidebar border-r w-[250px]\">\n      <Navigation />\n    </div>\n\n    {/* Main content area */}\n    <div className=\"flex flex-1 h-full flex-col\">\n      {/* Header - persistent across all pages */}\n      <div className=\"flex bg-header border-b h-[60px]\">\n        <Header />\n      </div>\n\n      {/* Page content area */}\n      <div className=\"flex p-4 flex-1 overflow-auto\">\n        <Outlet />\n      </div>\n    </div>\n  </div>\n</AppProvider>\n```\n\n**PROTECTED: NEVER remove `<AppProvider>` or `<Outlet />` from {{ui}}App.tsx!**\n\n### Page Structure\n\n```tsx\n// \u2705 CORRECT - Page focuses on content only\n<div className=\"flex flex-col gap-4 size-screen overflow-auto\">\n  <h1 className=\"text-3xl font-bold\">Dashboard Content</h1>\n  <Card>{/* Page-specific content */}</Card>\n</div>\n```\n\n**IMPORTANT**: The first div on the page must have `overflow-auto` so the user's page can scroll.\n\n## Routing\n\nUse `react-router@7` in data mode. Standard patterns apply:\n\n- `useNavigate()` for programmatic navigation\n- `useParams()` for route parameters\n- `useSearchParams()` for query strings\n\n**If you add new pages or rename files, you MUST update the router.**\n\nFile edits change the live app immediately, so keep every intermediate state valid:\n\n- Create a page before adding its router reference.\n- Remove router references before deleting a page.\n- To rename a page, create the new page, repoint the router, then delete the old page.\n- Wait for each dependent tool call to return without an error before starting the next step. Batch only independent tool calls.\n\nKeep route elements statically discoverable by the Superblocks editor:\n\n- Prefer direct JSX such as `element: <Page />`.\n- Keep code splitting with top-level `lazy(() => import(\"./pages/Page\"))`\n  bindings.\n- Keep page routes as `children` of the `App` layout route, and put one\n  `<Suspense>` boundary around `<Outlet />` inside `<AppProvider>` in `{{ui}}App.tsx`.\n- A single-argument wrapper such as `element: withSuspense(Page)` is also\n  discoverable when `Page` is directly imported or bound by top-level\n  `React.lazy`.\n- Do not unwrap working routes that use this shape.\n- Do not use nested or multi-argument calls such as\n  `element: withSuspense(makePage(Home))` or\n  `element: withSuspense(Home, opts)`.\n- Do not wrap page JSX in another element, such as\n  `element: <PageErrorBoundary><Page /></PageErrorBoundary>`.\n\n```tsx\nimport { App as AppProvider } from \"@superblocksteam/library\";\nimport { Suspense, lazy } from \"react\";\nimport { Outlet, createBrowserRouter } from \"react-router\";\n\nconst Page = lazy(() => import(\"./pages/Page\"));\n\nconst router = createBrowserRouter([\n  {\n    Component: App,\n    children: [{ path: \"/page\", element: <Page /> }],\n  },\n]);\n\nfunction App() {\n  return (\n    <AppProvider className=\"h-full w-full\">\n      <Suspense fallback={null}>\n        <Outlet />\n      </Suspense>\n    </AppProvider>\n  );\n}\n```\n\n### Page names\n\nA new app ships with one empty page at `{{ui}}pages/Home`, bound as the `/` index route:\n\n```tsx\n{ path: \"/\", index: true, lazy: () => import(\"./pages/Home/index.js\").then((mod) => ({ Component: mod.default })) }\n```\n\n- **Single-page app**: build the landing content in `{{ui}}pages/Home` and keep it named `Home` unless the user asks for something else\n- **Multi-page app**: every page you add beyond the starter gets a descriptive PascalCase name for what it shows (`Dashboard`, `Inventory`, `TopBuilders`), and the starter page keeps `Home` as the app's landing page \u2014 rename it too if the app's landing route is really something else (e.g. `Overview`), keeping it bound to the `/` index route\n- Page names are user-visible in the editor's page switcher, so name them the way you'd label a nav item\n- Never name a page `Page1`, `Page2`, ...\n\n## Design System (Tailwind CSS v4)\n\n**All design tokens are defined in `{{ui}}index.css`**. Apps come with a professional black-and-white theme by default.\n\n### Semantic Tokens Rule\n\n**ALWAYS use semantic tokens** \u2014 NEVER raw Tailwind utilities:\n\n```tsx\n// \u2705 CORRECT\n<Card className=\"bg-background text-foreground border border-border\" />\n\n// \u274C WRONG\n<Card className=\"bg-white text-black border-gray-200\" />\n```\n\n### When to Modify {{ui}}index.css\n\nOnly modify when:\n\n- User explicitly requests branding/theme changes\n- Replicating a specific brand look (e.g., Yelp, Instacart)\n- Migrating an attached third-party app \u2014 see `skills/system/third-party-migration/SKILL.md` (its theme-port rules override the Modification Rules below \u2014 copy source tokens as-is, do not convert to OKLCH or trim the palette)\n- Feature requests (lists, filters, CRUD) do NOT require changes\n\n**Modification Rules:**\n\n- All colors must be in OKLCH format\n- Use semantic names (`--color-warning`, `--shadow-elevated`)\n- Do not remove or rename existing tokens\n- Limit color palette to 5 colors max\n- Avoid gradients unless explicitly requested\n- Minimal font sizes (3 max: body, section heading, main heading)\n\n### Component Variants\n\nUse or create variants instead of one-off styles:\n\n```tsx\n// \u274C WRONG - Hacky inline overrides\n<Button className=\"text-white border-white hover:bg-white\" />\n\n// \u2705 CORRECT - Use a variant\n<Button variant=\"secondary\" />\n```\n\n## Icons\n\nUse icons from Lucide React library:\n\n```tsx\nimport { Icon } from \"@/components/ui/icon\";\n<Icon icon=\"heart\" />;\n\nimport { Button } from \"@/components/ui/button\";\n<Button>\n  <Icon icon=\"plus\" /> Add Item\n</Button>;\n```\n\n**Always use icons rather than emojis unless explicitly requested.**\n\nUse current Lucide icon names, not stale aliases: use `house` instead of `home`, `life-buoy` instead of `help-circle` or `circle-help`, and `chart-column-big` instead of `bar-chart-3`.\n\nWhen storing icon names as data (arrays/objects), type them with `IconName`. **`IconName` is a TYPE-only export \u2014 you MUST import it with the `type` keyword.** A value import compiles but CRASHES the app at runtime (`does not provide an export named 'IconName'`) and leaves the preview blank, which blocks UI verification. If you hit that error, read `skills/system/common-import-issues/SKILL.md`.\n\n```tsx\n// \u2705 CORRECT \u2014 type-only import\nimport type { IconName } from \"lucide-react/dynamic\";\n\nconst navItems: { icon: IconName; label: string }[] = [\n  { icon: \"house\", label: \"Home\" },\n  { icon: \"settings\", label: \"Settings\" },\n];\n\n// \u274C WRONG \u2014 value import crashes the app at runtime and blanks the preview\nimport { IconName } from \"lucide-react/dynamic\";\n```\n\n## Custom Components\n\n**CRITICAL: Component composition is MANDATORY. DO NOT create monolithic pages.**\n\n### The Composition Rule\n\nWhen building ANY feature:\n\n1. **First**, identify reusable parts (list items, cards, forms, filters, headers)\n2. **Then**, create separate component files\n3. **Finally**, compose them together in the page\n\n### When to Create Components\n\n- **Rendering any list** - Extract to a component\n- **Building cards/complex UI** - Each card type is a component\n- **Creating forms** - Form sections are components\n- **Adding filters/headers** - These are components\n- **Page has >50 lines JSX** - Break it down\n\n### Component Boundary Rules\n\n**Inside a custom component:**\n\n- \u2705 Use React hooks (useState, useReducer, useEffect, etc.)\n- \u2705 Use local React state\n- \u2705 Use internal helper components\n- \u2705 Use other registered components\n- \u274C CANNOT call APIs - must pass data into the component\n\n### Example: Proper Component Structure\n\n```tsx\n// {{ui}}components/ProductCard/index.tsx - Extract to component\nimport { Card } from \"@/components/ui/card\";\nimport { Button } from \"@/components/ui/button\";\n\ntype ProductCardProps = {\n  product: {\n    id: string;\n    name: string;\n    image: string;\n  };\n};\n\nexport default function ProductCard(props: ProductCardProps) {\n  return (\n    <Card>\n      <img src={props.product.image} />\n      <h3 className=\"text-lg font-semibold\">{props.product.name}</h3>\n      <Button>Add</Button>\n    </Card>\n  );\n}\n\n// {{ui}}pages/Products/index.tsx - Clean composition\nimport ProductCard from \"@/components/ProductCard\";\n\nconst ProductsPage = () => {\n  const [products, setProducts] = useState([]);\n\n  return (\n    <div className=\"grid grid-cols-3 gap-4\">\n      {products.map((p) => (\n        <ProductCard key={p.id} product={p} />\n      ))}\n    </div>\n  );\n};\n```\n\n## Visual Excellence\n\n**Prioritize visual excellence from the start:**\n\n1. **Design System Enhancement**: Start by enhancing `{{ui}}index.css` with app-specific colors that match the target aesthetic\n2. **Professional Layout Architecture**: Use sophisticated layouts with proper spacing, responsive design\n3. **Rich Interactive Components**: Leverage advanced components with proper variants and states\n4. **Visual Polish**: Add shadows, smooth transitions, skeleton loaders, hover effects, typography hierarchy\n5. **Real-World UI Patterns**: Create layouts that feel like professional applications\n\n**Make applications that look and feel like real, polished products - not basic wireframes.**\n\n### Loading States\n\nLoading behavior must differ based on whether data has already been fetched:\n\n**Initial load (no data yet):** Show skeleton shimmers that mirror the shape of the final content. Never show a blank screen or a generic spinner.\n\n**Refetch / background refresh (data already exists):** Keep showing the existing data. Use `fetching` from `useApiData` to apply a subtle visual indicator: light opacity (e.g. `opacity-70`) to signal a refresh is in progress, plus a non-blocking label such as a small inline spinner, a thin progress bar, or an \"Updating\u2026\" label. **Do not** use `pointer-events-none` or otherwise disable the content \u2014 it must remain fully interactive during refetch.\n\nUse `loading` and `fetching` from `useApiData` to distinguish these states:\n\n```tsx\nconst { data, loading, fetching, isError, error } = useApiData(\"GetOrders\", {\n  status: statusFilter,\n  search,\n});\n\n// Initial load \u2014 no data yet \u2192 show skeleton placeholder\nif (loading) {\n  return <OrderTableSkeleton />;\n}\n\nif (isError) return <ErrorBanner error={error} />;\n\n// Refetch \u2014 data exists \u2192 subtle opacity + indicator, table stays interactive\nreturn (\n  <div>\n    {fetching && <div className=\"text-xs text-muted-foreground\">Updating\u2026</div>}\n    <div className={fetching ? \"opacity-70\" : \"\"}>\n      <OrderTable orders={data.orders} />\n    </div>\n  </div>\n);\n```\n\n```tsx\n// \u274C WRONG \u2014 pointer-events-none disables the table, making it feel broken\nreturn (\n  <div className={fetching ? \"pointer-events-none\" : \"\"}>\n    <OrderTable orders={data.orders} />\n  </div>\n);\n\n// \u274C WRONG \u2014 no loading feedback when filters change\nif (loading) return <Skeleton />;\nreturn <OrderTable orders={data.orders} />;\n```\n\n#### Table Loading Rules\n\n- **Do not** use `pointer-events-none` on a table during loading \u2014 this disables interaction and makes the UI feel broken. During refetch, apply a subtle opacity (e.g. `opacity-70`) plus a non-blocking indicator (e.g., an \"Updating\u2026\" label or a thin progress bar). The table must remain clickable, sortable, and scrollable.\n- **Do not** replace a populated table with a full skeleton on refetch \u2014 this causes disorienting content flashes.\n- **Skeleton tables are only for initial load** (`loading` is true) when there is no data to display yet. Build them to match the real table's column structure (header + a few placeholder rows).\n\n### Efficient Loading Patterns\n\n1. **Always show loading indicators on refetch**: When inputs change (e.g. filters, search), show a non-blocking visual indicator while new data loads. Use `fetching` from `useApiData`.\n2. **Loading State Hierarchy**:\n   - No data yet (`loading`) \u2192 Full skeleton placeholder\n   - Has data, refetching (`fetching` && !`loading`) \u2192 Keep showing current data with a subtle visual indicator: light opacity (e.g. `opacity-70`) plus a non-blocking label (e.g. \"Updating\u2026\" text, thin progress bar, inline spinner). Do not use `pointer-events-none` \u2014 the content must remain fully interactive.\n   - Error state (`isError`) \u2192 Show error with retry option, optionally keep stale data visible\n3. **Debounce Rapid Requests**: Prevent multiple API calls in short succession\n4. **Use useApiData for automatic refetching**: `useApiData` auto-refetches when inputs change and supports `staleTime`, `refetchOnWindowFocus`, `refetchOnReconnect`, `refetchInterval`, and `retry` options.\n\n## Performance Rules\n\n### 1. ALWAYS Paginate Tables and Lists\n\n**NEVER render more than 50 rows without pagination.** Always add client-side pagination:\n\n```tsx\nfunction PaginatedTable({ data }: { data: any[] }) {\n  const PAGE_SIZE = 20;\n  const [page, setPage] = useState(0);\n  const totalPages = Math.ceil(data.length / PAGE_SIZE);\n  const pageData = useMemo(\n    () => data.slice(page * PAGE_SIZE, (page + 1) * PAGE_SIZE),\n    [data, page],\n  );\n\n  useEffect(() => {\n    setPage(0);\n  }, [data.length]);\n\n  return (\n    <>\n      <Table>{/* render pageData rows */}</Table>\n      <span>\n        Page {page + 1} of {totalPages} ({data.length} total rows)\n      </span>\n      <Button\n        onClick={() => setPage((p) => Math.max(0, p - 1))}\n        disabled={page === 0}\n      >\n        Previous\n      </Button>\n      <Button\n        onClick={() => setPage((p) => Math.min(totalPages - 1, p + 1))}\n        disabled={page >= totalPages - 1}\n      >\n        Next\n      </Button>\n    </>\n  );\n}\n```\n\nFor 200+ rows, prefer **server-side pagination**; use cursor/keyset pagination for high offsets instead of `LIMIT`/`OFFSET`.\n\nFor 500+ item lists where pagination doesn't fit the UX (chat messages, infinite scroll feeds, large dropdowns), use **virtualization** (`react-virtuoso` or `@tanstack/react-virtual`) to render only the items visible in the viewport.\n\n### 2. ALWAYS Debounce Input-Driven API Calls\n\n**NEVER call an API directly from onChange.** Debounce search/filter inputs with a 300ms timer:\n\n```tsx\nfunction DebouncedSearch({ onSearch }: { onSearch: (query: string) => void }) {\n  const [localValue, setLocalValue] = useState(\"\");\n  const timerRef = useRef<ReturnType<typeof setTimeout>>();\n  const handleChange = useCallback(\n    (e: React.ChangeEvent<HTMLInputElement>) => {\n      setLocalValue(e.target.value);\n      clearTimeout(timerRef.current);\n      timerRef.current = setTimeout(() => onSearch(e.target.value), 300);\n    },\n    [onSearch],\n  );\n  useEffect(() => () => clearTimeout(timerRef.current), []);\n\n  return (\n    <Input value={localValue} onChange={handleChange} placeholder=\"Search...\" />\n  );\n}\n```\n\n### 3. Memoize Expensive Renders\n\nUse memoization (`memo()`, `useMemo`, `useCallback`) when it prevents measurable re-renders or expensive recomputation:\n\n```tsx\nconst OrderRow = memo(function OrderRow({\n  order,\n  onSelect,\n}: {\n  order: Order;\n  onSelect: (id: string) => void;\n}) {\n  return (\n    <TableRow onClick={() => onSelect(order.id)}>\n      <TableCell>{order.id}</TableCell>...\n    </TableRow>\n  );\n});\n\nconst handleSelect = useCallback((id: string) => {\n  setSelectedId(id);\n}, []);\n\nconst filtered = useMemo(\n  () =>\n    orders.filter((o) => o.status === status).sort((a, b) => b.total - a.total),\n  [orders, status],\n);\n```\n\n### 4. ALWAYS Clean Up Side Effects\n\nClean up timers, event listeners, and subscriptions in `useEffect` return functions:\n\n```tsx\nuseEffect(() => {\n  const handler = (e: KeyboardEvent) => {\n    /* ... */\n  };\n  window.addEventListener(\"keydown\", handler);\n  return () => window.removeEventListener(\"keydown\", handler);\n}, []);\n```\n\n### 5. Cancel In-Flight API Requests on Unmount\n\nFor search/filter patterns, prefer `useApiData` \u2014 it handles cancellation and cleanup automatically:\n\n```tsx\n// useApiData: auto-fetches and cancels on unmount/input change\nconst { data, fetching } = useApiData(\"SearchProducts\", { query });\n```\n\nFor imperative usage with manual cleanup, use the `cancel()` function:\n\n```tsx\nconst { run, cancel } = useApi(\"SearchProducts\");\n\nuseEffect(() => {\n  if (!query) return;\n  run({ query }).catch(console.error);\n  return () => {\n    cancel().catch(() => {});\n  };\n}, [query, run, cancel]);\n```\n";
+export declare const content = "---\nname: superblocks-frontend\ndescription: |\n  Build frontend UI using React, Tailwind CSS, and Superblocks components. Essential for connecting Superblocks UIs with APIs.\n  Use when creating pages, components, handling user interactions, or working with the design system.\nreadOnly: true\nmetadata:\n  author: superblocks\n  version: \"1.0\"\n---\n\n# Superblocks Frontend Development\n\nThis skill covers building frontend UI for Superblocks applications using React, Tailwind CSS v4, and the Superblocks component library.\n\n## Platform Overview\n\nThis is a React-based web application platform. Use standard React patterns:\n\n- `useState`, `useEffect`, `useCallback`, `useMemo`\n- Event handlers and controlled components\n- JSX with Tailwind CSS classes\n\n## Using APIs from Frontend\n\n<!-- API_PRIMITIVE_IMPORT_GUIDANCE -->\n\n- **`useApiData`** \u2014 declarative reads with SWR caching (preferred for data loading)\n- **`useApi`** \u2014 imperative mutations (for event-driven actions)\n- **`executeApi`** \u2014 plain Promise outside React (utility functions, event handlers without hooks)\n\n**Data loading** \u2014 auto-fetches on mount and when inputs change (preferred for reads):\n\n```typescript\n// Auto-fetches when email or name changes. No useEffect or HMR guards needed.\n// IMPORTANT: Always use `fetching` to show a loading indicator during refetches.\nconst { data, loading, fetching, isError, error } = useApiData(\"GetUsers\", {\n  email,\n  name,\n});\n```\n\n**Mutations** \u2014 call `run()` manually (for event-driven actions like form submissions):\n\n```typescript\nimport { toast } from \"sonner\";\n\nconst { run: createOrder, loading } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder]);\n```\n\n**Outside React** \u2014 call APIs as a plain Promise (utility functions, event handlers):\n\n```typescript\nconst result = await executeApi(\"GetUsers\", { email });\n```\n\n`useApiData` returns `{ data, loading, fetching, isError, isSuccess, isStale, error, status, fetchStatus, refetch, cancel }`. `data` persists across background refetches (stale-while-revalidate). `loading` is true on first fetch with no cached data. `fetching` is true during any fetch including background refetch. `status` is `\"pending\"` | `\"success\"` | `\"error\"`. `fetchStatus` is `\"idle\"` | `\"fetching\"`. `cancel()` is synchronous (returns `void`).\n\n`useApi` returns `{ run, cancel, reset, loading, data, error, status, variables }`. `data` persists across re-runs (shows previous result while loading). `error` holds the most recent failure, or `undefined` on success. `status` is `\"idle\"` | `\"pending\"` | `\"success\"` | `\"error\"`. `variables` holds the inputs from the most recent `run()`. `reset()` clears all state back to idle. HMR double-fetch prevention is built in \u2014 no `useRef` guard needed.\n\n### useApiData Options\n\n```typescript\nconst { data } = useApiData(\"GetUsers\", { email }, {\n  enabled: true,           // Skip fetching when false (conditional fetching)\n  staleTime: 0,            // Ms before cached data is considered stale (0 = always refetch)\n  retry: 3,                // Retry attempts on failure (false to disable)\n  retryDelay: (n) => ...,  // Custom delay strategy (default: exponential backoff, max 30s)\n  refetchOnWindowFocus: false, // Refetch when tab regains focus\n  refetchOnReconnect: true,    // Refetch when network reconnects\n  refetchInterval: false,      // Polling interval in ms (false = disabled)\n  structuralSharing: false,    // Deep-compare to preserve object identity\n  placeholderData: undefined,  // Shown while the first fetch is in progress\n});\n```\n\n### Cache invalidation and optimistic updates\n\n**Same scope as the read**: After a mutation, prefer `refetch()` from the `useApiData` that loads the data (same component or wherever you can pass `refetch`).\n\n```typescript\nimport { toast } from \"sonner\";\n\nconst { data: orders, refetch } = useApiData(\"GetOrders\", { status });\nconst { run: createOrder } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n    await refetch();\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder, refetch]);\n```\n\n**Cross-scope or broad invalidation**: Use `queryClient.invalidateQueries` when you cannot call that `refetch` (mutation in a different place than the `useApiData`, or you need every cached variant of an API to refetch). For **`queryClient.invalidateQueries`, `buildCacheKey`, `setQueryData`, and any other `queryClient` usage, always import `queryClient` from `@superblocksteam/library`**.\n\n```typescript\nimport { toast } from \"sonner\";\n\nimport { queryClient } from \"@superblocksteam/library\";\n\nconst { run: createOrder } = useApi(\"CreateOrder\");\n\nconst handleSubmit = useCallback(async () => {\n  try {\n    await createOrder({ item, qty });\n    await queryClient.invalidateQueries(\"GetOrders\");\n  } catch (error) {\n    const message =\n      error && typeof error === \"object\" && \"message\" in error\n        ? String((error as { message: unknown }).message)\n        : String(error);\n    toast.error(\"Error creating order: \" + message);\n  }\n}, [item, qty, createOrder]);\n```\n\n#### Optimistic updates\n\nWhen a mutation changes rows the page is already showing (toggling a checkbox, editing a field inline, deleting or adding a list item), change the cached data first so the UI updates at once, run the mutation, then refetch. If the mutation fails, restore the previous data and show `toast.error`. Do not make the user wait for the write and the refetch before the row changes.\n\n```typescript\nimport { toast } from \"sonner\";\n\nimport { queryClient } from \"@superblocksteam/library\";\n\ntype OrdersData = { orders: Array<{ id: number; shipped: boolean }> };\n\nconst inputs = { status: \"active\" };\nconst { data, refetch } = useApiData(\"GetOrders\", inputs);\nconst { run: updateOrder } = useApi(\"UpdateOrder\");\n\nconst handleToggle = useCallback(\n  async (id: number, shipped: boolean) => {\n    const cacheKey = queryClient.buildCacheKey(\"GetOrders\", inputs);\n    // Undefined when nothing is cached yet (first load, after an invalidation).\n    const previous = queryClient.getQueryData<OrdersData>(cacheKey);\n    if (previous) {\n      queryClient.setQueryData<OrdersData>(cacheKey, {\n        ...previous,\n        orders: previous.orders.map((o) =>\n          o.id === id ? { ...o, shipped } : o,\n        ),\n      });\n    }\n    try {\n      await updateOrder({ id, shipped });\n      await refetch();\n    } catch (error) {\n      // updateOrder throws the API error object ({ code, message }), not an Error.\n      const message =\n        error && typeof error === \"object\" && \"message\" in error\n          ? String((error as { message: unknown }).message)\n          : String(error);\n      if (previous) {\n        queryClient.setQueryData<OrdersData>(cacheKey, previous);\n      }\n      toast.error(\"Could not update order: \" + message);\n    }\n  },\n  [updateOrder, refetch],\n);\n```\n\n- Read the cached data and skip the cache write when there is none, as above. Never read fields off the `old` argument of a `setQueryData` updater without a guard: it can be `undefined`, and a throw there happens outside the `try`, so the write never runs and no toast shows.\n- For deletes, filter the row out of the cached list; for inserts, append it with a temporary id of the same type as the column (for a numeric id, a negative number such as `-Date.now()`, not a string) and let the refetch replace it. Do not send writes for a row that still has the temporary id; disable its controls until the refetch lands.\n- Fire-and-confirm is fine when nothing on the page shows the change yet: a create dialog that closes on success, a one-shot action such as sending a message, or a settings save with no preview.\n\n### Critical API Rules\n\n<!-- API_NAME_GUIDANCE -->\n\n2. **Use `useApiData` for data loading, `useApi` for mutations**: For data fetching, use `useApiData(\"GetUsers\", { email })`. Only use `useApi` for event-driven actions (button clicks, form submissions). Use `executeApi` for API calls outside React components.\n3. **Use the hook's state fields**: Do NOT create separate `useState` for loading or response data \u2014 the hooks manage this for you\n4. **ALWAYS check API interfaces**: NEVER guess the response structure\n5. **Include all parameters**: Even optional ones should be passed as `null`\n6. **ALWAYS use try/catch**: In imperative mode, APIs throw errors when they fail - wrap ALL `run()` calls in try/catch blocks. In declarative mode, check the `error` field for failure details.\n\n### File Handling\n\n**CRITICAL: Files must be wrapped in `{ files: [...] }` format:**\n\n```tsx\n// \u2705 CORRECT - Frontend: wrap files in { files: [...] }\nconst response = await runUploadApi({ userFile: { files: selectedFiles } });\n\n// \u274C WRONG - backend cannot process unwrapped files\nconst response = await runUploadApi({ userFile: selectedFiles });\n```\n\n## Platform Hooks and Functions\n\nAvailable hooks and functions from `@superblocksteam/library`:\n\n### User and Group Context\n\n```typescript\nimport {\n  useSuperblocksUser,\n  useSuperblocksGroups,\n} from \"@superblocksteam/library\";\n\n// Get current user info\nconst user = useSuperblocksUser();\n// user.name, user.email, user.id, user.groups, user.username, user.metadata\n\n// Get organization groups\nconst groups = useSuperblocksGroups();\n```\n\n### Environments and Data Tags\n\nConcepts & terminology:\n\n- `Data tags` are labels for different data segments, such as `Staging`, `Production`, or `us-east`.\n- `Profiles` is the legacy term for the same concept. If a user asks about profiles, treat that as data tags.\n- `Environments` are `Edit`, `Preview`, and `Production`, and each data tag is allowed in one or more of those environments.\n- Clark operates in `Edit` mode, so the data tags visible in app context represent the tags available in `Edit`; do not assume this is the same set that will be available in `Preview` or `Production`.\n- When implementing app code, prefer `useSuperblocksDataTags()`, `dataTags`, and `setDataTag()`.\n\nThe `DataTag` type has these fields (it is an alias for `Profile` from `@superblocksteam/shared`):\n\n```typescript\ntype DataTag = {\n  id: string;\n  key: string;\n  displayName: string; // human-readable label \u2014 use this for display, NOT \"name\"\n  description: string;\n  type: \"RESERVED\" | \"CUSTOM\";\n};\n```\n\nRelevant hooks and functions:\n\n```typescript\nimport { useSuperblocksDataTags, getAppMode } from \"@superblocksteam/library\";\nimport type { DataTag, DataTags } from \"@superblocksteam/library\";\n\n// Manage data tags\nconst { dataTags, setDataTag } = useSuperblocksDataTags();\n// dataTags.available: DataTag[]   \u2014 all tags in the current environment\n// dataTags.selected:  DataTag | undefined \u2014 currently active tag (may be undefined)\n// dataTags.default:   DataTag     \u2014 the default tag\n// setDataTag(dataTag.key)         \u2014 switch the active tag by key\n\n// Read the current app mode when reasoning about environment-specific behavior\nconst appMode = getAppMode();\n```\n\nExample \u2014 data tag switcher using a Select:\n\n```tsx\nconst { dataTags, setDataTag } = useSuperblocksDataTags();\n\n<Select value={dataTags?.selected?.key} onValueChange={setDataTag}>\n  <SelectTrigger>\n    <SelectValue placeholder=\"Select a data tag\" />\n  </SelectTrigger>\n  <SelectContent>\n    {dataTags?.available.map((tag) => (\n      <SelectItem key={tag.key} value={tag.key}>\n        {tag.displayName}\n      </SelectItem>\n    ))}\n  </SelectContent>\n</Select>;\n```\n\n### Embedded Applications\n\n**For embedded applications**, see the `references/embedding.md` file for `useEmbedProperties`, `useEmbedEvent`, and `useEmitEmbedEvent` hooks.\n\n## Logging Out of Integrations\n\nWhen building a \"Log out\" or \"Sign out\" button for apps that use OAuth-like integrations, use `logoutIntegrations` from the library to clear OAuth tokens:\n\n```typescript\nimport { logoutIntegrations } from \"@superblocksteam/library\";\n\nconst handleLogout = async () => {\n  await logoutIntegrations();\n  // Optionally redirect or show confirmation\n};\n```\n\n## Application Architecture\n\n### {{ui}}App.tsx Layout Structure\n\n**For single-page applications:**\n\n- Put all content in `{{ui}}pages/<pageName>/index.tsx`\n- Use components to compose and build the page\n- Keep `{{ui}}App.tsx` minimal with `<AppProvider>`, `<Outlet />`, and `<Toaster />`\n\n**For multi-page applications:**\n\n- Put shared navigation/layout in `{{ui}}App.tsx` (sidebars, headers, footers)\n- Always include `<Outlet />` for page content\n- Always include `<AppProvider />` wrapper\n- Always include `<Toaster />` from `{{ui}}components/common/sonner` (sibling of `<AppProvider>`)\n- Individual pages focus on content, not layout\n\n```tsx\n// \u2705 CORRECT - Multi-page {{ui}}App.tsx layout\n<>\n  <AppProvider>\n    <div className=\"flex flex-row h-full w-full\">\n      {/* Sidebar - persistent across all pages */}\n      <div className=\"flex bg-sidebar border-r w-[250px]\">\n        <Navigation />\n      </div>\n\n      {/* Main content area */}\n      <div className=\"flex flex-1 h-full flex-col\">\n        {/* Header - persistent across all pages */}\n        <div className=\"flex bg-background border-b h-[60px]\">\n          <Header />\n        </div>\n\n        {/* Page content area */}\n        <div className=\"flex p-4 flex-1 overflow-auto\">\n          <Outlet />\n        </div>\n      </div>\n    </div>\n  </AppProvider>\n  <Toaster />\n</>\n```\n\n**PROTECTED: NEVER remove `<AppProvider>`, `<Outlet />`, or `<Toaster />` from {{ui}}App.tsx!**\n\n### Page Structure\n\n```tsx\n// \u2705 CORRECT - Page focuses on content only\n<div className=\"flex flex-col gap-4 h-full w-full overflow-auto\">\n  <h1 className=\"text-3xl font-bold\">Dashboard Content</h1>\n  <Card>{/* Page-specific content */}</Card>\n</div>\n```\n\n**IMPORTANT**: The first div on the page must have `overflow-auto` so the user's page can scroll.\n\n## Routing\n\nUse `react-router@7` in data mode. Standard patterns apply:\n\n- `useNavigate()` for programmatic navigation\n- `useParams()` for route parameters\n- `useSearchParams()` for query strings\n\n**If you add new pages or rename files, you MUST update the router.**\n\nFile edits change the live app immediately, so keep every intermediate state valid:\n\n- Create a page before adding its router reference.\n- Remove router references before deleting a page.\n- To rename a page, create the new page, repoint the router, then delete the old page.\n- Wait for each dependent tool call to return without an error before starting the next step. Batch only independent tool calls.\n\nKeep route elements statically discoverable by the Superblocks editor:\n\n- Prefer direct JSX such as `element: <Page />`.\n- Keep code splitting with top-level `lazy(() => import(\"./pages/Page\"))`\n  bindings.\n- Keep page routes as `children` of the `App` layout route, and put one\n  `<Suspense>` boundary around `<Outlet />` inside `<AppProvider>` in `{{ui}}App.tsx`.\n- A single-argument wrapper such as `element: withSuspense(Page)` is also\n  discoverable when `Page` is directly imported or bound by top-level\n  `React.lazy`.\n- Do not unwrap working routes that use this shape.\n- Do not use nested or multi-argument calls such as\n  `element: withSuspense(makePage(Home))` or\n  `element: withSuspense(Home, opts)`.\n- Do not wrap page JSX in another element, such as\n  `element: <PageErrorBoundary><Page /></PageErrorBoundary>`.\n\n```tsx\nimport { Suspense, lazy } from \"react\";\nimport { Outlet, createBrowserRouter } from \"react-router\";\n\nimport { App as AppProvider } from \"@superblocksteam/library\";\n\nimport { Toaster } from \"./components/common/sonner\";\n\nconst Page = lazy(() => import(\"./pages/Page\"));\n\nconst router = createBrowserRouter([\n  {\n    Component: App,\n    children: [{ path: \"/page\", element: <Page /> }],\n  },\n]);\n\nfunction App() {\n  return (\n    <>\n      <AppProvider className=\"h-full w-full\">\n        <Suspense fallback={null}>\n          <Outlet />\n        </Suspense>\n      </AppProvider>\n      <Toaster />\n    </>\n  );\n}\n```\n\n### Page names\n\nA new app ships with one empty page at `{{ui}}pages/Home`, bound as the `/` index route:\n\n```tsx\n{ path: \"/\", index: true, lazy: () => import(\"./pages/Home/index.js\").then((mod) => ({ Component: mod.default })) }\n```\n\n- **Single-page app**: build the landing content in `{{ui}}pages/Home` and keep it named `Home` unless the user asks for something else\n- **Multi-page app**: every page you add beyond the starter gets a descriptive PascalCase name for what it shows (`Dashboard`, `Inventory`, `TopBuilders`), and the starter page keeps `Home` as the app's landing page \u2014 rename it too if the app's landing route is really something else (e.g. `Overview`), keeping it bound to the `/` index route\n- Page names are user-visible in the editor's page switcher, so name them the way you'd label a nav item\n- Never name a page `Page1`, `Page2`, ...\n\n## Design System (Tailwind CSS v4)\n\n**All design tokens are defined in `{{ui}}index.css`**. Apps come with a professional black-and-white theme by default.\n\n### Semantic Tokens Rule\n\n**ALWAYS use semantic tokens** \u2014 NEVER raw Tailwind utilities:\n\n```tsx\n// \u2705 CORRECT\n<Card className=\"bg-background text-foreground border border-border\" />\n\n// \u274C WRONG\n<Card className=\"bg-white text-black border-gray-200\" />\n```\n\n### When to Modify {{ui}}index.css\n\nOnly modify when:\n\n- User explicitly requests branding/theme changes\n- Replicating a specific brand look (e.g., Yelp, Instacart)\n- Migrating an attached third-party app \u2014 see `skills/system/third-party-migration/SKILL.md` (its theme-port rules override the Modification Rules below \u2014 copy source tokens as-is, do not convert to OKLCH or trim the palette)\n- Feature requests (lists, filters, CRUD) do NOT require changes\n\n**Modification Rules:**\n\n- All colors must be in OKLCH format\n- Use semantic names (`--color-warning`, `--shadow-elevated`)\n- Do not remove or rename existing tokens\n- Limit color palette to 5 colors max\n- Avoid gradients unless explicitly requested\n- Minimal font sizes (3 max: body, section heading, main heading)\n\n### Component Variants\n\nUse or create variants instead of one-off styles:\n\n```tsx\n// \u274C WRONG - Hacky inline overrides\n<Button className=\"text-white border-white hover:bg-white\" />\n\n// \u2705 CORRECT - Use a variant\n<Button variant=\"secondary\" />\n```\n\n### Base UI Components\n\n<!-- BASE_UI_GUIDANCE -->\n\n## Icons\n\n<!-- ICON_GUIDANCE -->\n\n## Custom Components\n\n**CRITICAL: Component composition is MANDATORY. DO NOT create monolithic pages.**\n\n### The Composition Rule\n\nWhen building ANY feature:\n\n1. **First**, identify reusable parts (list items, cards, forms, filters, headers)\n2. **Then**, create separate component files\n3. **Finally**, compose them together in the page\n\n### When to Create Components\n\n- **Rendering any list** - Extract to a component\n- **Building cards/complex UI** - Each card type is a component\n- **Creating forms** - Form sections are components\n- **Adding filters/headers** - These are components\n- **Page has >50 lines JSX** - Break it down\n\n### Component Boundary Rules\n\n**Inside a custom component:**\n\n- \u2705 Use React hooks (useState, useReducer, useEffect, etc.)\n- \u2705 Use local React state\n- \u2705 Use internal helper components\n- \u2705 Use other registered components\n- \u274C CANNOT call APIs - must pass data into the component\n\n### Example: Proper Component Structure\n\n```tsx\n// {{ui}}components/ProductCard/index.tsx - Extract to component\nimport { Button } from \"@/components/ui/button\";\nimport { Card } from \"@/components/ui/card\";\n\ntype ProductCardProps = {\n  product: {\n    id: string;\n    name: string;\n    image: string;\n  };\n};\n\nexport default function ProductCard(props: ProductCardProps) {\n  return (\n    <Card>\n      <img src={props.product.image} />\n      <h3 className=\"text-lg font-semibold\">{props.product.name}</h3>\n      <Button>Add</Button>\n    </Card>\n  );\n}\n\n// {{ui}}pages/Products/index.tsx - Clean composition\nimport ProductCard from \"@/components/ProductCard\";\n\nconst ProductsPage = () => {\n  const [products, setProducts] = useState([]);\n\n  return (\n    <div className=\"grid grid-cols-3 gap-4\">\n      {products.map((p) => (\n        <ProductCard key={p.id} product={p} />\n      ))}\n    </div>\n  );\n};\n```\n\n## Visual Excellence\n\n**Prioritize visual excellence from the start:**\n\n1. **Design System Enhancement**: Start by enhancing `{{ui}}index.css` with app-specific colors that match the target aesthetic\n2. **Professional Layout Architecture**: Use sophisticated layouts with proper spacing, responsive design\n3. **Rich Interactive Components**: Leverage advanced components with proper variants and states\n4. **Visual Polish**: Add shadows, smooth transitions, skeleton loaders, hover effects, typography hierarchy\n5. **Real-World UI Patterns**: Create layouts that feel like professional applications\n\n**Make applications that look and feel like real, polished products - not basic wireframes.**\n\n### Loading States\n\nLoading behavior must differ based on whether data has already been fetched:\n\n**Initial load (no data yet):** Show skeleton shimmers that mirror the shape of the final content. Never show a blank screen or a generic spinner.\n\n**Refetch / background refresh (data already exists):** Keep showing the existing data. Use `fetching` from `useApiData` to apply a subtle visual indicator: light opacity (e.g. `opacity-70`) to signal a refresh is in progress, plus a non-blocking label such as a small inline spinner, a thin progress bar, or an \"Updating\u2026\" label. **Do not** use `pointer-events-none` or otherwise disable the content \u2014 it must remain fully interactive during refetch.\n\nUse `loading` and `fetching` from `useApiData` to distinguish these states:\n\n```tsx\nconst { data, loading, fetching, isError, error } = useApiData(\"GetOrders\", {\n  status: statusFilter,\n  search,\n});\n\n// Initial load \u2014 no data yet \u2192 show skeleton placeholder\nif (loading) {\n  return <OrderTableSkeleton />;\n}\n\nif (isError) return <ErrorBanner error={error} />;\n\n// Refetch \u2014 data exists \u2192 subtle opacity + indicator, table stays interactive\nreturn (\n  <div>\n    {fetching && <div className=\"text-xs text-muted-foreground\">Updating\u2026</div>}\n    <div className={fetching ? \"opacity-70\" : \"\"}>\n      <OrderTable orders={data.orders} />\n    </div>\n  </div>\n);\n```\n\n```tsx\n// \u274C WRONG \u2014 pointer-events-none disables the table, making it feel broken\nreturn (\n  <div className={fetching ? \"pointer-events-none\" : \"\"}>\n    <OrderTable orders={data.orders} />\n  </div>\n);\n\n// \u274C WRONG \u2014 no loading feedback when filters change\nif (loading) return <Skeleton />;\nreturn <OrderTable orders={data.orders} />;\n```\n\n#### Table Loading Rules\n\n- **Do not** use `pointer-events-none` on a table during loading \u2014 this disables interaction and makes the UI feel broken. During refetch, apply a subtle opacity (e.g. `opacity-70`) plus a non-blocking indicator (e.g., an \"Updating\u2026\" label or a thin progress bar). The table must remain clickable, sortable, and scrollable.\n- **Do not** replace a populated table with a full skeleton on refetch \u2014 this causes disorienting content flashes.\n- **Skeleton tables are only for initial load** (`loading` is true) when there is no data to display yet. Build them to match the real table's column structure (header + a few placeholder rows).\n\n### Efficient Loading Patterns\n\n1. **Always show loading indicators on refetch**: When inputs change (e.g. filters, search), show a non-blocking visual indicator while new data loads. Use `fetching` from `useApiData`.\n2. **Loading State Hierarchy**:\n   - No data yet (`loading`) \u2192 Full skeleton placeholder\n   - Has data, refetching (`fetching` && !`loading`) \u2192 Keep showing current data with a subtle visual indicator: light opacity (e.g. `opacity-70`) plus a non-blocking label (e.g. \"Updating\u2026\" text, thin progress bar, inline spinner). Do not use `pointer-events-none` \u2014 the content must remain fully interactive.\n   - Error state (`isError`) \u2192 Show error with retry option, optionally keep stale data visible\n3. **Debounce Rapid Requests**: Prevent multiple API calls in short succession\n4. **Use useApiData for automatic refetching**: `useApiData` auto-refetches when inputs change and supports `staleTime`, `refetchOnWindowFocus`, `refetchOnReconnect`, `refetchInterval`, and `retry` options.\n\n## Performance Rules\n\n### 1. ALWAYS Paginate Tables and Lists\n\n**NEVER render more than 50 rows without pagination.** Always add client-side pagination:\n\n```tsx\nfunction PaginatedTable({ data }: { data: any[] }) {\n  const PAGE_SIZE = 20;\n  const [page, setPage] = useState(0);\n  const totalPages = Math.ceil(data.length / PAGE_SIZE);\n  const pageData = useMemo(\n    () => data.slice(page * PAGE_SIZE, (page + 1) * PAGE_SIZE),\n    [data, page],\n  );\n\n  useEffect(() => {\n    setPage(0);\n  }, [data.length]);\n\n  return (\n    <>\n      <Table>{/* render pageData rows */}</Table>\n      <span>\n        Page {page + 1} of {totalPages} ({data.length} total rows)\n      </span>\n      <Button\n        onClick={() => setPage((p) => Math.max(0, p - 1))}\n        disabled={page === 0}\n      >\n        Previous\n      </Button>\n      <Button\n        onClick={() => setPage((p) => Math.min(totalPages - 1, p + 1))}\n        disabled={page >= totalPages - 1}\n      >\n        Next\n      </Button>\n    </>\n  );\n}\n```\n\nFor 200+ rows, prefer **server-side pagination**; use cursor/keyset pagination for high offsets instead of `LIMIT`/`OFFSET`.\n\nFor 500+ item lists where pagination doesn't fit the UX (chat messages, infinite scroll feeds, large dropdowns), use **virtualization** (`react-virtuoso` or `@tanstack/react-virtual`) to render only the items visible in the viewport.\n\n### 2. ALWAYS Debounce Input-Driven API Calls\n\n**NEVER call an API directly from onChange.** Debounce search/filter inputs with a 300ms timer:\n\n```tsx\nfunction DebouncedSearch({ onSearch }: { onSearch: (query: string) => void }) {\n  const [localValue, setLocalValue] = useState(\"\");\n  const timerRef = useRef<ReturnType<typeof setTimeout>>();\n  const handleChange = useCallback(\n    (e: React.ChangeEvent<HTMLInputElement>) => {\n      setLocalValue(e.target.value);\n      clearTimeout(timerRef.current);\n      timerRef.current = setTimeout(() => onSearch(e.target.value), 300);\n    },\n    [onSearch],\n  );\n  useEffect(() => () => clearTimeout(timerRef.current), []);\n\n  return (\n    <Input value={localValue} onChange={handleChange} placeholder=\"Search...\" />\n  );\n}\n```\n\n### 3. Memoize Expensive Renders\n\nUse memoization (`memo()`, `useMemo`, `useCallback`) when it prevents measurable re-renders or expensive recomputation:\n\n```tsx\nconst OrderRow = memo(function OrderRow({\n  order,\n  onSelect,\n}: {\n  order: Order;\n  onSelect: (id: string) => void;\n}) {\n  return (\n    <TableRow onClick={() => onSelect(order.id)}>\n      <TableCell>{order.id}</TableCell>...\n    </TableRow>\n  );\n});\n\nconst handleSelect = useCallback((id: string) => {\n  setSelectedId(id);\n}, []);\n\nconst filtered = useMemo(\n  () =>\n    orders.filter((o) => o.status === status).sort((a, b) => b.total - a.total),\n  [orders, status],\n);\n```\n\n### 4. ALWAYS Clean Up Side Effects\n\nClean up timers, event listeners, and subscriptions in `useEffect` return functions:\n\n```tsx\nuseEffect(() => {\n  const handler = (e: KeyboardEvent) => {\n    /* ... */\n  };\n  window.addEventListener(\"keydown\", handler);\n  return () => window.removeEventListener(\"keydown\", handler);\n}, []);\n```\n\n### 5. Cancel In-Flight API Requests on Unmount\n\nFor search/filter patterns, prefer `useApiData` \u2014 it handles cancellation and cleanup automatically:\n\n```tsx\n// useApiData: auto-fetches and cancels on unmount/input change\nconst { data, fetching } = useApiData(\"SearchProducts\", { query });\n```\n\nFor imperative usage with manual cleanup, use the `cancel()` function:\n\n```tsx\nconst { run, cancel } = useApi(\"SearchProducts\");\n\nuseEffect(() => {\n  if (!query) return;\n  run({ query }).catch(console.error);\n  return () => {\n    cancel().catch(() => {});\n  };\n}, [query, run, cancel]);\n```\n";
 //# sourceMappingURL=skill.generated.d.ts.map

package/dist/ai-service/skills/system/superblocks-frontend/skill.generated.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-frontend/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,802BA2uBnB,CAAC"}
+{"version":3,"file":"skill.generated.d.ts","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-frontend/skill.generated.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,u25BA0wBnB,CAAC"}

package/dist/ai-service/skills/system/superblocks-frontend/skill.generated.js

@@ -115,9 +115,10 @@ const handleSubmit = useCallback(async () => {
 **Cross-scope or broad invalidation**: Use \`queryClient.invalidateQueries\` when you cannot call that \`refetch\` (mutation in a different place than the \`useApiData\`, or you need every cached variant of an API to refetch). For **\`queryClient.invalidateQueries\`, \`buildCacheKey\`, \`setQueryData\`, and any other \`queryClient\` usage, always import \`queryClient\` from \`@superblocksteam/library\`**.
 
 \`\`\`typescript
-import { queryClient } from "@superblocksteam/library";
 import { toast } from "sonner";
 
+import { queryClient } from "@superblocksteam/library";
+
 const { run: createOrder } = useApi("CreateOrder");
 
 const handleSubmit = useCallback(async () => {
@@ -134,17 +135,57 @@ const handleSubmit = useCallback(async () => {
 }, [item, qty, createOrder]);
 \`\`\`
 
+#### Optimistic updates
+
+When a mutation changes rows the page is already showing (toggling a checkbox, editing a field inline, deleting or adding a list item), change the cached data first so the UI updates at once, run the mutation, then refetch. If the mutation fails, restore the previous data and show \`toast.error\`. Do not make the user wait for the write and the refetch before the row changes.
+
 \`\`\`typescript
-// Optimistic update: set cached data without refetching
+import { toast } from "sonner";
+
 import { queryClient } from "@superblocksteam/library";
 
-const cacheKey = queryClient.buildCacheKey("GetOrders", { status: "active" });
-queryClient.setQueryData(cacheKey, (old) => ({
-  ...old,
-  orders: [...old.orders, newOrder],
-}));
+type OrdersData = { orders: Array<{ id: number; shipped: boolean }> };
+
+const inputs = { status: "active" };
+const { data, refetch } = useApiData("GetOrders", inputs);
+const { run: updateOrder } = useApi("UpdateOrder");
+
+const handleToggle = useCallback(
+  async (id: number, shipped: boolean) => {
+    const cacheKey = queryClient.buildCacheKey("GetOrders", inputs);
+    // Undefined when nothing is cached yet (first load, after an invalidation).
+    const previous = queryClient.getQueryData<OrdersData>(cacheKey);
+    if (previous) {
+      queryClient.setQueryData<OrdersData>(cacheKey, {
+        ...previous,
+        orders: previous.orders.map((o) =>
+          o.id === id ? { ...o, shipped } : o,
+        ),
+      });
+    }
+    try {
+      await updateOrder({ id, shipped });
+      await refetch();
+    } catch (error) {
+      // updateOrder throws the API error object ({ code, message }), not an Error.
+      const message =
+        error && typeof error === "object" && "message" in error
+          ? String((error as { message: unknown }).message)
+          : String(error);
+      if (previous) {
+        queryClient.setQueryData<OrdersData>(cacheKey, previous);
+      }
+      toast.error("Could not update order: " + message);
+    }
+  },
+  [updateOrder, refetch],
+);
 \`\`\`
 
+- Read the cached data and skip the cache write when there is none, as above. Never read fields off the \`old\` argument of a \`setQueryData\` updater without a guard: it can be \`undefined\`, and a throw there happens outside the \`try\`, so the write never runs and no toast shows.
+- For deletes, filter the row out of the cached list; for inserts, append it with a temporary id of the same type as the column (for a numeric id, a negative number such as \`-Date.now()\`, not a string) and let the refetch replace it. Do not send writes for a row that still has the temporary id; disable its controls until the refetch lands.
+- Fire-and-confirm is fine when nothing on the page shows the change yet: a create dialog that closes on success, a one-shot action such as sending a message, or a settings save with no preview.
+
 ### Critical API Rules
 
 <!-- API_NAME_GUIDANCE -->
@@ -232,11 +273,16 @@ Example — data tag switcher using a Select:
 const { dataTags, setDataTag } = useSuperblocksDataTags();
 
 <Select value={dataTags?.selected?.key} onValueChange={setDataTag}>
-  {dataTags?.available.map((tag) => (
-    <SelectItem key={tag.key} value={tag.key}>
-      {tag.displayName}
-    </SelectItem>
-  ))}
+  <SelectTrigger>
+    <SelectValue placeholder="Select a data tag" />
+  </SelectTrigger>
+  <SelectContent>
+    {dataTags?.available.map((tag) => (
+      <SelectItem key={tag.key} value={tag.key}>
+        {tag.displayName}
+      </SelectItem>
+    ))}
+  </SelectContent>
 </Select>;
 \`\`\`
 
@@ -265,47 +311,51 @@ const handleLogout = async () => {
 
 - Put all content in \`{{ui}}pages/<pageName>/index.tsx\`
 - Use components to compose and build the page
-- Keep \`{{ui}}App.tsx\` minimal with just \`<AppProvider>\` and \`<Outlet />\`
+- Keep \`{{ui}}App.tsx\` minimal with \`<AppProvider>\`, \`<Outlet />\`, and \`<Toaster />\`
 
 **For multi-page applications:**
 
 - Put shared navigation/layout in \`{{ui}}App.tsx\` (sidebars, headers, footers)
 - Always include \`<Outlet />\` for page content
 - Always include \`<AppProvider />\` wrapper
+- Always include \`<Toaster />\` from \`{{ui}}components/common/sonner\` (sibling of \`<AppProvider>\`)
 - Individual pages focus on content, not layout
 
 \`\`\`tsx
 // ✅ CORRECT - Multi-page {{ui}}App.tsx layout
-<AppProvider>
-  <div className="flex flex-row size-screen">
-    {/* Sidebar - persistent across all pages */}
-    <div className="flex bg-sidebar border-r w-[250px]">
-      <Navigation />
-    </div>
-
-    {/* Main content area */}
-    <div className="flex flex-1 h-full flex-col">
-      {/* Header - persistent across all pages */}
-      <div className="flex bg-header border-b h-[60px]">
-        <Header />
+<>
+  <AppProvider>
+    <div className="flex flex-row h-full w-full">
+      {/* Sidebar - persistent across all pages */}
+      <div className="flex bg-sidebar border-r w-[250px]">
+        <Navigation />
       </div>
 
-      {/* Page content area */}
-      <div className="flex p-4 flex-1 overflow-auto">
-        <Outlet />
+      {/* Main content area */}
+      <div className="flex flex-1 h-full flex-col">
+        {/* Header - persistent across all pages */}
+        <div className="flex bg-background border-b h-[60px]">
+          <Header />
+        </div>
+
+        {/* Page content area */}
+        <div className="flex p-4 flex-1 overflow-auto">
+          <Outlet />
+        </div>
       </div>
     </div>
-  </div>
-</AppProvider>
+  </AppProvider>
+  <Toaster />
+</>
 \`\`\`
 
-**PROTECTED: NEVER remove \`<AppProvider>\` or \`<Outlet />\` from {{ui}}App.tsx!**
+**PROTECTED: NEVER remove \`<AppProvider>\`, \`<Outlet />\`, or \`<Toaster />\` from {{ui}}App.tsx!**
 
 ### Page Structure
 
 \`\`\`tsx
 // ✅ CORRECT - Page focuses on content only
-<div className="flex flex-col gap-4 size-screen overflow-auto">
+<div className="flex flex-col gap-4 h-full w-full overflow-auto">
   <h1 className="text-3xl font-bold">Dashboard Content</h1>
   <Card>{/* Page-specific content */}</Card>
 </div>
@@ -348,10 +398,13 @@ Keep route elements statically discoverable by the Superblocks editor:
   \`element: <PageErrorBoundary><Page /></PageErrorBoundary>\`.
 
 \`\`\`tsx
-import { App as AppProvider } from "@superblocksteam/library";
 import { Suspense, lazy } from "react";
 import { Outlet, createBrowserRouter } from "react-router";
 
+import { App as AppProvider } from "@superblocksteam/library";
+
+import { Toaster } from "./components/common/sonner";
+
 const Page = lazy(() => import("./pages/Page"));
 
 const router = createBrowserRouter([
@@ -363,11 +416,14 @@ const router = createBrowserRouter([
 
 function App() {
   return (
-    <AppProvider className="h-full w-full">
-      <Suspense fallback={null}>
-        <Outlet />
-      </Suspense>
-    </AppProvider>
+    <>
+      <AppProvider className="h-full w-full">
+        <Suspense fallback={null}>
+          <Outlet />
+        </Suspense>
+      </AppProvider>
+      <Toaster />
+    </>
   );
 }
 \`\`\`
@@ -431,38 +487,13 @@ Use or create variants instead of one-off styles:
 <Button variant="secondary" />
 \`\`\`
 
-## Icons
-
-Use icons from Lucide React library:
-
-\`\`\`tsx
-import { Icon } from "@/components/ui/icon";
-<Icon icon="heart" />;
-
-import { Button } from "@/components/ui/button";
-<Button>
-  <Icon icon="plus" /> Add Item
-</Button>;
-\`\`\`
+### Base UI Components
 
-**Always use icons rather than emojis unless explicitly requested.**
+<!-- BASE_UI_GUIDANCE -->
 
-Use current Lucide icon names, not stale aliases: use \`house\` instead of \`home\`, \`life-buoy\` instead of \`help-circle\` or \`circle-help\`, and \`chart-column-big\` instead of \`bar-chart-3\`.
-
-When storing icon names as data (arrays/objects), type them with \`IconName\`. **\`IconName\` is a TYPE-only export — you MUST import it with the \`type\` keyword.** A value import compiles but CRASHES the app at runtime (\`does not provide an export named 'IconName'\`) and leaves the preview blank, which blocks UI verification. If you hit that error, read \`skills/system/common-import-issues/SKILL.md\`.
-
-\`\`\`tsx
-// ✅ CORRECT — type-only import
-import type { IconName } from "lucide-react/dynamic";
-
-const navItems: { icon: IconName; label: string }[] = [
-  { icon: "house", label: "Home" },
-  { icon: "settings", label: "Settings" },
-];
+## Icons
 
-// ❌ WRONG — value import crashes the app at runtime and blanks the preview
-import { IconName } from "lucide-react/dynamic";
-\`\`\`
+<!-- ICON_GUIDANCE -->
 
 ## Custom Components
 
@@ -498,8 +529,8 @@ When building ANY feature:
 
 \`\`\`tsx
 // {{ui}}components/ProductCard/index.tsx - Extract to component
-import { Card } from "@/components/ui/card";
 import { Button } from "@/components/ui/button";
+import { Card } from "@/components/ui/card";
 
 type ProductCardProps = {
   product: {

package/dist/ai-service/skills/system/superblocks-frontend/skill.generated.js.map

@@ -1 +1 @@
-{"version":3,"file":"skill.generated.js","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-frontend/skill.generated.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,mDAAmD;AAEnD,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2uBtB,CAAC"}
+{"version":3,"file":"skill.generated.js","sourceRoot":"","sources":["../../../../../src/ai-service/skills/system/superblocks-frontend/skill.generated.ts"],"names":[],"mappings":"AAAA,iFAAiF;AACjF,mDAAmD;AAEnD,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0wBtB,CAAC"}