@wix/auto-patterns 1.44.0 → 1.46.0

package/dist/types/utils/bi/BiBulkDeleteReporter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"BiBulkDeleteReporter.d.ts","sourceRoot":"","sources":["../../../../src/utils/bi/BiBulkDeleteReporter.ts"],"names":[],"mappings":"AAIA,OAAO,EAAE,UAAU,EAAE,MAAM,aAAa,CAAC;AAEzC,MAAM,MAAM,kBAAkB,GAAG,wBAAwB,GAAG,YAAY,CAAC;AAEzE,MAAM,WAAW,kBAAkB;IACjC,WAAW,EAAE,OAAO,CAAC;IACrB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,kBAAkB,CAAC;CAC9B;AAED,MAAM,WAAW,0BAA0B;IACzC,QAAQ,CAAC,EAAE,UAAU,CAAC;IACtB,cAAc,EAAE,GAAG,EAAE,CAAC;IACtB,WAAW,EAAE,OAAO,CAAC;IACrB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,kBAAkB,CAAC;CAC9B;AAED,qBAAa,oBAAoB;IAC/B,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAa;IACvC,OAAO,CAAC,QAAQ,CAAC,cAAc,CAAQ;IACvC,OAAO,CAAC,QAAQ,CAAC,WAAW,CAAU;IACtC,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAS;IACjC,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAqB;gBAElC,MAAM,EAAE,0BAA0B;IAQ9C,OAAO,CAAC,WAAW;IAYnB,UAAU;IAQV,UAAU,CAAC,OAAO,EAAE,QAAQ,GAAG,QAAQ,GAAG,GAAG;CAY9C"}

package/dist/types/utils/bi/index.d.ts

@@ -0,0 +1,2 @@
+export * from './BiBulkDeleteReporter';
+//# sourceMappingURL=index.d.ts.map

package/dist/types/utils/bi/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/utils/bi/index.ts"],"names":[],"mappings":"AAAA,cAAc,wBAAwB,CAAC"}

package/dist/types/utils/filterCreators.d.ts

@@ -1,3 +1,4 @@
+import { FilterOperator } from '@wix/patterns';
 import { DynamicOptionsFilterConfig, EnumFilterConfig, Field, SchemaConfig } from '../types';
 import { FilterOptions } from '../hooks/useFiltersState';
 interface BaseFilterParams {
@@ -19,6 +20,10 @@ export declare const createBooleanFilter: ({ id, fieldId, fieldDefinition, commo
         falseLabel?: string;
     };
 }) => FilterOptions;
+export declare const createHasValueFilter: ({ id, fieldId, fieldDefinition, commonFilterProps, hasValueLabel, noValueLabel, }: BaseFilterParams & {
+    hasValueLabel?: string;
+    noValueLabel?: string;
+}) => FilterOptions;
 export declare const createNumberFilter: ({ id, fieldId, fieldDefinition, commonFilterProps, config, }: BaseFilterParams & {
     config?: {
         min?: number;
@@ -35,5 +40,13 @@ export declare const createReferenceFilter: ({ id, fieldId, fieldDefinition, com
         referencedSchema: SchemaConfig;
     };
 }) => FilterOptions;
+export declare const createOperatorFilter: ({ id, fieldId, fieldDefinition, commonFilterProps, additionalParams, }: BaseFilterParams & {
+    additionalParams: {
+        operators: FilterOperator[];
+    };
+    config?: {
+        placeholder?: string;
+    };
+}) => FilterOptions;
 export {};
 //# sourceMappingURL=filterCreators.d.ts.map

package/dist/types/utils/filterCreators.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"filterCreators.d.ts","sourceRoot":"","sources":["../../../src/utils/filterCreators.ts"],"names":[],"mappings":"AAMA,OAAO,EACL,0BAA0B,EAC1B,gBAAgB,EAChB,KAAK,EACL,YAAY,EACb,MAAM,UAAU,CAAC;AAClB,OAAO,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAC;AAOzD,UAAU,gBAAgB;IACxB,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,iBAAiB,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IACvC,eAAe,EAAE,KAAK,CAAC;CACxB;AAED,eAAO,MAAM,oBAAoB,GAAI,8DAMlC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,IAAI,CAAC,EAAE,iBAAiB,GAAG,aAAa,GAAG,SAAS,CAAC;QACrD,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;QACnB,WAAW,CAAC,EAAE,OAAO,CAAC;KACvB,CAAC;CACH,KAAG,aAWF,CAAC;AAEH,eAAO,MAAM,mBAAmB,GAAI,8DAMjC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,SAAS,CAAC,EAAE,MAAM,CAAC;QACnB,UAAU,CAAC,EAAE,MAAM,CAAC;KACrB,CAAC;CACH,KAAG,aAyBF,CAAC;AAEH,eAAO,MAAM,kBAAkB,GAAI,8DAMhC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,eAAe,CAAC,EAAE,OAAO,CAAC;KAC3B,CAAC;CACH,KAAG,aAWF,CAAC;AAEH,eAAO,MAAM,gBAAgB,GAAI,8DAM9B,gBAAgB,GAAG;IACpB,MAAM,EAAE,gBAAgB,CAAC;CAC1B,KAAG,aAkBH,CAAC;AAEF,eAAO,MAAM,qBAAqB,GAAI,gFAOnC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE,0BAA0B,CAAC;IACpC,gBAAgB,EAAE;QAChB,gBAAgB,EAAE,YAAY,CAAC;KAChC,CAAC;CACH,KAAG,aAUH,CAAC"}
+{"version":3,"file":"filterCreators.d.ts","sourceRoot":"","sources":["../../../src/utils/filterCreators.tsx"],"names":[],"mappings":"AACA,OAAO,EAKL,cAAc,EACf,MAAM,eAAe,CAAC;AAKvB,OAAO,EACL,0BAA0B,EAC1B,gBAAgB,EAChB,KAAK,EACL,YAAY,EACb,MAAM,UAAU,CAAC;AAClB,OAAO,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAC;AAUzD,UAAU,gBAAgB;IACxB,EAAE,EAAE,MAAM,CAAC;IACX,OAAO,EAAE,MAAM,CAAC;IAChB,iBAAiB,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IACvC,eAAe,EAAE,KAAK,CAAC;CACxB;AAED,eAAO,MAAM,oBAAoB,GAAI,8DAMlC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,IAAI,CAAC,EAAE,iBAAiB,GAAG,aAAa,GAAG,SAAS,CAAC;QACrD,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;QACnB,WAAW,CAAC,EAAE,OAAO,CAAC;KACvB,CAAC;CACH,KAAG,aAWF,CAAC;AAEH,eAAO,MAAM,mBAAmB,GAAI,8DAMjC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,SAAS,CAAC,EAAE,MAAM,CAAC;QACnB,UAAU,CAAC,EAAE,MAAM,CAAC;KACrB,CAAC;CACH,KAAG,aAyBF,CAAC;AAEH,eAAO,MAAM,oBAAoB,GAAI,mFAOlC,gBAAgB,GAAG;IACpB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,YAAY,CAAC,EAAE,MAAM,CAAC;CACvB,KAAG,aAyCF,CAAC;AAEH,eAAO,MAAM,kBAAkB,GAAI,8DAMhC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE;QACP,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,GAAG,CAAC,EAAE,MAAM,CAAC;QACb,eAAe,CAAC,EAAE,OAAO,CAAC;KAC3B,CAAC;CACH,KAAG,aAWF,CAAC;AAEH,eAAO,MAAM,gBAAgB,GAAI,8DAM9B,gBAAgB,GAAG;IACpB,MAAM,EAAE,gBAAgB,CAAC;CAC1B,KAAG,aAkBH,CAAC;AAOF,eAAO,MAAM,qBAAqB,GAAI,gFAOnC,gBAAgB,GAAG;IACpB,MAAM,CAAC,EAAE,0BAA0B,CAAC;IACpC,gBAAgB,EAAE;QAChB,gBAAgB,EAAE,YAAY,CAAC;KAChC,CAAC;CACH,KAAG,aAaH,CAAC;AAEF,eAAO,MAAM,oBAAoB,GAAI,wEAMlC,gBAAgB,GAAG;IACpB,gBAAgB,EAAE;QAChB,SAAS,EAAE,cAAc,EAAE,CAAC;KAC7B,CAAC;IACF,MAAM,CAAC,EAAE;QACP,WAAW,CAAC,EAAE,MAAM,CAAC;KACtB,CAAC;CACH,KAAG,aAWH,CAAC"}

package/dist/types/utils/schema/getImageFieldId.d.ts

@@ -0,0 +1,7 @@
+import { Field } from '../../types';
+/**
+ * Finds the ID of the first IMAGE type field in a fields map.
+ * Useful for displaying avatar/thumbnail alongside reference field names.
+ */
+export declare const getImageFieldId: (fields: Record<string, Field | undefined>) => string | undefined;
+//# sourceMappingURL=getImageFieldId.d.ts.map

package/dist/types/utils/schema/getImageFieldId.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"getImageFieldId.d.ts","sourceRoot":"","sources":["../../../../src/utils/schema/getImageFieldId.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,EAAE,MAAM,aAAa,CAAC;AAEpC;;;GAGG;AACH,eAAO,MAAM,eAAe,GAC1B,QAAQ,MAAM,CAAC,MAAM,EAAE,KAAK,GAAG,SAAS,CAAC,KACxC,MAAM,GAAG,SAEX,CAAC"}

package/dist/types/utils/schema/index.d.ts

@@ -0,0 +1,3 @@
+export { getImageFieldId } from './getImageFieldId';
+export { fetchReferenceItems, extractReferenceDisplayValues, type ReferenceItem, type FetchReferenceItemsResult, type ReferenceDisplayValues, } from './referenceUtils';
+//# sourceMappingURL=index.d.ts.map

package/dist/types/utils/schema/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../src/utils/schema/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACpD,OAAO,EACL,mBAAmB,EACnB,6BAA6B,EAC7B,KAAK,aAAa,EAClB,KAAK,yBAAyB,EAC9B,KAAK,sBAAsB,GAC5B,MAAM,kBAAkB,CAAC"}

package/dist/types/utils/schema/referenceUtils.d.ts

@@ -0,0 +1,18 @@
+import { fetchCmsData } from '../../dataSourceAdapters/cms/fetchCmsData';
+import { SchemaConfig } from '../../types';
+export interface ReferenceItem {
+    id: string;
+    name: string;
+    image?: string;
+}
+export interface FetchReferenceItemsResult {
+    items: ReferenceItem[];
+    total: number;
+}
+export interface ReferenceDisplayValues {
+    name: string | undefined;
+    image: string | undefined;
+}
+export declare const fetchReferenceItems: (collectionId: string, query: Parameters<typeof fetchCmsData>[1], schema: SchemaConfig) => Promise<FetchReferenceItemsResult>;
+export declare const extractReferenceDisplayValues: (value: unknown, schema: SchemaConfig) => ReferenceDisplayValues;
+//# sourceMappingURL=referenceUtils.d.ts.map

package/dist/types/utils/schema/referenceUtils.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"referenceUtils.d.ts","sourceRoot":"","sources":["../../../../src/utils/schema/referenceUtils.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,MAAM,2CAA2C,CAAC;AACzE,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAG3C,MAAM,WAAW,aAAa;IAC5B,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,MAAM,WAAW,yBAAyB;IACxC,KAAK,EAAE,aAAa,EAAE,CAAC;IACvB,KAAK,EAAE,MAAM,CAAC;CACf;AAED,MAAM,WAAW,sBAAsB;IACrC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IACzB,KAAK,EAAE,MAAM,GAAG,SAAS,CAAC;CAC3B;AAED,eAAO,MAAM,mBAAmB,GAC9B,cAAc,MAAM,EACpB,OAAO,UAAU,CAAC,OAAO,YAAY,CAAC,CAAC,CAAC,CAAC,EACzC,QAAQ,YAAY,KACnB,OAAO,CAAC,yBAAyB,CAsBnC,CAAC;AAEF,eAAO,MAAM,6BAA6B,GACxC,OAAO,OAAO,EACd,QAAQ,YAAY,KACnB,sBAYF,CAAC"}

package/docs/GETTING_STARTED.md

@@ -1,33 +1,86 @@
 # Getting Started
 *Build your first dashboard page on Patterns using Cursor.*
 
-## Library Installations
-Run the following command to install the library and its peer dependencies:
+## Setup
+
+Follow these steps to set up Auto Patterns with Cursor AI assistance:
+
+### 1. Create `aicm.json` at Project Root
+
 ```bash
-yarn add @wix/auto-patterns @wix/patterns @wix/design-system react-router-dom
+echo '{ "presets": ["@wix/ai-rules/yoshi-flow-bm"] }' > aicm.json
 ```
 
-## MCP Installations
+### 2. Add Postinstall Script
 
-- [Install Business Schema MCP in Cursor](https://github.com/wix-private/mcp-servers/tree/master/packages/business-schema-mcp)
-  - [cursor://anysphere.cursor-deeplink/mcp/install?name=business-schema&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAd2l4L2J1c2luZXNzLXNjaGVtYS1tY3AiXX0%3D](cursor://anysphere.cursor-deeplink/mcp/install?name=business-schema&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAd2l4L2J1c2luZXNzLXNjaGVtYS1tY3AiXX0%3D)
-- [Install Auto Patterns MCP in Cursor](https://github.com/wix-private/mcp-servers/tree/master/packages/auto-patterns-mcp)
-  - [cursor://anysphere.cursor-deeplink/mcp/install?name=auto-patterns&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAd2l4L2F1dG8tcGF0dGVybnMtbWNwIl19](cursor://anysphere.cursor-deeplink/mcp/install?name=auto-patterns&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyJAd2l4L2F1dG8tcGF0dGVybnMtbWNwIl19)
+Add a `postinstall` script to your root `package.json`:
 
-> Deep links to Cursor for convenience. If they do not work, please copy and paste them into your browser or install the MCPs manually.
+```json
+{
+  "name": "your-project",
+  "scripts": {
+    "postinstall": "yarn dlx @wix/ai-rules"
+  }
+}
+```
+
+### 3. Update `.gitignore`
+
+Add the following to your `.gitignore`:
 
-## Working with Auto Patterns
-A typical usage of Auto Patterns is to render a `AutoPatternsApp` component with a configuration object. You don't need to do it manually, but generate it through Cursor's chat.
-You can write a prompt like this:
 ```
-I want a dashboard page for sessions, use wix.bookings.v1.sessions fqdn for that.
+.cursor/*/aicm
 ```
 
-Then Cursor will retrieve the schema for the `wix.bookings.v1.sessions` FQDN and create an Auto Patterns configuration with custom data source.
+### 4. Run Yarn Install
+
+```bash
+yarn install
+```
+
+This will automatically install rules, MCP tools, and commands in `.cursor/rules` and `.cursor/commands` for all packages.
+
+### What You Get
+
+After running `yarn install`, you will have:
 
-Then, you can run your app and see the results.
-According to the results, you can ask Cursor to improve the configuration.
-For example, you can ask Cursor to add specific filters, actions, or custom columns.
+- **MCP Tools** - Business Schema MCP and Auto Patterns MCP for Cursor
+- **Cursor Rules** - AI rules for auto-patterns development
+- **2 Commands** - `init-auto-patterns` and `extend-auto-patterns`
+
+## Working with Auto Patterns
+
+Auto Patterns provides two Cursor commands to help you build dashboard pages:
+
+### `init-auto-patterns`
+
+Creates a new auto-patterns app from scratch with FQDN-based custom data sources.
+
+This interactive workflow will:
+1. Check and install required dependencies
+2. Ask what collection you're managing (e.g., Contacts, Products)
+3. Discover the SDK package for your FQDN
+4. Extract schema and let you select fields
+5. Generate working code with full CRUD operations
+
+### `extend-auto-patterns`
+
+Adds features to an existing auto-patterns app.
+
+Available features:
+- Entity pages (edit/view modes)
+- Filters and search
+- Views and sorting
+- Custom actions and bulk actions
+- Column overrides and custom components
+- Delete actions
+- Table/Grid toggle
+- Slots
+- And much more
+
+Both commands guide you through an interactive configuration process, ensuring you get exactly what you need.
+
+While you can interact directly with the MCP tools using natural language, we strongly recommend using the provided commands for the best results.
 
 ## Handling Translations
 You should provide translated values everywhere you configure or render text content, just like you do in the rest of your app.
@@ -43,7 +96,7 @@ import { AppConfig, AutoPatternsApp } from '@wix/auto-patterns';
 import { useTranslation } from 'react-i18next';
 
 const MyPage = () => {
-  const { t } = useTranslation();
+  const { t, ready } = useTranslation();
 
   const config: AppConfig = {
     pages: [
@@ -95,6 +148,8 @@ const MyPage = () => {
     ],
   };
 
+  if (!ready) return null;
+
   return <AutoPatternsApp configuration={config} />;
 };
 

package/mcp-docs/app_config_structure.md

@@ -38,8 +38,7 @@
 
 ## Common Configuration Mistakes to Avoid
 
-- Adding more than two pages
-- Mixing page types in a single configuration
+- Mixing page types incorrectly in a single page configuration
 - Including undefined optional fields
 - Selecting too many initial columns
 - Not designating exactly one page as `appMainPage: true`
@@ -59,7 +58,7 @@
 export interface AppConfig {
   pages: {
     id: string; // Page unique identifier (must be unique across the app)
-    type: 'collectionPage' | 'entityPage'; // Defines page type
+    type: 'collectionPage' | 'entityPage' | 'settingsPage'; // Defines page type
     appMainPage?: boolean; // Designates this page as the main page (exactly one page must have this set to true)
     collectionPage?: {
       route: {
@@ -449,9 +448,73 @@ export interface AppConfig {
         id: string; // ID matching your custom data source identifier
       };
     };
+    settingsPage?: {
+      route: {
+        path: string; // Route path for the settings page (e.g., '/settings')
+      };
+      entityTypeSource: 'custom'; // Data source type - settings pages use custom data sources
+      custom: { // REQUIRED - matches the custom data source identifier
+        id: string; // ID matching your custom data source identifier (e.g., 'app-settings')
+      };
+      title?: {
+        text: string; // Page title text
+      };
+      subtitle?: {
+        text: string; // Subtitle text
+        learnMore?: {
+          url: string; // Learn more URL
+          label?: string; // Learn more link label
+        };
+      };
+      actions?: {
+        moreActions?: { // Custom actions for the settings page (export, import, reset, etc.)
+          id: string; // Action identifier matching a custom action resolver
+          type: 'custom'; // Action type
+          label: string; // Action label displayed in menu
+          biName: string; // MANDATORY: Business intelligence name for analytics tracking
+        }[];
+      };
+      layout?: {
+        main: CardLayout[]; // Main content cards
+        sidebar?: CardLayout[]; // Optional sidebar cards
+      };
+    };
   }[];
 }
 
+// Settings page and Entity page layout types
+type CardLayout = {
+  type: 'card';
+  card: {
+    title: { text: string }; // Card header title
+    subtitle?: { text: string }; // Optional card subtitle
+    children: LayoutContent[]; // Card content items (fields reference data source schema)
+  };
+};
+
+type LayoutContent =
+  | {
+      type: 'field';
+      field: {
+        span?: number; // Grid columns (1-12)
+        fieldId: string; // Field ID from the data source schema (custom data source or CMS)
+      };
+    }
+  | {
+      type: 'container';
+      container: {
+        span?: number; // Grid columns (1-12)
+        children: LayoutContent[]; // Nested layout items
+      };
+    }
+  | {
+      type: 'component';
+      component: {
+        span?: number; // Grid columns (1-12)
+        componentId: string; // ID mapping to a custom component override
+      };
+    };
+
 type ActionItem = {
   id: string; // Unique identifier for the action
   type: 'update' | 'delete' | 'custom'; // Action type

package/mcp-docs/auto-patterns-guide.md

@@ -116,8 +116,7 @@ It is configured using a TypeScript file conforming to the `AppConfig` interface
 
 ## Common Configuration Mistakes to Avoid
 
-- Adding more than two pages
-- Mixing page types in a single configuration
+- Mixing page types incorrectly in a single page configuration
 - Including undefined optional fields
 - Selecting too many initial columns
 - Not designating exactly one page as `appMainPage: true`
@@ -137,7 +136,7 @@ It is configured using a TypeScript file conforming to the `AppConfig` interface
 export interface AppConfig {
   pages: {
     id: string; // Page unique identifier (must be unique across the app)
-    type: 'collectionPage' | 'entityPage'; // Defines page type
+    type: 'collectionPage' | 'entityPage' | 'settingsPage'; // Defines page type
     appMainPage?: boolean; // Designates this page as the main page (exactly one page must have this set to true)
     collectionPage?: {
       route: {
@@ -527,9 +526,73 @@ export interface AppConfig {
         id: string; // ID matching your custom data source identifier
       };
     };
+    settingsPage?: {
+      route: {
+        path: string; // Route path for the settings page (e.g., '/settings')
+      };
+      entityTypeSource: 'custom'; // Data source type - settings pages use custom data sources
+      custom: { // REQUIRED - matches the custom data source identifier
+        id: string; // ID matching your custom data source identifier (e.g., 'app-settings')
+      };
+      title?: {
+        text: string; // Page title text
+      };
+      subtitle?: {
+        text: string; // Subtitle text
+        learnMore?: {
+          url: string; // Learn more URL
+          label?: string; // Learn more link label
+        };
+      };
+      actions?: {
+        moreActions?: { // Custom actions for the settings page (export, import, reset, etc.)
+          id: string; // Action identifier matching a custom action resolver
+          type: 'custom'; // Action type
+          label: string; // Action label displayed in menu
+          biName: string; // MANDATORY: Business intelligence name for analytics tracking
+        }[];
+      };
+      layout?: {
+        main: CardLayout[]; // Main content cards
+        sidebar?: CardLayout[]; // Optional sidebar cards
+      };
+    };
   }[];
 }
 
+// Settings page and Entity page layout types
+type CardLayout = {
+  type: 'card';
+  card: {
+    title: { text: string }; // Card header title
+    subtitle?: { text: string }; // Optional card subtitle
+    children: LayoutContent[]; // Card content items (fields reference data source schema)
+  };
+};
+
+type LayoutContent =
+  | {
+      type: 'field';
+      field: {
+        span?: number; // Grid columns (1-12)
+        fieldId: string; // Field ID from the data source schema (custom data source or CMS)
+      };
+    }
+  | {
+      type: 'container';
+      container: {
+        span?: number; // Grid columns (1-12)
+        children: LayoutContent[]; // Nested layout items
+      };
+    }
+  | {
+      type: 'component';
+      component: {
+        span?: number; // Grid columns (1-12)
+        componentId: string; // ID mapping to a custom component override
+      };
+    };
+
 type ActionItem = {
   id: string; // Unique identifier for the action
   type: 'update' | 'delete' | 'custom'; // Action type
@@ -714,13 +777,20 @@ Notice how the `label` is derived from the `value` by capitalizing the first let
 
 ## Critical Page Rules
 
-- **Pages array must contain exactly two pages** - one collectionPage and one entityPage
 - **Exactly one page must have `appMainPage: true`** to designate it as the main page
 - **All page IDs referenced in relationships must exist in the configuration** - validate all `parentPageId` and `entityPageId` references
 
-## Default Generation
+## Page Types
+
+AutoPatterns supports three page types:
 
-* **Always generate two pages**:
+1. **collectionPage** - Displays a collection of entities in table/grid view
+2. **entityPage** - Displays details for a single entity with edit/view modes
+3. **settingsPage** - Form-based page for managing application settings and preferences
+
+## Default Generation (Collection/Entity Pages)
+
+* **For collection-based apps, generate two pages**:
 
   * One **collectionPage** (routePath: `/`)
   * One **entityPage** (routePath: `/[segment]/:entityId`)
@@ -729,6 +799,16 @@ Notice how the `label` is derived from the `value` by capitalizing the first let
     * The route path **must** include a descriptive segment (e.g., `/product/:entityId`, `/pet/:entityId`)
     * **Never use just `/:entityId`** - this conflicts with the collection page route and breaks routing
 
+## Settings Page Generation
+
+* **For settings-based apps**, generate a **settingsPage** with:
+  * Route path (e.g., `/settings`)
+  * Custom data source with schema and CRUD actions (same pattern as collection pages)
+  * Layout with main and optional sidebar cards
+  * Optional more actions for additional operations (export, import, reset)
+
+See [Settings Page](./settings_page.md) for detailed configuration.
+
 ## Page Connection Configuration
 
 ### Main Page Designation

package/mcp-docs/index.md

@@ -62,6 +62,10 @@ This index maps user requests to the appropriate section IDs for fetching releva
 **Topics**: Entity page view mode actions, primaryActions, secondaryActions, collection-style actions
 **Keywords**: view mode actions, primaryActions, secondaryActions, read-only entity actions, entity page view operations, collection-style entity actions, navigation actions
 
+### ID: `settings_page`
+**Topics**: Settings page configuration, form-based settings interface, custom data source, card-based layout, application preferences
+**Keywords**: settings page, settingsPage, form settings, custom data source, settings layout, preferences, configuration page, more actions, settings fields, main sidebar layout, SchemaConfig, entityTypeSource custom
+
 ### ID: `resolved_action`
 **Topics**: ResolvedAction interface, common return type for custom actions, field documentation
 **Keywords**: ResolvedAction, action return type, custom action interface, action fields, label, icon, onClick, disabled, hidden, tooltip, skin

package/mcp-docs/pages_configuration.md

@@ -2,13 +2,20 @@
 
 ## Critical Page Rules
 
-- **Pages array must contain exactly two pages** - one collectionPage and one entityPage
 - **Exactly one page must have `appMainPage: true`** to designate it as the main page
 - **All page IDs referenced in relationships must exist in the configuration** - validate all `parentPageId` and `entityPageId` references
 
-## Default Generation
+## Page Types
 
-* **Always generate two pages**:
+AutoPatterns supports three page types:
+
+1. **collectionPage** - Displays a collection of entities in table/grid view
+2. **entityPage** - Displays details for a single entity with edit/view modes
+3. **settingsPage** - Form-based page for managing application settings and preferences
+
+## Default Generation (Collection/Entity Pages)
+
+* **For collection-based apps, generate two pages**:
 
   * One **collectionPage** (routePath: `/`)
   * One **entityPage** (routePath: `/[segment]/:entityId`)
@@ -17,6 +24,16 @@
     * The route path **must** include a descriptive segment (e.g., `/product/:entityId`, `/pet/:entityId`)
     * **Never use just `/:entityId`** - this conflicts with the collection page route and breaks routing
 
+## Settings Page Generation
+
+* **For settings-based apps**, generate a **settingsPage** with:
+  * Route path (e.g., `/settings`)
+  * Custom data source with schema and CRUD actions (same pattern as collection pages)
+  * Layout with main and optional sidebar cards
+  * Optional more actions for additional operations (export, import, reset)
+
+See [Settings Page](./settings_page.md) for detailed configuration.
+
 ## Page Connection Configuration
 
 ### Main Page Designation