@salesforce/afv-skills 1.26.0 → 1.28.0

package/skills/experience-lwc-generate/references/template-anti-patterns.md

@@ -26,7 +26,7 @@ This guide documents systematic errors in Lightning Web Component templates, wit
 
 **Critical Rule**: LWC templates do NOT support JavaScript expressions. Only property references are allowed.
 
-### ❌ BAD: Arithmetic in Template
+### BAD: Arithmetic in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -37,7 +37,7 @@ This guide documents systematic errors in Lightning Web Component templates, wit
 </template>
 ```
 
-### ✅ GOOD: Use Getters
+### GOOD: Use Getters
 
 ```javascript
 // component.js
@@ -69,7 +69,7 @@ export default class PriceCalculator extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: String Concatenation in Template
+### BAD: String Concatenation in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -79,7 +79,7 @@ export default class PriceCalculator extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Computed Properties
+### GOOD: Computed Properties
 
 ```javascript
 // component.js
@@ -112,7 +112,7 @@ export default class Greeting extends LightningElement {
 
 **Critical Rule**: Ternary operators (`condition ? a : b`) are NOT allowed in LWC templates.
 
-### ❌ BAD: Ternary in Template
+### BAD: Ternary in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -123,7 +123,7 @@ export default class Greeting extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use Getters for Conditional Values
+### GOOD: Use Getters for Conditional Values
 
 ```javascript
 // component.js
@@ -155,7 +155,7 @@ export default class StatusDisplay extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use if:true/if:false for Conditional Rendering
+### GOOD: Use if:true/if:false for Conditional Rendering
 
 ```html
 <!-- component.html -->
@@ -189,7 +189,7 @@ get hasCount() {
 
 **Critical Rule**: Object literals (`{}`) cannot be passed directly as attribute values.
 
-### ❌ BAD: Inline Object Literals
+### BAD: Inline Object Literals
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -206,7 +206,7 @@ get hasCount() {
 </template>
 ```
 
-### ✅ GOOD: Define Objects in JavaScript
+### GOOD: Define Objects in JavaScript
 
 ```javascript
 // component.js
@@ -237,7 +237,7 @@ export default class ParentComponent extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: Inline Array Literals
+### BAD: Inline Array Literals
 
 ```html
 <!-- DOES NOT WORK -->
@@ -246,7 +246,7 @@ export default class ParentComponent extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Define Arrays in JavaScript
+### GOOD: Define Arrays in JavaScript
 
 ```javascript
 // component.js
@@ -272,7 +272,7 @@ export default class ColorPicker extends LightningElement {
 
 **Critical Rule**: No method calls, comparisons, or logical operators in templates.
 
-### ❌ BAD: Method Calls in Template
+### BAD: Method Calls in Template
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -284,7 +284,7 @@ export default class ColorPicker extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Use Getters for Transformations
+### GOOD: Use Getters for Transformations
 
 ```javascript
 // component.js
@@ -322,7 +322,7 @@ export default class DataDisplay extends LightningElement {
 </template>
 ```
 
-### ❌ BAD: Comparisons in Template
+### BAD: Comparisons in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -337,7 +337,7 @@ export default class DataDisplay extends LightningElement {
 </template>
 ```
 
-### ✅ GOOD: Getter-Based Comparisons
+### GOOD: Getter-Based Comparisons
 
 ```javascript
 // component.js
@@ -363,7 +363,7 @@ get isActive() {
 </template>
 ```
 
-### ❌ BAD: Logical Operators in Template
+### BAD: Logical Operators in Template
 
 ```html
 <!-- DOES NOT WORK -->
@@ -378,7 +378,7 @@ get isActive() {
 </template>
 ```
 
-### ✅ GOOD: Computed Boolean Properties
+### GOOD: Computed Boolean Properties
 
 ```javascript
 // component.js
@@ -408,7 +408,7 @@ get isNotLoading() {
 
 ## 5. Event Handler Mistakes
 
-### ❌ BAD: Inline Event Handlers with Arguments
+### BAD: Inline Event Handlers with Arguments
 
 ```html
 <!-- LLM generates this - DOES NOT WORK -->
@@ -419,7 +419,7 @@ get isNotLoading() {
 </template>
 ```
 
-### ✅ GOOD: Handler Functions with Data Attributes
+### GOOD: Handler Functions with Data Attributes
 
 ```html
 <!-- component.html -->
@@ -449,7 +449,7 @@ handleChange(event) {
 }
 ```
 
-### ❌ BAD: Event Binding with bind()
+### BAD: Event Binding with bind()
 
 ```html
 <!-- DOES NOT WORK -->
@@ -458,7 +458,7 @@ handleChange(event) {
 </template>
 ```
 
-### ✅ GOOD: Use Data Attributes for Context
+### GOOD: Use Data Attributes for Context
 
 ```html
 <!-- component.html -->
@@ -491,7 +491,7 @@ handleItemClick(event) {
 
 ## 6. Iteration Anti-Patterns
 
-### ❌ BAD: Missing Key in Iteration
+### BAD: Missing Key in Iteration
 
 ```html
 <!-- LLM forgets key - causes rendering issues -->
@@ -502,7 +502,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ✅ GOOD: Always Include Key
+### GOOD: Always Include Key
 
 ```html
 <!-- component.html -->
@@ -513,7 +513,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ❌ BAD: Using Index as Key
+### BAD: Using Index as Key
 
 ```html
 <!-- Anti-pattern: index can cause issues with reordering -->
@@ -524,7 +524,7 @@ handleItemClick(event) {
 </template>
 ```
 
-### ✅ GOOD: Use Unique Identifier as Key
+### GOOD: Use Unique Identifier as Key
 
 ```javascript
 // If items don't have unique IDs, generate them
@@ -545,7 +545,7 @@ connectedCallback() {
 </template>
 ```
 
-### ❌ BAD: Nested Iteration Without Proper Keys
+### BAD: Nested Iteration Without Proper Keys
 
 ```html
 <!-- PROBLEMATIC -->
@@ -562,7 +562,7 @@ connectedCallback() {
 </template>
 ```
 
-### ✅ GOOD: Compound Keys for Nested Iteration
+### GOOD: Compound Keys for Nested Iteration
 
 ```javascript
 // component.js
@@ -595,7 +595,7 @@ get processedCategories() {
 
 ## 7. Conditional Rendering Issues
 
-### ❌ BAD: if:true on Non-Boolean Values
+### BAD: if:true on Non-Boolean Values
 
 ```html
 <!-- LLM assumes truthy/falsy works like JS - it doesn't always -->
@@ -612,7 +612,7 @@ get processedCategories() {
 </template>
 ```
 
-### ✅ GOOD: Explicit Boolean Conversion
+### GOOD: Explicit Boolean Conversion
 
 ```javascript
 // component.js
@@ -638,7 +638,7 @@ get hasCount() {
 </template>
 ```
 
-### ❌ BAD: Multiple Conditions Without Else
+### BAD: Multiple Conditions Without Else
 
 ```html
 <!-- Verbose and error-prone -->
@@ -655,7 +655,7 @@ get hasCount() {
 </template>
 ```
 
-### ✅ GOOD: Use a State Getter
+### GOOD: Use a State Getter
 
 ```javascript
 // component.js
@@ -694,7 +694,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 
 ## 8. Slot and Composition Errors
 
-### ❌ BAD: Named Slot with Wrong Syntax
+### BAD: Named Slot with Wrong Syntax
 
 ```html
 <!-- LLM uses Vue/React slot syntax -->
@@ -711,7 +711,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 </template>
 ```
 
-### ✅ GOOD: LWC Slot Syntax
+### GOOD: LWC Slot Syntax
 
 ```html
 <!-- Parent component using slots -->
@@ -746,7 +746,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 
 ## 9. Data Binding Mistakes
 
-### ❌ BAD: Two-Way Binding Syntax
+### BAD: Two-Way Binding Syntax
 
 ```html
 <!-- LLM uses Angular/Vue two-way binding - doesn't exist in LWC -->
@@ -757,7 +757,7 @@ get isEmptyState() { return this.viewState === 'empty'; }
 </template>
 ```
 
-### ✅ GOOD: One-Way Binding with Event Handler
+### GOOD: One-Way Binding with Event Handler
 
 ```html
 <!-- component.html -->
@@ -790,7 +790,7 @@ handleInputChange(event) {
 }
 ```
 
-### ❌ BAD: Direct Property Mutation in Template
+### BAD: Direct Property Mutation in Template
 
 ```html
 <!-- Cannot mutate in template -->
@@ -799,7 +799,7 @@ handleInputChange(event) {
 </template>
 ```
 
-### ✅ GOOD: Mutate in Handler
+### GOOD: Mutate in Handler
 
 ```javascript
 // component.js
@@ -821,7 +821,7 @@ handleIncrement() {
 
 ## 10. Style and Class Binding
 
-### ❌ BAD: Dynamic Styles in Template
+### BAD: Dynamic Styles in Template
 
 ```html
 <!-- LLM uses React/Vue style binding - doesn't work in LWC -->
@@ -836,7 +836,7 @@ handleIncrement() {
 </template>
 ```
 
-### ✅ GOOD: CSS Custom Properties (Recommended)
+### GOOD: CSS Custom Properties (Recommended)
 
 ```javascript
 // component.js
@@ -864,7 +864,7 @@ renderedCallback() {
 </template>
 ```
 
-### ✅ GOOD: Computed Style String (When Necessary)
+### GOOD: Computed Style String (When Necessary)
 
 ```javascript
 // component.js
@@ -880,7 +880,7 @@ get dynamicStyle() {
 </template>
 ```
 
-### ❌ BAD: Dynamic Class with Expression
+### BAD: Dynamic Class with Expression
 
 ```html
 <!-- DOES NOT WORK -->
@@ -890,7 +890,7 @@ get dynamicStyle() {
 </template>
 ```
 
-### ✅ GOOD: Computed Class String
+### GOOD: Computed Class String
 
 ```javascript
 // component.js

package/skills/experience-ui-bundle-agentforce-client-generate/references/constraints.md

@@ -65,19 +65,19 @@ When updating an existing component:
 
 ## Examples
 
-### ❌ Wrong - Using containerStyle
+### Wrong - Using containerStyle
 
 ```tsx
 <AgentforceConversationClient agentId="0Xx..." containerStyle={{ width: 420, height: 600 }} />
 ```
 
-### ✅ Correct - Using width/height directly
+### Correct - Using width/height directly
 
 ```tsx
 <AgentforceConversationClient agentId="0Xx..." width="420px" height="600px" />
 ```
 
-### ❌ Wrong - Creating CSS file
+### Wrong - Creating CSS file
 
 ```css
 /* agent-styles.css */
@@ -93,7 +93,7 @@ import "./agent-styles.css";
 <AgentforceConversationClient className="agentforce-chat" />;
 ```
 
-### ✅ Correct - Using styleTokens
+### Correct - Using styleTokens
 
 ```tsx
 <AgentforceConversationClient
@@ -105,7 +105,7 @@ import "./agent-styles.css";
 />
 ```
 
-### ❌ Wrong - Creating style tag
+### Wrong - Creating style tag
 
 ```tsx
 <>
@@ -114,7 +114,7 @@ import "./agent-styles.css";
 </>
 ```
 
-### ✅ Correct - Using styleTokens
+### Correct - Using styleTokens
 
 ```tsx
 <AgentforceConversationClient
@@ -125,10 +125,10 @@ import "./agent-styles.css";
 />
 ```
 
-### ❌ Wrong - Editing implementation file
+### Wrong - Editing implementation file
 
 Reading or editing: `node_modules/@salesforce/ui-bundle-template-feature-react-agentforce-conversation-client/src/AgentforceConversationClient.tsx`
 
-### ✅ Correct - Editing usage file
+### Correct - Editing usage file
 
 Reading and editing: usage files where the component is imported and used (for example, `src/app.tsx`, a route component, or a feature page)

package/skills/experience-ui-bundle-custom-app-generate/SKILL.md

@@ -55,10 +55,10 @@ Use the default template in the doc below. Values in `{braces}` are resolved pro
 
 | Metadata Type | Template Reference |
 |--------------|-------------------|
-| CustomApplication | [configure-metadata-custom-application.md](docs/configure-metadata-custom-application.md) |
+| CustomApplication | [configure-metadata-custom-application.md](references/configure-metadata-custom-application.md) |
 
 ### Execution Note for Step 4: Load and use the doc
-- Agents MUST read the full contents of the docs/*.md file referenced in Step 4 before attempting to populate metadata fields.
+- Agents MUST read the full contents of the references/*.md file referenced in Step 4 before attempting to populate metadata fields.
 - Read the file in full, replace placeholders (e.g. `{appName}`) with the resolved values, then use the expanded template to populate the metadata XML content.
 - If Step 2 determined the older field names apply, substitute `<uiBundle>` with `<webApplication>` in the generated output.
 

package/skills/experience-ui-bundle-frontend-generate/SKILL.md

@@ -13,9 +13,9 @@ Determine which category the request falls into:
 
 | Category | Examples | Implementation Guide |
 |----------|----------|---------------------|
-| **Page** | New routed page (contacts, dashboard, settings) | `implementation/page.md` |
-| **Header / Footer** | Site-wide nav bar, footer, branding | `implementation/header-footer.md` |
-| **Component** | Widget, card, table, form, dialog | `implementation/component.md` |
+| **Page** | New routed page (contacts, dashboard, settings) | `references/page.md` |
+| **Header / Footer** | Site-wide nav bar, footer, branding | `references/header-footer.md` |
+| **Component** | Widget, card, table, form, dialog | `references/component.md` |
 
 ---
 

package/skills/experience-ui-bundle-metadata-generate/SKILL.md

@@ -149,5 +149,5 @@ Whenever the app references a new external domain: CDN images, external fonts, t
 
 Always also set `isApplicableToConnectSrc` to `true` for preflight/redirect handling.
 
-4. **Create the metadata file** — follow `implementation/csp-metadata-format.md` for the `.cspTrustedSite-meta.xml` format. Place in `force-app/main/default/cspTrustedSites/`.
+4. **Create the metadata file** — follow `references/csp-metadata-format.md` for the `.cspTrustedSite-meta.xml` format. Place in `force-app/main/default/cspTrustedSites/`.
 

package/skills/experience-ui-bundle-site-generate/SKILL.md

@@ -47,23 +47,23 @@ Use the default templates in the docs below. Values in `{braces}` are resolved p
 
 | Metadata Type | Template Reference |
 |--------------|-------------------|
-| Network | [configure-metadata-network.md](docs/configure-metadata-network.md) |
-| CustomSite | [configure-metadata-custom-site.md](docs/configure-metadata-custom-site.md) |
-| DigitalExperienceConfig | [configure-metadata-digital-experience-config.md](docs/configure-metadata-digital-experience-config.md) |
-| DigitalExperienceBundle | [configure-metadata-digital-experience-bundle.md](docs/configure-metadata-digital-experience-bundle.md) |
-| DigitalExperience (sfdc_cms__site) | [configure-metadata-digital-experience.md](docs/configure-metadata-digital-experience.md) |
+| Network | [configure-metadata-network.md](references/configure-metadata-network.md) |
+| CustomSite | [configure-metadata-custom-site.md](references/configure-metadata-custom-site.md) |
+| DigitalExperienceConfig | [configure-metadata-digital-experience-config.md](references/configure-metadata-digital-experience-config.md) |
+| DigitalExperienceBundle | [configure-metadata-digital-experience-bundle.md](references/configure-metadata-digital-experience-bundle.md) |
+| DigitalExperience (sfdc_cms__site) | [configure-metadata-digital-experience.md](references/configure-metadata-digital-experience.md) |
 
-For URL updates, see [update-site-urls.md](docs/update-site-urls.md).
+For URL updates, see [update-site-urls.md](references/update-site-urls.md).
 
 ### Execution Note for Step 3: Load and use the docs
-- Agents MUST read the full contents of each docs/*.md file referenced in Step 3 before attempting to populate metadata fields.
+- Agents MUST read the full contents of each references/*.md file referenced in Step 3 before attempting to populate metadata fields.
 - Use your platform's file-read tool (for example, `read_file`) to load these files in full, then perform placeholder substitution for values in `{braces}` using the resolved properties from Step 1.
 - Files to load:
-  - `docs/configure-metadata-network.md`
-  - `docs/configure-metadata-custom-site.md`
-  - `docs/configure-metadata-digital-experience-config.md`
-  - `docs/configure-metadata-digital-experience-bundle.md`
-  - `docs/configure-metadata-digital-experience.md`
+  - `references/configure-metadata-network.md`
+  - `references/configure-metadata-custom-site.md`
+  - `references/configure-metadata-digital-experience-config.md`
+  - `references/configure-metadata-digital-experience-bundle.md`
+  - `references/configure-metadata-digital-experience.md`
 - Read entire file contents, replace placeholders (e.g. `{siteName}`) with the resolved values, then use the expanded templates to populate the metadata XML/JSON content.
   
 ### Step 4: Do Not Modify Non-Templated Properties
@@ -88,5 +88,5 @@ sf project deploy validate --metadata Network CustomSite DigitalExperienceConfig
 **Use when** user wants to update or change site URLs (urlPathPrefix).
 
 **Steps**:
-- [ ] Read [update-site-urls.md](docs/update-site-urls.md) to understand the three-component architecture and URL update workflow
+- [ ] Read [update-site-urls.md](references/update-site-urls.md) to understand the three-component architecture and URL update workflow
 - [ ] Follow the step-by-step workflow in the doc to update URLs consistently across all three components (DigitalExperienceConfig, Network, CustomSite)

package/skills/integration-connectivity-generate/SKILL.md

@@ -163,8 +163,8 @@ Next step: <deploy, register, test, or implement>
 - `assets/endpoint-security/` — Remote Site Setting and CSP Trusted Site XML templates
 
 ### Automation hooks
-- `hooks/scripts/suggest_credential_setup.py` — auto-suggests credential configuration steps when integration files are detected
-- `hooks/scripts/validate_integration.py` — validates integration patterns before agent responses
+- `scripts/suggest_credential_setup.py` — auto-suggests credential configuration steps when integration files are detected
+- `scripts/validate_integration.py` — validates integration patterns before agent responses
 
 ---
 

package/skills/omnistudio-callable-apex-generate/SKILL.md

@@ -175,7 +175,7 @@ action contract stable.
 
 ---
 
-## ⛔ Guardrails (Mandatory)
+## Guardrails (Mandatory)
 
 Stop and ask the user if any of these would be introduced:
 - Dynamic method execution based on user input (no reflection)

package/skills/platform-apex-logs-debug/references/benchmarking-guide.md

@@ -228,7 +228,7 @@ public void processWithSafety(List<Account> accounts) {
 
 ## Benchmarking Anti-Patterns
 
-### ❌ Don't Do These
+### Don't Do These
 
 | Anti-Pattern | Problem | Solution |
 |--------------|---------|----------|

package/skills/platform-apex-test-run/SKILL.md

@@ -143,7 +143,7 @@ Next step: <fix class, add test, rerun scope, or widen regression>
 | `assets/test-data-factory.cls` | Template: reusable `TestDataFactory` with create and insert helpers |
 | `assets/dml-mock.cls` | Template: `IDML` interface + `DMLMock` implementation for database-free unit tests |
 | `assets/stub-provider-example.cls` | Template: `StubProvider`-based dependency injection stub |
-| `hooks/scripts/parse-test-results.py` | Post-tool hook — parses `sf apex run test` JSON output and formats failures for the auto-fix loop |
+| `scripts/parse-test-results.py` | Post-tool hook — parses `sf apex run test` JSON output and formats failures for the auto-fix loop |
 
 ---
 

package/skills/platform-apex-test-run/references/testing-best-practices.md

@@ -324,7 +324,7 @@ static void testBulkOperation_StaysWithinLimits() {
 
 ## Common Anti-Patterns to Avoid
 
-### ❌ SeeAllData=true
+### SeeAllData=true
 
 ```apex
 // ❌ BAD: Depends on org data
@@ -342,7 +342,7 @@ static void testGoodPattern() {
 }
 ```
 
-### ❌ No Assertions
+### No Assertions
 
 ```apex
 // ❌ BAD: No assertions - test passes even if code is broken
@@ -364,7 +364,7 @@ static void testWithAssertions() {
 }
 ```
 
-### ❌ Hardcoded IDs
+### Hardcoded IDs
 
 ```apex
 // ❌ BAD: Hardcoded IDs fail across orgs

package/skills/platform-custom-application-generate/SKILL.md

@@ -19,7 +19,7 @@ Use this skill when you need to:
 
 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
+## Purpose
 - Organize related functionality into focused applications
 - Group tabs and components for specific user roles
 - Provide tailored user experiences
@@ -29,7 +29,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - Override standard actions with custom Lightning pages for enhanced user experience
 - Enable profile-specific experiences through profile action overrides
 
-## ⚙️ Required Properties
+## Required Properties
 
 ### Core Application Properties
 - **fullName**: API name of the application
@@ -51,7 +51,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **isNavPersonalizationDisabled**: Personalization setting (default: false)
 - **isNavTabPersistenceDisabled**: Tab persistence setting (default: false)
 
-## 🔧 Application Configuration
+## Application Configuration
 
 ### Navigation Type Selection (CRITICAL)
 **Decision Criteria for navType:**
@@ -116,7 +116,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **profileActionOverrides.profile**: Profile API name (e.g., "Admin", "Standard User")
     - Enables different page layouts for different user profiles
 
-## 📱 Device Support
+## Device Support
 
 ### Desktop Configuration
 - **formFactor**: "Large"
@@ -130,7 +130,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **formFactor**: "Medium"
 - **tabs**: Tablet-appropriate tab selection
 
-## 🎨 User Experience Features
+## User Experience Features
 
 ### Navigation Behavior
 - **Auto Temporary Tabs**: Can be enabled/disabled
@@ -142,12 +142,12 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **Screen Reader**: Compatible with assistive technologies
 - **High Contrast**: Support for high contrast modes
 
-## 🔗 Integration Points
+## 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
+## 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
@@ -168,7 +168,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **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
+## 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
@@ -192,7 +192,7 @@ Custom applications (Lightning Apps) that group tabs and functionality to provid
 - **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)
+## 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