@salesforce/afv-skills 1.22.0 → 1.24.0

package/skills/generating-apex-test/references/async-testing.md

@@ -1,193 +0,0 @@
-# Async Testing Patterns
-
-## Key Principle
-
-`Test.stopTest()` forces all async operations to execute synchronously, allowing assertions on their results.
-
-## Batch Apex Testing
-
-### Basic Batch Test
-
-**Critical:** In test context only one `execute()` invocation runs, so always set `batchSize >= testRecordCount` (e.g., `Database.executeBatch(batch, 200)` with 200 records). Never create more records than the batch size.
-
-```apex
-@isTest
-static void shouldProcessAllRecords_WhenBatchExecutes() {
-    List<Account> accounts = TestDataFactory.createAccounts(200, true);
-
-    Test.startTest();
-    MyBatchClass batch = new MyBatchClass();
-    Id batchId = Database.executeBatch(batch, 200);
-    Test.stopTest();
-
-    List<Account> updated = [SELECT Id, Status__c FROM Account];
-    for (Account acc : updated) {
-        Assert.areEqual('Processed', acc.Status__c,
-            'Batch should update all account statuses');
-    }
-}
-```
-
-### Batch with Failures
-
-```apex
-@isTest
-static void shouldLogErrors_WhenRecordsFail() {
-    List<Account> accounts = TestDataFactory.createAccounts(198, true);
-
-    List<Account> invalidAccounts = new List<Account>();
-    for (Integer i = 0; i < 2; i++) {
-        invalidAccounts.add(new Account(
-            Name = 'Invalid Account ' + i,
-            Invalid_Field__c = 'triggers_validation_error'
-        ));
-    }
-    insert invalidAccounts;
-
-    Test.startTest();
-    MyBatchClass batch = new MyBatchClass();
-    Database.executeBatch(batch, 200);
-    Test.stopTest();
-
-    List<Error_Log__c> errors = [SELECT Id, Message__c FROM Error_Log__c];
-    Assert.areEqual(2, errors.size(), 'Should log 2 failed records');
-}
-```
-
-### Batch Chaining
-
-Test `finish()` chaining in a **separate test method** — calling `Database.executeBatch()` inside `finish()` during a test can throw `UnexpectedException`. Verify the first batch independently, then test that `finish()` enqueues the next batch.
-
-## Queueable Testing
-
-### Basic Queueable Test
-
-```apex
-@isTest
-static void shouldCompleteProcessing_WhenQueueableEnqueued() {
-    Account acc = TestDataFactory.createAccount(true);
-
-    Test.startTest();
-    MyQueueableClass queueable = new MyQueueableClass(acc.Id);
-    System.enqueueJob(queueable);
-    Test.stopTest();
-
-    Account updated = [SELECT Id, Status__c FROM Account WHERE Id = :acc.Id];
-    Assert.areEqual('Processed', updated.Status__c,
-        'Queueable should update account status');
-}
-```
-
-### Queueable Chaining
-
-Only the **first** chained queueable executes in tests. Design tests to verify:
-1. First job completes correctly
-2. Chain is properly enqueued (query `AsyncApexJob`)
-3. Each job works independently in its own test method
-
-```apex
-@isTest
-static void shouldChainNextJob_WhenMoreRecordsExist() {
-    List<Account> accounts = TestDataFactory.createAccounts(500, true);
-
-    Test.startTest();
-    MyChainedQueueable queueable = new MyChainedQueueable(0, 100);
-    System.enqueueJob(queueable);
-    Test.stopTest();
-
-    List<Account> processed = [SELECT Id FROM Account WHERE Processed__c = true];
-    Assert.areEqual(100, processed.size(), 'First batch should process 100 records');
-
-    List<AsyncApexJob> jobs = [
-        SELECT Id, Status, JobType
-        FROM AsyncApexJob
-        WHERE ApexClass.Name = 'MyChainedQueueable'
-    ];
-    Assert.isTrue(jobs.size() >= 1, 'Chained job should be enqueued');
-}
-```
-
-### Queueable with Callouts
-
-Set the callout mock **before** `Test.startTest()`:
-
-```apex
-@isTest
-static void shouldMakeCallout_WhenQueueableWithCallout() {
-    Test.setMock(HttpCalloutMock.class, new MockHttpResponse(200, '{"status":"ok"}'));
-    Account acc = TestDataFactory.createAccount(true);
-
-    Test.startTest();
-    MyQueueableWithCallout queueable = new MyQueueableWithCallout(acc.Id);
-    System.enqueueJob(queueable);
-    Test.stopTest();
-
-    Account updated = [SELECT Id, External_Status__c FROM Account WHERE Id = :acc.Id];
-    Assert.areEqual('Synced', updated.External_Status__c,
-        'Should update status after successful callout');
-}
-```
-
-## Future Method Testing
-
-```apex
-@isTest
-static void shouldExecuteFutureMethod() {
-    Account acc = TestDataFactory.createAccount(true);
-
-    Test.startTest();
-    MyClass.processFuture(acc.Id);
-    Test.stopTest();
-
-    Account updated = [SELECT Id, Processed__c FROM Account WHERE Id = :acc.Id];
-    Assert.isTrue(updated.Processed__c, 'Future should process record');
-}
-```
-
-## Scheduled Apex Testing
-
-### Direct Execution
-
-```apex
-@isTest
-static void shouldExecuteScheduledJob() {
-    List<Account> accounts = TestDataFactory.createAccounts(50, true);
-
-    Test.startTest();
-    MyScheduledClass scheduled = new MyScheduledClass();
-    scheduled.execute(null);
-    Test.stopTest();
-
-    List<Account> processed = [SELECT Id FROM Account WHERE Processed__c = true];
-    Assert.areEqual(50, processed.size(), 'Scheduled job should process records');
-}
-```
-
-### CRON Registration
-
-```apex
-@isTest
-static void shouldScheduleJob() {
-    Test.startTest();
-    String cronExp = '0 0 6 * * ?';
-    String jobId = System.schedule('Daily Processing', cronExp, new MyScheduledClass());
-    Test.stopTest();
-
-    CronTrigger ct = [
-        SELECT Id, CronExpression, State
-        FROM CronTrigger
-        WHERE Id = :jobId
-    ];
-    Assert.areEqual('0 0 6 * * ?', ct.CronExpression, 'CRON should match');
-    Assert.areEqual('WAITING', ct.State, 'Job should be waiting');
-}
-```
-
-## Common Pitfalls
-
-| Pitfall | Impact |
-|---|---|
-| Missing `Test.stopTest()` | Async never executes, assertions fail silently |
-| Expecting all chained queueables to run | Only the first runs; test each independently |
-| Mock set after `Test.startTest()` | Callout mock must be set **before** `Test.startTest()` |
-| Batch size < record count in tests | Only `batchSize` records processed; set `batchSize >= recordCount` |

package/skills/generating-apex-test/references/mocking-patterns.md

@@ -1,220 +0,0 @@
-# Mocking Patterns
-
-## HTTP Callout Mocking
-
-Apex doesn't allow real HTTP callouts in tests. Use `HttpCalloutMock` interface.
-
-### Basic Mock
-
-```apex
-@isTest
-public class MockHttpResponse implements HttpCalloutMock {
-    
-    private Integer statusCode;
-    private String body;
-    
-    public MockHttpResponse(Integer statusCode, String body) {
-        this.statusCode = statusCode;
-        this.body = body;
-    }
-    
-    public HTTPResponse respond(HTTPRequest req) {
-        HttpResponse res = new HttpResponse();
-        res.setStatusCode(statusCode);
-        res.setBody(body);
-        res.setHeader('Content-Type', 'application/json');
-        return res;
-    }
-}
-```
-
-### Using the Mock
-
-```apex
-@isTest
-static void shouldProcessApiResponse_WhenCalloutSucceeds() {
-    String mockResponse = '{"status": "success", "data": [{"id": "123"}]}';
-    Test.setMock(HttpCalloutMock.class, new MockHttpResponse(200, mockResponse));
-
-    Test.startTest();
-    List<ExternalRecord> results = MyIntegrationService.fetchRecords();
-    Test.stopTest();
-
-    Assert.areEqual(1, results.size(), 'Should parse one record from response');
-    Assert.areEqual('123', results[0].externalId, 'Should extract correct ID');
-}
-
-@isTest
-static void shouldHandleError_WhenCalloutFails() {
-    String errorResponse = '{"error": "Unauthorized"}';
-    Test.setMock(HttpCalloutMock.class, new MockHttpResponse(401, errorResponse));
-
-    Test.startTest();
-    CalloutResult result = MyIntegrationService.fetchRecords();
-    Test.stopTest();
-
-    Assert.areEqual(false, result.isSuccess, 'Should indicate failure');
-    Assert.isTrue(result.errorMessage.contains('Unauthorized'), 'Should capture error');
-}
-```
-
-### Multi-Request Mock
-
-For services making multiple callouts:
-
-```apex
-@isTest
-public class MultiRequestMock implements HttpCalloutMock {
-
-    private Map<String, HttpResponse> endpointResponses;
-
-    public MultiRequestMock(Map<String, HttpResponse> responses) {
-        this.endpointResponses = responses;
-    }
-
-    public HTTPResponse respond(HTTPRequest req) {
-        String endpoint = req.getEndpoint();
-        for (String key : endpointResponses.keySet()) {
-            if (endpoint.contains(key)) {
-                return endpointResponses.get(key);
-            }
-        }
-        HttpResponse res = new HttpResponse();
-        res.setStatusCode(404);
-        res.setBody('{"error": "Not found"}');
-        return res;
-    }
-}
-```
-
-### StaticResourceCalloutMock
-
-Use when response JSON is large or complex:
-
-```apex
-@isTest
-static void shouldParseComplexResponse() {
-    StaticResourceCalloutMock mock = new StaticResourceCalloutMock();
-    mock.setStaticResource('TestApiResponse');
-    mock.setStatusCode(200);
-    mock.setHeader('Content-Type', 'application/json');
-    Test.setMock(HttpCalloutMock.class, mock);
-
-    Test.startTest();
-    Result r = MyService.callExternalApi();
-    Test.stopTest();
-
-    Assert.isNotNull(r, 'Should parse response');
-}
-```
-
-## SOSL Mocking
-
-SOSL returns empty results in tests by default. Call `Test.setFixedSearchResults(List<Id>)` before the search:
-
-```apex
-@isTest
-static void shouldReturnSearchResults() {
-    Account acc = TestDataFactory.createAccount(true);
-    Test.setFixedSearchResults(new List<Id>{ acc.Id });
-
-    Test.startTest();
-    List<Account> results = MyService.searchAccounts('Test');
-    Test.stopTest();
-
-    Assert.areEqual(1, results.size(), 'Should return mocked search result');
-}
-```
-
-## DML Mocking (Constructor Injection)
-
-Design for testability — use a public constructor for production and a `@TestVisible private` constructor that accepts mock interfaces:
-
-```apex
-public class MyService {
-    private IDML dmlHandler;
-
-    public MyService() {
-        this.dmlHandler = new DMLHandler();
-    }
-
-    @TestVisible
-    private MyService(IDML dmlHandler) {
-        this.dmlHandler = dmlHandler;
-    }
-
-    public void createRecords(List<Account> accounts) {
-        dmlHandler.doInsert(accounts);
-    }
-}
-```
-
-## Stub API (System.StubProvider)
-
-For mocking Apex class dependencies:
-
-```apex
-@isTest
-public class MyServiceMock implements System.StubProvider {
-
-    public Object handleMethodCall(
-        Object stubbedObject, String stubbedMethodName, Type returnType,
-        List<Type> paramTypes, List<String> paramNames, List<Object> args
-    ) {
-        if (stubbedMethodName == 'getAccountData') {
-            return new AccountData('Mock Account', 'Active');
-        }
-        return null;
-    }
-}
-
-@isTest
-static void shouldUseAccountData() {
-    MyServiceMock mockProvider = new MyServiceMock();
-    IMyService mockService = (IMyService) Test.createStub(IMyService.class, mockProvider);
-
-    MyController controller = new MyController(mockService);
-
-    Test.startTest();
-    String result = controller.displayAccountInfo();
-    Test.stopTest();
-
-    Assert.isTrue(result.contains('Mock Account'), 'Should use mocked data');
-}
-```
-
-## Email Testing
-
-Apex doesn't actually send emails in tests. Use limits to verify:
-
-```apex
-@isTest
-static void shouldSendEmail_WhenTriggered() {
-    Integer emailsBefore = Limits.getEmailInvocations();
-
-    Test.startTest();
-    MyService.sendNotification(testContact);
-    Test.stopTest();
-
-    Assert.areEqual(emailsBefore + 1, Limits.getEmailInvocations(),
-        'One email should be sent');
-}
-```
-
-## Platform Event Testing
-
-```apex
-@isTest
-static void shouldPublishEvent_WhenRecordCreated() {
-    Test.startTest();
-    Test.enableChangeDataCapture();
-
-    Account acc = TestDataFactory.createAccount(true);
-    Test.getEventBus().deliver();
-    Test.stopTest();
-    
-    // Query platform event trigger results
-    List<EventLog__c> logs = [SELECT Id FROM EventLog__c WHERE AccountId__c = :acc.Id];
-    Assert.areEqual(1, logs.size(), 'Event handler should create log record');
-}
-```

package/skills/generating-apex-test/references/test-data-factory.md

@@ -1,75 +0,0 @@
-# TestDataFactory Patterns
-
-For the base class template, see [assets/test-data-factory-template.cls](../assets/test-data-factory-template.cls).
-
-## Design Rules
-
-1. **Always accept a `doInsert` flag** — lets callers modify records before insert
-2. **Append loop index to all fields that participate in matching rules** — prevents `DUPLICATES_DETECTED` errors from active Duplicate Rules
-3. **Single-record methods delegate to bulk** — e.g., `createAccount(doInsert)` calls `createAccounts(1, doInsert)[0]`
-4. **Return created records** — enables chaining and further manipulation
-5. **Set all required fields** — include fields enforced by validation rules, not just schema-required fields
-
-## Field Override Pattern
-
-Allow callers to override default values without creating new factory methods:
-
-```apex
-public static Account createAccount(Map<String, Object> fieldOverrides, Boolean doInsert) {
-    Account acc = new Account(
-        Name = 'Test Account',
-        Industry = 'Technology'
-    );
-    for (String fieldName : fieldOverrides.keySet()) {
-        acc.put(fieldName, fieldOverrides.get(fieldName));
-    }
-    if (doInsert) insert acc;
-    return acc;
-}
-
-// Usage:
-Account acc = TestDataFactory.createAccount(new Map<String, Object>{
-    'Name' => 'Custom Name',
-    'Industry' => 'Healthcare'
-}, true);
-```
-
-## Record Type Support
-
-```apex
-public static Account createAccountByRecordType(String recordTypeName, Boolean doInsert) {
-    Id recordTypeId = Schema.SObjectType.Account
-        .getRecordTypeInfosByDeveloperName()
-        .get(recordTypeName)
-        .getRecordTypeId();
-
-    Account acc = new Account(
-        Name = 'Test Account',
-        RecordTypeId = recordTypeId
-    );
-    if (doInsert) insert acc;
-    return acc;
-}
-```
-
-## Handling Duplicate Rules
-
-When unique field values alone are not sufficient, use `Database.insert()` with a `DuplicateRuleHeader`:
-
-```apex
-public static List<Account> createAccountsAllowDuplicates(Integer count, Boolean doInsert) {
-    List<Account> accounts = new List<Account>();
-    for (Integer i = 0; i < count; i++) {
-        accounts.add(new Account(
-            Name = 'Test Account ' + i,
-            Phone = '555-000-' + String.valueOf(i).leftPad(4, '0')
-        ));
-    }
-    if (doInsert) {
-        Database.DMLOptions dml = new Database.DMLOptions();
-        dml.DuplicateRuleHeader.allowSave = true;
-        Database.insert(accounts, dml);
-    }
-    return accounts;
-}
-```

package/skills/generating-custom-application/SKILL.md

@@ -1,211 +0,0 @@
----
-name: generating-custom-application
-description: "Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use generating-ui-bundle-custom-app for that case."
-metadata:
-  version: "1.0"
----
-
-## When to Use This Skill
-
-Use this skill when you need to:
-- Create Lightning applications
-- Organize tabs and features into focused apps
-- Configure application navigation and branding
-- Set up custom page layouts for objects
-- Troubleshoot deployment errors related to custom applications
-# CustomApplication (Lightning App) Metadata Specification
-
-## Overview
-
-Custom applications (Lightning Apps) that group tabs and functionality to provide a focused user experience for specific business processes. Always configured for Lightning Experience.
-
-## 🎯 Purpose
-- Organize related functionality into focused applications
-- Group tabs and components for specific user roles
-- Provide tailored user experiences
-- Control access to specific features and data
-- Use Standard navigation for general business applications or Console navigation for specialized service/support workflows requiring multi-tab workspaces
-- Create professional, branded application identity with custom colors and branding
-- Override standard actions with custom Lightning pages for enhanced user experience
-- Enable profile-specific experiences through profile action overrides
-
-## ⚙️ Required Properties
-
-### Core Application Properties
-- **fullName**: API name of the application
-- **label**: Display name of the application
-- **uiType**: Always "Lightning" for modern apps
-- **navType**: CRITICAL - Choose based on user requirements and workflow patterns
-    - "Standard": DEFAULT for general business applications (e.g., sales, marketing, operations)
-    - "Console": ONLY when workflow requires managing multiple records simultaneously with split-view or multi-tab workspace (e.g., customer service, call centers, support operations)
-- **formFactors**: Array of form factors (["LARGE"] for desktop, ["SMALL"] for mobile, or both)
-
-### Optional Properties
-- **description**: Brief description of the application's purpose
-- **tabs**: Array of tab names to include
-- **utilityBar**: API name of the Utility Bar configuration
-- **brand**: ⚠️ HIGHLY RECOMMENDED - Branding configuration object (headerColor, shouldOverrideOrgTheme, footerColor)
-- **actionOverrides**: ⚠️ REQUIRED when custom record pages exist - Action override configuration (actionName, content, formFactor, type, pageOrSobjectType)
-- **profileActionOverrides**: Profile-specific action overrides (actionName, content, formFactor, pageOrSobjectType, type, profile)
-- **isNavAutoTempTabsDisabled**: Navigation behavior setting (default: false)
-- **isNavPersonalizationDisabled**: Personalization setting (default: false)
-- **isNavTabPersistenceDisabled**: Tab persistence setting (default: false)
-
-## 🔧 Application Configuration
-
-### Navigation Type Selection (CRITICAL)
-**Decision Criteria for navType:**
-
-**Choose "Standard" (DEFAULT) for:**
-- General business applications and most workflows
-- Single-record focus or linear navigation patterns
-- Standard tab-based navigation is sufficient
-
-**Choose "Console" ONLY when workflow requires:**
-- Managing multiple related records simultaneously in split-view
-- Multi-tab workspace for handling complex, interconnected data
-- Contextual information from multiple sources visible at once
-- Examples: customer service operations, support desks, call centers
-
-**When in doubt:** Default to "Standard" for most general business use cases
-
-### Navigation Settings
-- **isNavAutoTempTabsDisabled**: Controls automatic temporary tab creation
-- **isNavPersonalizationDisabled**: Controls user personalization features
-- **isNavTabPersistenceDisabled**: Controls tab persistence across sessions
-
-### Tab Management
-- **tabs**: Array of tab names to include in the application
-- **formFactors**: Device-specific configurations (Large for desktop, Small for mobile)
-
-### Utility Bar
-- **utilityBar**: Reference to Lightning utility bar (appears at bottom of Lightning Experience)
-
-### Branding (HIGHLY RECOMMENDED - DO NOT SKIP)
-**IMPORTANT**: Provide branding configuration to create a professional, visually distinct application identity.
-
-- **brand.headerColor**: Header bar color in hex format (e.g., "#0070D2") - RECOMMENDED
-- **brand.shouldOverrideOrgTheme**: Override organization theme (true/false) - Default: false
-- **brand.footerColor**: Footer color in hex format
-
-### Action Overrides (CRITICAL - DO NOT SKIP)
-**IMPORTANT**: Action overrides MUST be created for every custom object tab that has a record page generated by flexipage expert.
-
-- **actionOverrides.actionName**: Action to override ("View" or "Tab")
-- **actionOverrides.content**: Page/component name (FlexiPage, Visualforce, Lightning component)
-    - For "View" action: Reference record pages generated by flexipage expert
-    - For "Tab" action: Reference home/app pages generated by flexipage expert
-- **actionOverrides.formFactor**: Device type ("Large" or "Small")
-- **actionOverrides.type**: Override type ("Default", "Visualforce", "Flexipage", "LightningComponent", "Scontrol")
-    - Recommended: Use "Flexipage" for Lightning record/home pages generated by flexipage expert
-- **actionOverrides.pageOrSobjectType**: Object API name the override applies to
-- **actionOverrides.comment**: Optional description (max 1000 characters)
-    - Auto-generated comment: "Action override created by Lightning App Builder during activation."
-- **actionOverrides.skipRecordTypeSelect**: Skip record type selection (default: false)
-
-### Profile Action Overrides
-- **profileActionOverrides.actionName**: Action to override ("View" or "Tab")
-- **profileActionOverrides.content**: Page/component name
-    - For "View" action: Reference profile-specific record pages generated by flexipage expert
-    - For "Tab" action: Reference profile-specific home pages generated by flexipage expert
-    - Can reference same or different FlexiPages than actionOverrides for profile-specific experiences
-- **profileActionOverrides.formFactor**: Device type ("Large" or "Small")
-- **profileActionOverrides.pageOrSobjectType**: Object API name
-- **profileActionOverrides.type**: Override type
-    - Recommended: Use "Flexipage" for Lightning pages generated by flexipage expert
-- **profileActionOverrides.profile**: Profile API name (e.g., "Admin", "Standard User")
-    - Enables different page layouts for different user profiles
-
-## 📱 Device Support
-
-### Desktop Configuration
-- **formFactor**: "Large"
-- **tabs**: Full list of application tabs
-
-### Phone Configuration
-- **formFactor**: "Small"
-- **tabs**: Mobile-optimized tab selection
-
-### Tablet Configuration
-- **formFactor**: "Medium"
-- **tabs**: Tablet-appropriate tab selection
-
-## 🎨 User Experience Features
-
-### Navigation Behavior
-- **Auto Temporary Tabs**: Can be enabled/disabled
-- **Personalization**: User customization options
-- **Tab Persistence**: Remember user's tab selections
-
-### Accessibility
-- **Keyboard Navigation**: Full keyboard support
-- **Screen Reader**: Compatible with assistive technologies
-- **High Contrast**: Support for high contrast modes
-
-## 🔗 Integration Points
-- **Custom Tabs**: Include custom object and web tabs
-- **Standard Tabs**: Include standard Salesforce tabs
-- **Lightning Pages**: Integrate with Lightning page layouts
-- **Components**: Include custom Lightning components
-## ✅ Best Practices
-- **Always use Lightning UI**: Set `uiType` to "Lightning" for modern apps
-- **Choose appropriate navigation**: CRITICAL - Analyze requirements carefully for `navType` selection
-    - Use "Standard" (DEFAULT) for general business applications
-    - Use "Console" ONLY when workflow requires multi-tab workspace, split-view, or managing multiple related records simultaneously
-    - Examples for Console: customer service, call centers, support operations
-    - Default to "Standard" for most general business use cases
-- **Include Standard Tabs**: Add common Salesforce tabs (Home, Accounts, Contacts, etc.)
-- **Use clear, descriptive application names**
-- **Group related functionality logically**
-- **Consider different user roles and needs**
-- **Test across different device types**
-- **Ensure proper permissions and access control**
-- **Provide meaningful descriptions for users**
-- **Follow consistent naming conventions**
-- **Always configure branding**: Set headerColor to create professional application identity
-- **Use accessible brand colors**: Ensure hex colors have sufficient contrast (WCAG AA compliant)
-- **Configure utility bars**: Add useful quick-access tools for users
-- **Leverage action overrides**: Customize page layouts for specific objects using FlexiPages from flexipage expert
-- **Use profile overrides**: Provide role-specific experiences by referencing different flexipage expert generated pages per profile
-
-## 🎯 Enhancement Rules
-- **uiType**: Always set to "Lightning" for modern app experience
-- **navType**: CRITICAL DECISION - Analyze user requirements carefully
-    - Set to "Standard" (DEFAULT) for general business applications
-    - Set to "Console" ONLY when workflow requires:
-        - Managing multiple related records simultaneously with split-view capability
-        - Multi-tab workspace for handling complex, interconnected data
-        - Contextual information from multiple sources visible at once
-    - Console examples: customer service operations, call centers, support desks
-    - When in doubt between Standard and Console, choose "Standard" for most business use cases
-- **formFactors**: Always set to ["LARGE"] for desktop Lightning Experience
-- **Standard Tabs**: Automatically add Home, Accounts, Contacts, Opportunities, Leads, Cases
-- **Navigation Settings**: Set all navigation flags to false for best user experience
-- **Branding**: ALWAYS include brand configuration for professional application identity
-    - MANDATORY: Set brand.headerColor to appropriate color (e.g., "#0070D2" for Salesforce Blue)
-    - Set brand.shouldOverrideOrgTheme based on requirements
-- **Action Overrides**: ALWAYS create action overrides when custom record pages exist
-    - MANDATORY: Add actionOverrides for "View" action pointing to flexipage expert generated record pages
-    - Use "Flexipage" type and reference the exact FlexiPage name
-    - Set formFactor to "Large" for desktop
-    - Include pageOrSobjectType with the object API name
-- **Profile Action Overrides**: Reference flexipage expert generated pages for role-based customization
-- **Form Factors**: Use "Large" for desktop, "Small" for mobile in overrides
-
-## ⚠️ CRITICAL Verification Checklist (MUST VERIFY)
-- [ ] All tabs are included in the application
-- [ ] **navType IS CORRECTLY SET** - Verify Console vs Standard selection
-- [ ] Default to "Standard" for most general business applications
-- [ ] Set to "Console" ONLY if workflow requires managing multiple records simultaneously, split-view, or multi-tab workspace
-- [ ] If requirements are general/ambiguous → navType should be "Standard"
-- [ ] **BRANDING IS CONFIGURED** - This is HIGHLY RECOMMENDED for professional applications
-- [ ] brand.headerColor is set with valid hex color (e.g., "#0070D2")
-- [ ] brand.shouldOverrideOrgTheme is set (default: false)
-- [ ] **ACTION OVERRIDES ARE CREATED** - This is MANDATORY for every custom object with a record page
-- [ ] Action overrides are defined for EACH custom object tab pointing to the correct record page
-- [ ] actionOverrides.content matches the exact FlexiPage name generated by flexipage expert
-- [ ] actionOverrides.pageOrSobjectType is set to the correct object API name
-- [ ] actionOverrides.type is set to "Flexipage"
-- [ ] actionOverrides.actionName is set to "View"
-- [ ] actionOverrides.formFactor is set to "Large"
-- [ ] All required fields are populated (fullName, label, uiType, navType, formFactors)