Lightning Record Page design and deployment guidance. Use when building Lightning pages in App Builder, selecting page templates, adding components, configuring dynamic visibility, or deploying FlexiPages via CLI/API.
From opspal-salesforcenpx claudepluginhub revpalsfdc/opspal-commercial --plugin opspal-salesforceThis skill is limited to using the following tools:
component-library.mddefault-tab-strategy.mddynamic-visibility.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Activate this skill when the user:
A Lightning Record Page (FlexiPage) is a customizable page layout for Lightning Experience that can include:
| Aspect | Classic Page Layout | Lightning Record Page |
|---|---|---|
| Structure | Linear sections | Flexible regions |
| Components | Limited to related lists, buttons | Any Lightning component |
| Visibility | Per layout/profile | Per component rules |
| Tabs | Built-in (Details, Related) | Configurable tabs |
| Customization | Section + field | Component-level |
| Template | Best For | Structure |
|---|---|---|
| Header and One Column | Simple, mobile-first pages | Full-width content |
| Header and Two Columns | Standard record pages | 2/3 + 1/3 split |
| Header and Three Columns | Information-dense pages | Three equal columns |
| Header, Subheader, and One Column | Pages with key metrics | KPIs on top, content below |
| Header and Two Columns (7/5) | Balanced layout | Slight left emphasis |
Choose 1-Column when:
Choose 2-Column when:
Choose 3-Column when:
Always include in header:
| Component | Purpose | When to Use |
|---|---|---|
| Record Detail | Display fields from page layout | Standard field display |
| Field Section (Dynamic Forms) | Individual field control | Per-field visibility needed |
| Tabs | Organize content into tabs | Multiple content areas |
| Accordion | Collapsible sections | Information density |
| Related Lists | Show child records | Always (object dependent) |
| Related List - Single | One specific related list | Highlight important relationships |
| Component | Purpose | When to Use |
|---|---|---|
| Activities | Timeline of activities | User engagement tracking |
| Chatter | Feed and collaboration | Team communication |
| Related Record | Key related record detail | Show parent or key lookup |
| Rich Text | Static instructions | User guidance |
| Report Chart | Visual KPIs | Performance dashboards |
| Component | Purpose | When to Use |
|---|---|---|
| Knowledge | Related articles | Support/service pages |
| Case Comments | Case-specific | Case object only |
| Social Post | Social monitoring | Social Studio integration |
| Einstein | AI recommendations | Einstein enabled orgs |
Dynamic visibility shows/hides components based on:
By Profile:
Filter: User > Profile > Name
Operator: Equals
Value: Sales User
By Record Type:
Filter: Record > Record Type > Name
Operator: Equals
Value: Enterprise
By Field Value:
Filter: Record > Stage
Operator: Equals
Value: Closed Won
By Permission:
Filter: User > Custom Permission
Operator: Is True
Value: View_Sensitive_Data
The default tab is what users see first when opening a record.
Decision Framework:
| Object Type | Recommended Default | Rationale |
|---|---|---|
| Hub objects (Account) | Related | Users seek connected records |
| Process objects (Opportunity) | Details | Users update fields frequently |
| Detail objects (Contact, Lead) | Details | Users view/edit information |
| Support objects (Case) | Related | Users seek context (articles, history) |
| Custom objects | Evaluate workflow | Match primary user task |
In Lightning App Builder:
Lightning pages can be assigned at multiple levels (most specific wins):
Minimize Page Variations:
Assignment Strategy by Scenario:
| Scenario | Approach |
|---|---|
| Same components, different visibility | One page + visibility rules |
| Different components needed | Multiple pages |
| Different apps need different views | Per-app assignment |
| Single org, consistent experience | Org default only |
| Component | Impact | Mitigation |
|---|---|---|
| Report Chart | API call per chart | Limit to 1-2, use tabs |
| Rich Analytics | Heavy rendering | Use only when needed |
| Custom LWC | Varies | Profile custom code |
| Many Related Lists | Multiple queries | Use Related List Quick Links |
Use layout-planning-guide skill to determine:
sf project retrieve start -m "FlexiPage:PageName"
sf project deploy start -m "FlexiPage:PageName"
sf project deploy start -m "FlexiPage:PageName,Profile:SalesUser"
For detailed guidance, see:
template-selection.md - Detailed template comparisoncomponent-library.md - Complete component referencedynamic-visibility.md - Visibility rule patternsdefault-tab-strategy.md - Landing tab recommendations