Skip to content

forcedotcom/sf-skills / plugins/builder/salesforce-development/skills/platform-flexipage-generate

platform-flexipage-generate

Verified

Use 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.

references/flexipage_richText.md

View on GitHub
# flexipage:richText — Rich Text

## Purpose

Displays HTML-formatted rich text content on a page. Supports text formatting, headings, lists, links, and inline styles. Content is static (not data-bound).

## Supported Page Types

- RecordPage
- AppPage
- HomePage

## Property Table

| Property | Type | Required | Default | Description |
|----------|------|----------|---------|-------------|
| richTextValue | String (HTML-encoded) | Yes | — | HTML content, entity-encoded for XML |
| decorate | Boolean | No | true | Show card-style border/decoration around the content |

## Property Inference Rules

| User Intent | Inferred Properties |
|-------------|-------------------|
| "add rich text with {content}" | `richTextValue` = HTML-encoded version of content |
| "add a heading {text}" | `richTextValue` = `<p><b style="font-size: 16px;">{text}</b></p>` |
| "add a link to {url}" | `richTextValue` = `<p><a href="{url}" rel="noopener noreferrer" target="_blank">{text}</a></p>` |
| "no border" or "borderless" | `decorate` = `false` |
| "with card border" or "in a card" | `decorate` = `true` |

## HTML Encoding Rules

**CRITICAL:** The `richTextValue` must be double-encoded for XML:
1. Write the desired HTML content
2. Entity-encode ALL HTML characters:
   - `&` -> `&` (encode FIRST)
   - `<` -> `&lt;`
   - `>` -> `&gt;`
   - `"` -> `&quot;`

**Example:** To display `<b>Hello</b>`, the value must be `&lt;b&gt;Hello&lt;/b&gt;`

**Supported HTML tags:**
- `<p>` — paragraphs (required wrapper for all content)
- `<b>` — bold
- `<u>` — underline
- `<i>` — italic
- `<a href="..." rel="noopener noreferrer" target="_blank">` — links
- `<span style="...">` — inline styling
- `<br>` or `<br />` — line breaks

**Supported inline styles:**
- `font-size: Npx` (e.g., `12px`, `14px`, `16px`, `18px`)
- `color: #hex` or `color: colorname`
- `text-align: left|center|right`
- `background-color: #hex`

## XML Example

```xml
<itemInstances>
    <componentInstance>
        <componentInstanceProperties>
            <name>richTextValue</name>
            <value>&lt;p style=&quot;text-align: center;&quot;&gt;&lt;b style=&quot;font-size: 16px;&quot;&gt;Welcome to the Account Page&lt;/b&gt;&lt;/p&gt;&lt;p&gt;Use this page to manage account details and related records.&lt;/p&gt;</value>
        </componentInstanceProperties>
        <componentInstanceProperties>
            <name>decorate</name>
            <value>true</value>
        </componentInstanceProperties>
        <componentName>flexipage:richText</componentName>
        <identifier>flexipage_richText</identifier>
    </componentInstance>
</itemInstances>
```

## Edge Cases

- Never put raw HTML in `<value>` tags — always entity-encode
- Encode `&` FIRST before encoding `<` and `>` to avoid double-encoding `&amp;lt;`
- Multiple rich text components on same page: increment identifier (`flexipage_richText`, `flexipage_richText2`)
- Empty content is invalid — always include at least one `<p>` element
- Links must include `rel="noopener noreferrer" target="_blank"` for security
- Can be placed in any region
- Keep content concise — rich text is for static labels/instructions, not data display
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall