forcedotcom/sf-skills / plugins/builder/salesforce-development/skills/platform-flexipage-generate
platform-flexipage-generate
VerifiedUse when users create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger on RecordPage, AppPage, HomePage, Lightning pages, adding components to a page, page customization (e.g. 'customize the record page'), or .flexipage-meta.xml files (regions, components, deployment errors). DO NOT TRIGGER for Visualforce pages, page layout assignments in the UI, UI Bundle/Experience Cloud site pages, or Aura/Lightning Web Component development without FlexiPage context.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.1 KB |
| references/cli_commands.md | markdown | 769 B |
| references/flexipage_fieldSection.md | markdown | 5.8 KB |
| references/flexipage_richText.md | markdown | 3.2 KB |
| references/identifiers_and_regions.md | markdown | 6.0 KB |
| references/mcp_action_examples.md | markdown | 3.8 KB |
| references/record_flexipage_dynamicHighlights.md | markdown | 4.7 KB |
| references/xml_rules.md | markdown | 13.7 KB |
| scripts/resolve-component-instructions.shexecutable | script | 1.2 KB |
| scripts/scan-lwc-components.shexecutable | script | 2.9 KB |
references/record_flexipage_dynamicHighlights.md
View on GitHub# record_flexipage:dynamicHighlights — Dynamic Highlights Panel
## Purpose
Displays the record highlights panel at the top of a record page with a primary identifying field, secondary summary fields, and configurable actions. Replaces the older static `force:highlightsPanel`.
## Supported Page Types
- RecordPage only (always in `header` region)
## Property Table
| Property | Type | Required | Default | Description |
|----------|------|----------|---------|-------------|
| primaryField | String (Facet ref) | Yes | — | Reference to a Facet containing the primary field (typically Record.Name) |
| secondaryFields | String (Facet ref) | No | — | Reference to a Facet containing secondary highlight fields |
| actionNames | valueList | No | — | Actions in the highlights panel: `Edit`, `Delete`, `ChangeOwnerOne`, `Share`, `RecordShareHierarchy` |
| numVisibleActions | Integer | No | 3 | Number of actions shown before overflow menu |
## Structural Pattern
This component uses an **indirect Facet reference** pattern. The `primaryField` and `secondaryFields` properties point to Facet regions that contain `fieldInstance` elements — they are NOT direct field API names.
**Required supporting structure:**
1. A Facet region for `primaryField` containing one `fieldInstance` (the identifying field)
2. A Facet region for `secondaryFields` containing multiple `fieldInstance` elements (summary fields)
## Property Inference Rules
| User Intent | Inferred Properties |
|-------------|-------------------|
| "highlights with {fields}" | Create secondaryFields facet with those fields as fieldInstances |
| "show actions: Edit, Delete" | `actionNames` = valueList with `Edit`, `Delete` |
| "show {N} actions" | `numVisibleActions` = `{N}` |
**Field selection:** Primary = `Record.Name` (or object's identifying field). Secondary = 4-6 useful fields (max 12). Prefer CLI `--secondary-fields` values if available.
## XML Example
```xml
<!-- Component in header region -->
<flexiPageRegions>
<itemInstances>
<componentInstance>
<componentInstanceProperties>
<name>actionNames</name>
<valueList>
<valueListItems>
<value>Edit</value>
</valueListItems>
<valueListItems>
<value>Delete</value>
</valueListItems>
<valueListItems>
<value>ChangeOwnerOne</value>
</valueListItems>
</valueList>
</componentInstanceProperties>
<componentInstanceProperties>
<name>numVisibleActions</name>
<value>3</value>
</componentInstanceProperties>
<componentInstanceProperties>
<name>primaryField</name>
<value>Facet-primary-field-001</value>
</componentInstanceProperties>
<componentInstanceProperties>
<name>secondaryFields</name>
<value>Facet-secondary-fields-001</value>
</componentInstanceProperties>
<componentName>record_flexipage:dynamicHighlights</componentName>
<identifier>record_flexipage_dynamicHighlights</identifier>
</componentInstance>
</itemInstances>
<name>header</name>
<type>Region</type>
</flexiPageRegions>
<!-- Primary field Facet -->
<flexiPageRegions>
<itemInstances>
<fieldInstance>
<fieldInstanceProperties>
<name>uiBehavior</name>
<value>none</value>
</fieldInstanceProperties>
<fieldItem>Record.Name</fieldItem>
<identifier>RecordNameField</identifier>
</fieldInstance>
</itemInstances>
<name>Facet-primary-field-001</name>
<type>Facet</type>
</flexiPageRegions>
<!-- Secondary fields Facet (same structure as primary, multiple fieldInstances) -->
<flexiPageRegions>
<itemInstances>
<fieldInstance>
<fieldInstanceProperties>
<name>uiBehavior</name>
<value>none</value>
</fieldInstanceProperties>
<fieldItem>Record.Phone</fieldItem>
<identifier>RecordPhoneField</identifier>
</fieldInstance>
</itemInstances>
<name>Facet-secondary-fields-001</name>
<type>Facet</type>
</flexiPageRegions>
```
## Edge Cases
- Only ONE per page — never multiple instances
- Always in `header` region — never in `main` or sidebar
- Facet names must be unique UUIDs or descriptive names
- Primary field `uiBehavior` is `none`; secondary fields also use `none`
- If CLI already generated highlights, modify existing — do not add a duplicate
- Identifier is always `record_flexipage_dynamicHighlights` (singular, never numbered)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |