your-ai-workflow-firebase-os 1.2.21 → 1.2.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "your-ai-workflow-firebase-os",
-  "version": "1.2.21",
+  "version": "1.2.22",
   "description": "A complete Firebase-powered admin OS — one React component.",
   "type": "module",
   "main": "dist/your-ai-workflow-firebase-os.cjs.js",

package/scripts/postinstall.js

@@ -114,6 +114,20 @@ copyConfig('forms/contactForm.config.ts', 'contactForm.config.ts');
 copyConfig('forms/supportForm.config.ts', 'supportForm.config.ts');
 console.log('  ✓ Copied configuration files to your src/your-ai-workflow-firebase-os/configs directory');
 
+// Copy microcomponents examples
+const microcomponentsSourceDir = path.join(__dirname, '..', 'src', 'microcomponents');
+const microcomponentsDestDir = path.join(fbosDir, 'microcomponents');
+if (fs.existsSync(microcomponentsSourceDir)) {
+  if (!fs.existsSync(microcomponentsDestDir)) fs.mkdirSync(microcomponentsDestDir, { recursive: true });
+  const files = fs.readdirSync(microcomponentsSourceDir);
+  for (const file of files) {
+    if (file.endsWith('.tsx')) {
+      fs.copyFileSync(path.join(microcomponentsSourceDir, file), path.join(microcomponentsDestDir, file));
+    }
+  }
+  console.log('  ✓ Copied microcomponent examples to your src/your-ai-workflow-firebase-os/microcomponents directory');
+}
+
 // Read and rewrite Home.tsx
 const sourceHomePath = path.join(__dirname, '..', 'src', 'pages', 'Home.tsx');
 if (fs.existsSync(sourceHomePath)) {

package/src/prompts/pages/publicPage.ts

@@ -3,42 +3,38 @@ export const publicPagePrompt = (config: any, forms: string[] = []) => {
     .toLowerCase().replace(/[^a-z0-9]+/g, '_');
   const microName = `${parsedPageName.charAt(0).toUpperCase()}${parsedPageName.slice(1)}Content`;
 
-  return `I need your help building the inner content for a newly created Public Page. This page is powered by the \`PublicPageTemplate\` (located at \`src/templates/PublicPageTemplate.tsx\`).
-
-The page "infrastructure" (routing, header, public accessibility) is already set up and working. Your goal is to design the "Landing Content" that lives inside this page.
-
-### ── Current Page Configuration ──────────────────────────────────────────────
-\`\`\`json
-${JSON.stringify({
-    pageName: config.pageName,
-    pageTitle: config.pageTitle,
-    route: config.route,
-    template: config.template,
-  }, null, 2)}
-\`\`\`
+  return `Create a microcomponent for the Public Landing Page: \`${config.pageName}\`.
+
+### ── Context ────────────────────────────────────────────────────────────────
+- **Route**: \`${config.route}\`
+- **Examples Folder**: Check \`src/your-ai-workflow-firebase-os/microcomponents/\` for reference examples of how to build and insert microcomponents.
 
 ### ── Available Forms ────────────────────────────────────────────────────────
-The following public forms are available in the system. **These are for your information only—do NOT use them unless specifically needed.** Your priority is to listen to the user's specific input and decide if a particular modal, form, or component is actually required for the context of this page:
 ${forms.length > 0 ? forms.map(f => `- ${f}`).join('\n') : '- No public forms found'}
+Use these only if specifically requested by the user.
+
+### ── Your Task ──────────────────────────────────────────────────────────────
+1. **Create Microcomponent**: Build \`src/microcomponents/${microName}.tsx\`.
+2. **Build Content**: Implement landing page content (hero sections, features, etc).
+3. **Register Route**: In \`src/App.tsx\`, map your microcomponent to the \`customRoutes\` prop of \`<FirebaseOS>\`:
+
+\`\`\`tsx
+import { ${microName} } from './microcomponents/${microName}';
+
+// Inside App.tsx:
+<FirebaseOS 
+  customRoutes={{
+    '${config.route}': ${microName}
+  }}
+  // ...
+/>
+\`\`\`
 
-### ── Your Mission ────────────────────────────────────────────────────────────
-1. **Create the Content Layer**: Design a new micro-component at \`src/microcomponents/${microName}.tsx\`.
-2. **Build the UI**: Inside this component, build the landing page content (hero sections, feature grids, contact sections, etc.).
-3. **Inject into Template**: Once created, import and place \`<${microName} />\` inside the main content area of \`src/templates/PublicPageTemplate.tsx\`, replacing the placeholder robot icon and default text.
-
-### ── Guardrails ─────────────────────────────────────────────────────────────
-- **DO NOT** modify the outer layout of \`PublicPageTemplate.tsx\` (back buttons, page header, footer, dynamic title).
-- **DO NOT** change the routing or page exports.
-- Focus exclusively on the inner content box using the micro-component strategy.
-
-### ── Aesthetic & Performance (Theme System) ───────────────────────────────
-Build with the user's active theme in mind:
-- **CSS Variables**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-bg)\`, \`var(--panel-border)\`.
-- **Components**: Re-use \`<Button />\`, \`<Input />\`, \`<ConfirmModal />\`, and \`<ContactPopup />\` natively.
-- **Styles**: Use the \`glass-panel\` class for sections and \`text-gradient\` for headers.
-
-### ── Important Formatting Rules ──────────────────────────────────────────────
-- **NO REDUNDANT HEADERS**: The parent template already injects a large dynamic page title and action buttons. DO NOT add a main \`<h1>\` or \`<h2>\` page title at the top of your micro-component. Start directly with your cards, lists, or sub-sections.
+### ── Guidelines ─────────────────────────────────────────────────────────────
+- **Use Theme Tokens**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-border)\`.
+- **Pre-built UI**: Import \`{ Button, Input, ContactPopup }\` from \`your-ai-workflow-firebase-os\`.
+- **Layout**: Use \`glass-panel\` class for sections. DO NOT add redundant \`<h1>\` page titles (the layout handles this).
+- **DO NOT create React Router routes**. Only use the \`customRoutes\` mapping.
 
 [WHAT SHOULD I BUILD ON THIS PUBLIC PAGE?]`;
 };

package/src/prompts/tabs/crud/admin.ts

@@ -3,61 +3,37 @@ export const adminCrudPrompt = (config: any, recordsCollection: string) => {
     .toLowerCase().replace(/[^a-z0-9]+/g, '_');
   const microName = `${parsedTabName.charAt(0).toUpperCase()}${parsedTabName.slice(1)}Content`;
 
-  return `I need your help building the inner functionality for an **already existing** Admin View. This view is powered by the \`AdminPageTemplate\` (located at \`src/templates/AdminPageTemplate.tsx\`).
-
-The "infrastructure" (routing, header, database connection) is entirely set up and functioning. Your goal is to design the "Dashboard Content" that lives inside this specific admin view.
-
-### ── Current View Configuration ──────────────────────────────────────────────
-\`\`\`json
-${JSON.stringify({
-    viewName: config.tabName,
-    viewTitle: config.tabTitle,
-    route: config.route,
-    template: config.template,
-    storageEnabled: !!config.storage,
-    showActionButton: !!config.showButton,
-    buttonStyle: config.buttonAction || 'primary',
-  }, null, 2)}
-\`\`\`
+  return `Create a microcomponent for the Admin view: \`${config.tabName}\`.
 
-### ── Note on Forms ──────────────────────────────────────────────────────────
-**No forms are needed for this view.** Focus on building the administrative dashboard and management tools requested by the user.
+### ── Context ────────────────────────────────────────────────────────────────
+- **Route**: \`${config.route}\`
+- **Data Collection**: \`${recordsCollection}\`
+- **Storage**: ${config.storage ? "Enabled (admin_files/)" : "Disabled"}
+- **Examples Folder**: Check \`src/your-ai-workflow-firebase-os/microcomponents/\` for reference examples of how to build and insert microcomponents.
 
-### ── Data & Storage Architecture ─────────────────────────────────────────────
-The app is already configured to handle data for this specific view using these paths:
-- **Firestore Collection**: \`${recordsCollection}\` (Use this for all view data).
-- **Storage Layer**: ${config.storage ? "Enabled. Uploads are handled via \`admin_files/\` folder in Storage and mirrored to a shared Firestore collection for tracking." : "Disabled for this view."}
-- **Access Level**: Full Admin Access. This view is only visible to users with the 'admin' role.
+### ── Your Task ──────────────────────────────────────────────────────────────
+1. **Create Microcomponent**: Build \`src/microcomponents/${microName}.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top.
+2. **Handle UX/UI**: Implement the required admin dashboard interface (charts, lists, management tools). Write your own Firebase queries using the provided collection. No forms are needed.
+3. **Register Route**: In \`src/App.tsx\`, map your microcomponent to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 
-### ── Your Mission ────────────────────────────────────────────────────────────
-1. **Create the Page**: Create a full page component at \`src/pages/\${microName}Page.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top of the content area.
-2. **Handle UX/UI**: Inside this component, build the interface (lists, charts, management forms, or any feature requested).
-3. **Register the Route**: Open \`src/App.tsx\` and map this component to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 \`\`\`tsx
-import { \${microName}Page } from './pages/\${microName}Page';
+import { ${microName} } from './microcomponents/${microName}';
 
 // Inside App.tsx:
 <FirebaseOS 
   customRoutes={{
-    '\${config.route}': \${microName}Page
+    '${config.route}': ${microName}
   }}
   // ...
 />
 \`\`\`
 
-### ── Guardrails ─────────────────────────────────────────────────────────────
-- **CRITICAL: DO NOT CREATE A NEW ROUTE IN REACT ROUTER.** You are only mapping a component to an existing dynamic route via \\\`customRoutes\\\`.
-- **Database Logic**: You must write your own database queries inside the component using the provided collection names.
-
-### ── Aesthetic & Performance (Theme System) ───────────────────────────────
-Build with the user's active theme in mind:
-- **CSS Variables**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-bg)\`, \`var(--panel-border)\`.
-- **Components**: Re-use \`<Button />\`, \`<Input />\`, \`<ConfirmModal />\`, and \`<DashboardNav />\` natively.
-- **Styles**: Use \`glass-panel\` and \`text-gradient\` for a premium look.
-- **Example**: See \`src/microcomponents/AdminExampleContent.tsx\` for a structural reference.
-
-### ── Important Formatting Rules ──────────────────────────────────────────────
-- **NO REDUNDANT HEADERS**: The parent template already injects a large dynamic page title and action buttons. DO NOT add a main \`<h1>\` or \`<h2>\` page title at the top of your micro-component. Start directly with your cards, lists, or sub-sections.
+### ── Guidelines ─────────────────────────────────────────────────────────────
+- **Use Theme Tokens**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-border)\`.
+- **Pre-built UI**: Import \`{ Button, Input, ConfirmModal }\` from \`your-ai-workflow-firebase-os\`.
+- **Layout**: Use \`glass-panel\` class for cards. DO NOT add redundant \`<h1>\` page titles (the layout handles this).
+- **DO NOT create React Router routes**. Only use the \`customRoutes\` mapping.
 
 [WHAT FEATURES SHOULD I ADD TO THIS ADMIN VIEW?]`;
 };
+

package/src/prompts/tabs/crud/private.ts

@@ -1,65 +1,39 @@
-export const privateCrudPrompt = (config: any, recordsCollection: string, forms: string[] = []) => {
+export const privateCrudPrompt = (config: any, recordsCollection: string) => {
   const parsedTabName = (config.tabName || config.pageId || 'private_page')
     .toLowerCase().replace(/[^a-z0-9]+/g, '_');
   const microName = `${parsedTabName.charAt(0).toUpperCase()}${parsedTabName.slice(1)}Content`;
 
-  return `I need your help building the inner functionality for an **already existing** Private User View. This view is powered by the \`PrivatePageTemplate\` (located at \`src/templates/PrivatePageTemplate.tsx\`).
+  return `Create a microcomponent for the Private view: \`${config.tabName}\`.
 
-The "infrastructure" (auth-guards, dynamic routing, navigation menus, database sync) is entirely set up and functioning. Your task is strictly to design the "Dashboard Content" that lives inside this specific user view.
+### ── Context ────────────────────────────────────────────────────────────────
+- **Route**: \`${config.route}\`
+- **Data Collection**: \`${recordsCollection}\`
+- **Storage**: ${config.storage ? "Enabled (user_files/)" : "Disabled"}
+- **Security**: Data must be filtered by \`where('uid', '==', user.uid)\`.
+- **Examples Folder**: Check \`src/your-ai-workflow-firebase-os/microcomponents/\` for reference examples of how to build and insert microcomponents.
 
-### ── Current View Configuration ──────────────────────────────────────────────
-\`\`\`json
-${JSON.stringify({
-    viewName: config.tabName,
-    viewTitle: config.tabTitle,
-    route: config.route,
-    template: config.template,
-    storageEnabled: !!config.storage,
-    showActionButton: !!config.showButton,
-    availablePrivateForms: forms,
-  }, null, 2)}
-\`\`\`
-
-### ── Available Forms ────────────────────────────────────────────────────────
-The following private forms are available in the system. **These are for your information only—do NOT use them unless specifically needed.** Your priority is to listen to the user's specific input and decide if a particular modal, form, or component is actually required for the context of this page:
-${forms.length > 0 ? forms.map(f => `- ${f}`).join('\n') : '- No private forms found'}
-
-### ── Data & Storage Architecture ─────────────────────────────────────────────
-Every user sees their own unique data on this page. The system is rigged to handle this isolation:
-- **Firestore Collection**: \`${recordsCollection}\`. The template already filters this by \`uid == current_user.uid\`. Use this for all record storage.
-- **Storage Layer**: ${config.storage ? "Enabled. User files are saved to \`user_files/\` and strictly isolated by user ID." : "Disabled for this view."}
-- **Access Level**: Private. Only the owner of the data can view or modify these records.
+### ── Your Task ──────────────────────────────────────────────────────────────
+1. **Create Microcomponent**: Build \`src/microcomponents/${microName}.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top.
+2. **Handle UX/UI**: Implement the required private dashboard interface (charts, lists, management tools). Write your own Firebase queries using the provided collection. No forms are needed.
+3. **Register Route**: In \`src/App.tsx\`, map your microcomponent to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 
-### ── Your Mission ────────────────────────────────────────────────────────────
-1. **Create the Page**: Create a full page component at \`src/pages/\${microName}Page.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top of the content area.
-2. **Handle UX/UI**: Inside this component, build the interface (lists, charts, forms, etc).
-3. **Register the Route**: Open \`src/App.tsx\` and map this component to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 \`\`\`tsx
-import { \${microName}Page } from './pages/\${microName}Page';
+import { ${microName} } from './microcomponents/${microName}';
 
 // Inside App.tsx:
 <FirebaseOS 
   customRoutes={{
-    '\${config.route}': \${microName}Page
+    '${config.route}': ${microName}
   }}
   // ...
 />
 \`\`\`
 
-### ── Guardrails ─────────────────────────────────────────────────────────────
-- **CRITICAL: DO NOT CREATE A NEW ROUTE IN REACT ROUTER.** You are only mapping a component to an existing dynamic route via \\\`customRoutes\\\`.
-- **Database Logic**: You must write your own database queries inside the component using the provided collection names.
-- Re-use the \`ContactPopup\` component with the available private forms if the user needs to submit requests.
-
-### ── Aesthetic & Performance (Theme System) ───────────────────────────────
-Build with the user's active theme in mind:
-- **CSS Variables**: Use \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-bg)\`, \`var(--panel-border)\`.
-- **Components**: Re-use \`<Button />\`, \`<Input />\`, \`<ConfirmModal />\`, and \`<DashboardNav />\` natively.
-- **Styles**: Use \`glass-panel\` and \`text-gradient\` for a premium look.
-- **Example**: See \`src/microcomponents/PrivateExampleContent.tsx\` for a structural reference.
-
-### ── Important Formatting Rules ──────────────────────────────────────────────
-- **NO REDUNDANT HEADERS**: The parent template already injects a large dynamic page title and action buttons. DO NOT add a main \`<h1>\` or \`<h2>\` page title at the top of your micro-component. Start directly with your cards, lists, or sub-sections.
+### ── Guidelines ─────────────────────────────────────────────────────────────
+- **Use Theme Tokens**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-border)\`.
+- **Pre-built UI**: Import \`{ Button, Input, ConfirmModal }\` from \`your-ai-workflow-firebase-os\`.
+- **Layout**: Use \`glass-panel\` class for cards. DO NOT add redundant \`<h1>\` page titles (the layout handles this).
+- **DO NOT create React Router routes**. Only use the \`customRoutes\` mapping.
 
 [WHAT SHOULD I BUILD INSIDE THIS PRIVATE VIEW?]`;
 };

package/src/prompts/tabs/crud/shared.ts

@@ -3,61 +3,37 @@ export const sharedCrudPrompt = (config: any, recordsCollection: string) => {
     .toLowerCase().replace(/[^a-z0-9]+/g, '_');
   const microName = `${parsedTabName.charAt(0).toUpperCase()}${parsedTabName.slice(1)}Content`;
 
-  return `I need your help building the inner functionality for an **already existing** Shared Member View. This view is powered by the \`SharedPageTemplate\` (located at \`src/templates/SharedPageTemplate.tsx\`).
+  return `Create a microcomponent for the Shared view: \`${config.tabName}\`.
 
-The "infrastructure" (real-time sync, collaborative routing) is entirely set up and functioning. Your goal is to design the "Community Content" that lives inside this specific shared view.
+### ── Context ────────────────────────────────────────────────────────────────
+- **Route**: \`${config.route}\`
+- **Data Collection**: \`${recordsCollection}\`
+- **Storage**: ${config.storage ? "Enabled (mem_files/)" : "Disabled"}
+- **Security**: Data is visible to all authenticated members. Only admins and the original creator can edit/delete.
+- **Examples Folder**: Check \`src/your-ai-workflow-firebase-os/microcomponents/\` for reference examples of how to build and insert microcomponents.
 
-### ── Current View Configuration ──────────────────────────────────────────────
-\`\`\`json
-${JSON.stringify({
-    viewName: config.tabName,
-    viewTitle: config.tabTitle,
-    route: config.route,
-    template: config.template,
-    storageEnabled: !!config.storage,
-    showActionButton: !!config.showButton,
-  }, null, 2)}
-\`\`\`
-
-### ── Note on Forms ──────────────────────────────────────────────────────────
-**No forms are needed for this view.** Focus on building the collaborative features and shared content areas requested by the user.
-
-### ── Data & Storage Architecture ─────────────────────────────────────────────
-All logged-in members share the data on this page. The system is configured for collaboration:
-- **Firestore Collection**: \`${recordsCollection}\`. All authenticated users can read and create records here. The template ensures only creators can edit/delete their own items.
-- **Storage Layer**: ${config.storage ? "Enabled. Shared files are saved to \`mem_files/\` and are visible to all members." : "Disabled for this view."}
-- **Access Level**: Shared Member Access. Requires authentication.
+### ── Your Task ──────────────────────────────────────────────────────────────
+1. **Create Microcomponent**: Build \`src/microcomponents/${microName}.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top.
+2. **Handle UX/UI**: Implement the required shared dashboard interface (charts, lists, management tools). Write your own Firebase queries using the provided collection. No forms are needed.
+3. **Register Route**: In \`src/App.tsx\`, map your microcomponent to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 
-### ── Your Mission ────────────────────────────────────────────────────────────
-1. **Create the Page**: Create a full page component at \`src/pages/\${microName}Page.tsx\`. Include \`<DashboardNav />\` from \`your-ai-workflow-firebase-os\` at the top of the content area.
-2. **Handle UX/UI**: Inside this component, build the collaborative interface (group lists, message boards, shared resource trackers).
-3. **Register the Route**: Open \`src/App.tsx\` and map this component to the \`customRoutes\` prop of \`<FirebaseOS>\`:
 \`\`\`tsx
-import { \${microName}Page } from './pages/\${microName}Page';
+import { ${microName} } from './microcomponents/${microName}';
 
 // Inside App.tsx:
 <FirebaseOS 
   customRoutes={{
-    '\${config.route}': \${microName}Page
+    '${config.route}': ${microName}
   }}
   // ...
 />
 \`\`\`
 
-### ── Guardrails ─────────────────────────────────────────────────────────────
-- **CRITICAL: DO NOT CREATE A NEW ROUTE IN REACT ROUTER.** You are only mapping a component to an existing dynamic route via \\\`customRoutes\\\`.
-- **Database Logic**: You must write your own database queries inside the component using the provided collection names.
-- **NEVER** expose administrative control settings in this shared view.
-
-### ── Aesthetic & Performance (Theme System) ───────────────────────────────
-Build with the user's active theme in mind:
-- **CSS Variables**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-bg)\`, \`var(--panel-border)\`.
-- **Components**: Re-use \`<Button />\`, \`<Input />\`, \`<ConfirmModal />\`, and \`<DashboardNav />\` natively.
-- **Styles**: Use \`glass-panel\` and \`text-gradient\` for a premium look.
-- **Example**: See \`src/microcomponents/SharedExampleContent.tsx\` for a structural reference.
-
-### ── Important Formatting Rules ──────────────────────────────────────────────
-- **NO REDUNDANT HEADERS**: The parent template already injects a large dynamic page title and action buttons. DO NOT add a main \`<h1>\` or \`<h2>\` page title at the top of your micro-component. Start directly with your cards, lists, or sub-sections.
+### ── Guidelines ─────────────────────────────────────────────────────────────
+- **Use Theme Tokens**: \`var(--bg-color)\`, \`var(--fg-color)\`, \`var(--accent-color)\`, \`var(--panel-border)\`.
+- **Pre-built UI**: Import \`{ Button, Input, ConfirmModal }\` from \`your-ai-workflow-firebase-os\`.
+- **Layout**: Use \`glass-panel\` class for cards. DO NOT add redundant \`<h1>\` page titles (the layout handles this).
+- **DO NOT create React Router routes**. Only use the \`customRoutes\` mapping.
 
-[WHAT SHARED FEATURE SHOULD I BUILD IN THIS VIEW?]`;
+[WHAT FEATURES SHOULD I ADD TO THIS SHARED VIEW?]`;
 };

package/src/templates/PrivatePageTemplate.tsx

@@ -56,7 +56,7 @@ export function PrivatePageTemplate({ config }: { config: any }) {
   const [editNote, setEditNote] = useState('');
   const [editFields, setEditFields] = useState<{key: string; value: string}[]>([]);
   const fileInputRef = useRef<HTMLInputElement>(null);
-  const [availableForms, setAvailableForms] = useState<string[]>([]);
+
 
   const parsedTabName = (config.tabName || config.pageId || 'private_page')
     .toLowerCase().replace(/[^a-z0-9]+/g, '_');
@@ -65,7 +65,7 @@ export function PrivatePageTemplate({ config }: { config: any }) {
   useEffect(() => {
     document.title = config.tabTitle || config.tabName || themeConfig.appName || 'Firebase OS';
     getDocs(collection(db, 'sys_forms')).then(snap => {
-       setAvailableForms(snap.docs.filter(d => d.data().formType === 'private').map(doc => doc.id));
+
     });
   }, [config.tabTitle, config.tabName, themeConfig.appName]);
 
@@ -411,7 +411,7 @@ export function PrivatePageTemplate({ config }: { config: any }) {
   };
 
   // ── Prompt text ───────────────────────────────────────────────────────────
-  const promptText = privateCrudPrompt(config, recordsCollection, availableForms);
+  const promptText = privateCrudPrompt(config, recordsCollection);
 
   const handleCopyPrompt = () => {
     navigator.clipboard.writeText(promptText);