New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Experience UI Bundle Custom App Generate

by forcedotcom in forcedotcom/sf-skills

MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience.

Apache-2.0Auto-check passedSales & Support

Install Experience UI Bundle Custom App Generate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-custom-app-generate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills experience-ui-bundle-custom-app-generate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/experience-ui-bundle-custom-app-generate .claude/skills/experience-ui-bundle-custom-app-generate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
experience-ui-bundle-custom-app-generate
GitHub stars
1.1k
Token cost
~2.3k tokens
SKILL.md length
943 words
Files
3 (incl. scripts, references)
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience.

  • Works in 6 steps: Resolve All Required Properties → Query API Context (Version-Aware Field… → Create the Project Structure → …
  • Creating a CustomApplication metadata record to surface the UI bundle in the App Launcher
  • SKILL.md covers Required Properties, Generation Workflow and Verification Checklist
  • Runs JavaScript scripts from its folder; calls sf and node; reaches soap.sforce.com

What it does

Experience UI Bundle Custom App Generate is an agent skill from forcedotcom/sf-skills. MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience. Use this skill when creating a CustomApplication metadata record to surface the UI bundle in the App Launcher. Activate when files matching applications/.app-meta.xml exist and need modification, or when the user wants to expose their app via the Lightning App Launcher without a Digital Experience Site. Do NOT use…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/configure-metadata-custom-application.md`).

It sits in Sales & Support. It works with Salesforce and React. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • Creating a CustomApplication metadata record to surface the UI bundle in the App Launcher
  • Wants to expose their app via the Lightning App Launcher without a Digital Experience Site

Example prompts

  • “/experience-ui-bundle-custom-app-generate”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Resolve All Required Properties
  2. Query API Context (Version-Aware Field Discovery)
  3. Create the Project Structure
  4. Populate All Metadata Fields
  5. Update UI Bundle Meta XML
  6. Do Not Modify Non-Templated Properties

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • sf
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • soap.sforce.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Experience UI Bundle Custom App Generate loads about 2.3k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 164 tokens; SKILL.md has 943 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~164
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 943 words, ~2,252 tokens.

Download SKILL.mdSave it as .claude/skills/experience-ui-bundle-custom-app-generate/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
experience-ui-bundle-custom-app-generate
description
MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience. Use this skill when creating a CustomApplication metadata record to surface the UI bundle in the App Launcher. Activate when files matching applications/*.app-meta.xml exist and need modification, or when the user wants to expose their app via the Lightning App Launcher without a Digital Experience Site. Do NOT use platform-custom-application-generate for this — UI bundle apps do not use tabs, action overrides, or flexipages.
metadata.version
1.0
metadata.domains
Experience, Platform
metadata.minApiVersion
65.0
metadata.relatedSkills
platform-custom-application-generate

Custom Application for React UI Bundles

Create and configure a Salesforce Custom Application that hosts a React UI bundle in Lightning Experience. This skill generates the CustomApplication metadata so the app appears in the Lightning App Launcher and can be accessed by internal users.

Custom Applications differ from Experience Sites: they don't need Networks, CustomSite, DigitalExperienceConfig, or DigitalExperienceBundle metadata. The Custom Application acts as a thin launcher entry that delegates rendering to the React UI bundle referenced by uiBundle.

Required Properties

Resolve all properties before generating any metadata. Each has a fallback chain — work through each option in order until a value is found.

PropertyFormatHow to Resolve
appNamelowercamelcase (e.g., myInternalApp)The UI bundle name from uiBundles/<name>/ directory
appNamespaceStringnamespace in sfdx-project.json → sf data query -q "SELECT NamespacePrefix FROM Organization" --target-org ${usernameOrAlias} → default c
appLabelHuman-readable stringUser-provided, or derive from appName by converting camelCase to Title Case

The appNamespace and appName connect the Custom Application to the correct React UI bundle. In newer API versions this uses <uiBundle>{appNamespace}__{appName}</uiBundle>; in older versions it uses <webApplication>{appName}</webApplication>. Getting this wrong means the app launcher entry exists but shows a blank page. Step 2 of the workflow determines which field to use.

Generation Workflow

Step 1: Resolve All Required Properties

Determine values for all properties before constructing anything. Use the resolution strategies in the table above.

Step 2: Query API Context (Version-Aware Field Discovery)

Call salesforce-api-context MCP tools to discover which fields exist for the target org's API version. This ensures the generated metadata is compatible with the user's Salesforce version.

Required calls — use the metadataType parameter exactly as shown. Do not substitute a detail parameter or any other shape; metadataType is the only parameter this tool accepts:

  1. get_metadata_type_fields({ "metadataType": "CustomApplication" }) — check whether the uiBundle field exists in the response's field list
  2. get_metadata_type_fields({ "metadataType": "UIBundle" }) — check whether the target field exists in the response's field list

Field resolution based on API response:

Field CheckIf presentIf absent (older API version)
CustomApplication.uiBundleUse <uiBundle>{appNamespace}__{appName}</uiBundle>Use <webApplication>{appName}</webApplication> (no namespace)
UIBundle.targetUse <target>CustomApplication</target>Omit the <target> element entirely

If salesforce-api-context is unavailable after a real attempt, fall back to the newer field names (uiBundle + target).

Step 3: Create the Project Structure

Create any files and directories that don't already exist:

Metadata TypePath
CustomApplication<sourceDir>/applications/{appName}.app-meta.xml

Note: <sourceDir> is determined from sfdx-project.json. Read packageDirectories[] and use the entry where "default": true; the full source directory is <path>/main/default. If no default is set, use the first entry. Commonly force-app/main/default, but this path is configurable.

Step 4: Populate All Metadata Fields

Use the default template in the doc below. Values in {braces} are resolved property references — substitute them with the actual values from Step 1. Apply the field resolution from Step 2 to determine which XML elements to use.

Metadata TypeTemplate Reference
CustomApplicationconfigure-metadata-custom-application.md
Execution Note for Step 4: Load and use the doc
  • 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.
Show full SKILL.md (400 more words)Show less
Step 5: Update UI Bundle Meta XML

This step edits an existing file — it never creates a new one. UIBundle is a bundle-style metadata type: its meta XML normally lives inside its own folder at uiBundles/{appName}/{appName}.uibundle-meta.xml, alongside the bundle's other source files (e.g. index.html, src/). Some older or hand-authored projects may instead have it at the flat path uiBundles/{appName}.uibundle-meta.xml (no subfolder).

Run node scripts/resolve-uibundle-path.mjs "{appName}" — it prints the path of the existing meta XML (preferring the nested layout, falling back to the flat layout). Always invoke via node (never as a bare executable) so this works on Windows as well as macOS/Linux. Edit that exact file in place; do not create a second file at the other path or migrate it to a different layout as part of this skill.

If Step 2 confirmed the target field exists on UIBundle, add <target>CustomApplication</target> inside the existing <UIBundle> element of that file, preserving every other existing element and value untouched (skip this step entirely if the field doesn't exist in the org's API version — do not create the file or add <target> in that case).

Do NOT:

  • Create a new .uibundle-meta.xml file
  • Create a second .uibundle-meta.xml file at a different path when one already exists (nested or flat) — edit the existing one in place, wherever it is
  • Leave the original uiBundles/{appName}/{appName}.uibundle-meta.xml (or uiBundles/{appName}.uibundle-meta.xml, if that's the existing layout) unmodified while adding <target> somewhere else

The only files this skill produces or modifies are applications/{appName}.app-meta.xml (new) and the existing {appName}.uibundle-meta.xml (edited in place, only if <target> applies). Any other UI-bundle-related file appearing in the output is a bug.

Example of the fully updated file (at uiBundles/{appName}/{appName}.uibundle-meta.xml, or the flat path if that's the existing layout) — this illustrates the end state of the existing file, not a new file to create:

xml
<?xml version="1.0" encoding="UTF-8"?>
<UIBundle xmlns="http://soap.sforce.com/2006/04/metadata">
    <masterLabel>{appName}</masterLabel>
    <description>A Salesforce UI Bundle.</description>
    <isActive>true</isActive>
    <version>1</version>
    <target>CustomApplication</target>
</UIBundle>
Step 6: Do Not Modify Non-Templated Properties

Do not modify any default property values for CustomApplication metadata that are not expressed as variables wrapped in {braces}.

Verification Checklist

Before deploying, confirm:

  • All required properties are resolved
  • API context was queried to determine available fields (Step 2)
  • applications/{appName}.app-meta.xml exists with correct content
  • The bundle reference field matches the org's API version (<uiBundle> or <webApplication>)
  • If target field is supported: the existing {appName}.uibundle-meta.xml (nested at uiBundles/{appName}/, or flat at uiBundles/, whichever already existed) has <target>CustomApplication</target>
  • No extra .uibundle-meta.xml file was created — exactly one {appName}.uibundle-meta.xml exists, at whichever path it already lived at
  • Deployment validates successfully:
bash
sf project deploy validate --metadata CustomApplication UIBundle --target-org ${usernameOrAlias}

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in skills/experience-ui-bundle-custom-app-generate of forcedotcom/sf-skills.

  • SKILL.md
  • references/configure-metadata-custom-application.md
  • scripts/resolve-uibundle-path.mjs

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Experience UI Bundle Custom App Generate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Experience UI Bundle Custom App Generate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Experience UI Bundle Custom App Generate this skillforcedotcom/sf-skills1.1k—~2.3kAutomated safety check: PassApache-2.0
Services Extension Consumptionforcedotcom/salesforcedx-vscode1k—~5kAutomated safety check: PassBSD-3-Clause
Gh Bot Commentjetstreamapp/jetstream125—~616Automated safety check: PassCustom licence
Core Extension APIforcedotcom/salesforcedx-vscode1k—~842Automated safety check: PassBSD-3-Clause
Sf ApexJaganpro/sf-skills424—~2kAutomated safety check: PassMIT
Sf DebugJaganpro/sf-skills424—~1.3kAutomated safety check: PassMIT

Similar skills

  • Services Extension Consumption

    forcedotcom/salesforcedx-vscode

    Consume the salesforcedx-vscode-services extension API. An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~5k tokensUpdated today
    Sales & SupportAuto-check passed

  • Gh Bot Comment

    jetstreamapp/jetstream

    Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.

    125 GitHub stars~616 tokensUpdated today
    DevelopmentAuto-check passed

  • Core Extension API

    forcedotcom/salesforcedx-vscode

    Public API exported by salesforcedx-vscode-core activate(). An agent skill from forcedotcom/salesforcedx-vscode.

    1k GitHub stars~842 tokensUpdated today
    Sales & SupportAuto-check passed

  • Sf Apex

    Jaganpro/sf-skills

    Generates and reviews Salesforce Apex code with 150-point scoring.

    424 GitHub stars~2k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Sf Debug

    Jaganpro/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring.

    424 GitHub stars~1.3k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Churn Risk

    indranilbanerjee/digital-marketing-pro

    Score customer segments for churn risk from behavioral signals — email engagement decline, purchase recency, usage drops, support sentiment — producing a 0-100 risk scorecard with four tiers…

    855 GitHub starsUsed in 1 repo~2.4k tokens
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 251 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated yesterday
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Experience UI Bundle Custom App Generate

What does Experience UI Bundle Custom App Generate do?

MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience. Experience UI Bundle Custom App Generate is an agent skill from forcedotcom/sf-skills. MUST activate when the project contains a uiBundles//src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience.

When should I use Experience UI Bundle Custom App Generate?

Experience UI Bundle Custom App Generate fits situations like: creating a CustomApplication metadata record to surface the UI bundle in the App Launcher; wants to expose their app via the Lightning App Launcher without a Digital Experience Site.

How do I install Experience UI Bundle Custom App Generate in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-custom-app-generate -a claude-code`. Or copy the skill folder (skills/experience-ui-bundle-custom-app-generate in forcedotcom/sf-skills) into .claude/skills/experience-ui-bundle-custom-app-generate in your project. Claude Code loads it when a task matches its description.

How do I install Experience UI Bundle Custom App Generate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-custom-app-generate -a codex`. Or copy the skill folder (skills/experience-ui-bundle-custom-app-generate in forcedotcom/sf-skills) into .agents/skills/experience-ui-bundle-custom-app-generate in your project. Codex loads it when a task matches its description.

Can I use Experience UI Bundle Custom App Generate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill experience-ui-bundle-custom-app-generate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/experience-ui-bundle-custom-app-generate, .gemini/skills/experience-ui-bundle-custom-app-generate, .github/skills/experience-ui-bundle-custom-app-generate and .opencode/skills/experience-ui-bundle-custom-app-generate in your project.

What does Experience UI Bundle Custom App Generate need to run?

Going by SKILL.md and its folder, Experience UI Bundle Custom App Generate needs JavaScript for the scripts in its folder and the command-line tools its instructions call (sf and node). Our summary lists: Node.js.

Does Experience UI Bundle Custom App Generate access the network?

SKILL.md names 1 domain. In commands or code: soap.sforce.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Experience UI Bundle Custom App Generate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Experience UI Bundle Custom App Generate use?

Experience UI Bundle Custom App Generate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Experience UI Bundle Custom App Generate use?

About 2.3k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 971 tokens, read only when the agent opens those files.

What are the alternatives to Experience UI Bundle Custom App Generate?

Skills that share tags, products or a category with Experience UI Bundle Custom App Generate: Services Extension Consumption (forcedotcom/salesforcedx-vscode, 1k stars), Gh Bot Comment (jetstreamapp/jetstream, 125 stars), Core Extension API (forcedotcom/salesforcedx-vscode, 1k stars) and Sf Apex (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Experience UI Bundle Custom App Generate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.