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/mcp_action_examples.md

View on GitHub
# MCP Action Integration — Examples & Reference

Two invocable actions provide component discovery and schema retrieval, called via the `dispatch` MCP tool. The API-version requirement and shared conventions are in SKILL.md → MCP Action Integration.

## discoverUiComponents

Discovers components available for a page type in the user's org.

**When to call:** Tier 2 discovery — after local scan finds no match.

**Input:**
```text
dispatch POST /services/data/<ver>/headless/invocableaction
  body: {
    "action": "discoverUiComponents-discoverUiComponents",
    "inputs": {
      "pageType": "RECORD_PAGE",
      "pageContext": { "entityName": "Account" },
      "searchQuery": "related list"
    }
  }
```

**Parameters** (all go in `inputs`):

| Param | Type | Required | Description |
|-------|------|----------|-------------|
| pageType | String | Yes | `RECORD_PAGE`, `APP_PAGE`, or `HOME_PAGE` |
| pageContext | JSON | Conditional | Required for RECORD_PAGE: `{"entityName": "ObjectApiName"}` |
| searchQuery | String | No | Natural language search from user intent |

**Output:**
```json
{
  "outputs": {
    "componentDefinitions": [
      {
        "definition": "lst/dynamicRelatedList",
        "label": "Dynamic Related List",
        "description": "Shows related records...",
        "attributes": [{"name": "parentFieldApiName", "description": "..."}]
      }
    ]
  }
}
```

**Notes:**
- Output uses forward-slash delimiter (`namespace/blockName`), but XML uses colon (`namespace:blockName`)
- Only returns components compatible with the page type and accessible in the org
- May return empty list if no match — proceed to Tier 3

**When multiple components are returned:**
1. **Best-match selection:** If one component clearly matches user intent (label/description aligns with the request), auto-select it
2. **Ambiguous results:** If multiple components could satisfy the request, present the top candidates to the user with their labels and descriptions, and ask which one to use
3. **Refinement:** If results are too broad, refine the `searchQuery` parameter with more specific keywords from user intent and retry once before prompting the user

## getUiComponentSchemas

Retrieves the full property schema for one or more components.

**When to call:** Tier 2 (org-discovered) components only — skip for Tier 1 (local) and Tier 3 (generated) components; read @api properties from source instead.

**Input:**
```text
dispatch POST /services/data/<ver>/headless/invocableaction
  body: {
    "action": "getUiComponentSchemas-getUiComponentSchemas",
    "inputs": {
      "pageType": "RECORD_PAGE",
      "pageContext": { "entityName": "Account" },
      "componentDefinitions": ["lst/dynamicRelatedList", "flexipage/richText"],
      "includeKnowledge": true
    }
  }
```

**Parameters** (all go in `inputs`):

| Param | Type | Required | Description |
|-------|------|----------|-------------|
| pageType | String | Yes | `RECORD_PAGE`, `APP_PAGE`, or `HOME_PAGE` |
| pageContext | JSON | Conditional | Required for RECORD_PAGE |
| componentDefinitions | List | Yes | Component FQNs (forward-slash format) |
| includeKnowledge | Boolean | No | Include component guidance text (default: true) |

**Output:**
```json
{
  "outputs": {
    "componentSchemas": [
      {
        "definition": "lst/dynamicRelatedList",
        "success": true,
        "schema": "{...JSON Schema string...}",
        "knowledge": "Optional guidance text for this component"
      }
    ]
  }
}
```

**Notes:**
- Supports **partial failures** — each component has its own `success` boolean
- On failure: `{"definition": "...", "success": false, "error": "reason"}`
- When a component schema fails, fall through to Step 3 (smart defaults + LLM inference)
- `knowledge` provides platform-curated guidance — use it alongside instructions files
- Component definition format: always `namespace/blockName` (forward-slash)
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