What problem does it solve? Building OmniStudio FlexCards requires correctly configuring DataSourceConfig and PropertySetConfig JSON, binding Integration Procedure data sources, and meeting SLDS, accessibility, and performance standards—mistakes cause runtime data failures and broken card layouts. ## Core Features & Use Cases - FlexCard Authoring: Generate OmniUiCard definitions with layouts (single, list, tabbed, flyout), states, action buttons, and conditional visibility. - Data Source Binding: Configure Integration Procedure data sources with input mapping, merge field syntax, and multi-source coordination. - 130-Point Validation: Score cards across 7 categories (design, data binding, actions, styling, accessibility, testing, performance) with deploy/review/block thresholds. - Use Case: A Salesforce Industries developer needs an account summary card on a record page. The skill generates the OmniUiCard JSON bound to an active Integration Procedure, validates it against the scoring rubric, and produces a deployment checklist. ## Quick Start Ask the AI to create a FlexCard that displays account summary data from the Account_GetSummary Integration Procedure with a button launching an OmniScript.