Pre-built features installer for UI Bundles
Install pre-built, tested features (auth, search, shadcn/ui foundations) into React Salesforce UI Bundles via the features CLI
- What
- Install pre-built, tested features (auth, search, shadcn/ui foundations) into React Salesforce UI Bundles via the features CLI
- Cost
- Free
- Needs
- npm and npx (>= 7.0.0); an existing Salesforce UI Bundle project in React or Angular (the skill detects the framework deterministically and stops if it finds neither); for the authentication feature, a Salesforce org with Sites enabled and Experience Cloud (Customer Community / Customer Community Plus) licenses — a paid Salesforce license — plus org-side setup after the files are installed (Digital Experiences enabled, Apex class access, sharing rules). Nothing is needed to install the skill files themselves.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — 💳 Paid API required / API payante requise — this skill's own access check requires an Experience Cloud (Customer Community / Customer Community Plus) licensed org; the listing is free, but running it needs a paid Salesforce license. @forcedotcom's workflow for installing pre-built, tested features into React Salesforce UI Bundles with the `@salesforce/ui-bundle-features` CLI instead of hand-building them: always run `list` first (the catalog grows), `describe` the feature before wiring (the README is the contract), install with conflict handling (`--dry-run`, `--on-conflict error` + resolution file), then verify the integration actually runs before deleting `__examples__/` (build must pass, pattern confirmed present). Mount the shipped entry component — don't hand-roll a parallel one — and always resolve `<sfdxRoot>` placeholders after every install so files land in the real metadata root. By @forcedotcom, listed here with credit to its creator. Honest caveats: React UI bundles only (the skill's verify script stops on non-React); auth and Agentforce-conversation features are owned by separate skills — confirm the delivery path before installing; the auth feature carries a known logout CSRF-handling gap (tracked as W-21253864) and still needs org-side config (Digital Experiences enabled, Sites, Apex class access for auth classes) that this skill cannot do for you. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Pre-built features installer for UI Bundles is a free Muse skill, a workflow installing pre-built, tested features into React Salesforce UI Bundles via the @salesforce/ui-bundle-features CLI. Always run list first, catalog grows, describe the feature before wiring, README is the contract, requires a paid Salesforce license, Experience Cloud org, Customer Community or Plus, listing itself free.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 72d9f5fBefore you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: npm and npx (>= 7.0.0); an existing Salesforce UI Bundle project in React or Angular (the skill detects the framework deterministically and stops if it finds neither); for the authentication feature, a Salesforce org with Sites enabled and Experience Cloud (Customer Community / Customer Community Plus) licenses — a paid Salesforce license — plus org-side setup after the files are installed (Digital Experiences enabled, Apex class access, sharing rules). Nothing is needed to install the skill files themselves. Install "Pre-built features installer for UI Bundles" for me. It installs pre-built, tested feature packages — authentication, search and a growing catalog — into a Salesforce UI Bundle with the @salesforce/ui-bundle-features CLI instead of hand-building them: determine the framework first (from the calling context, or the skill's deterministic detect-framework.sh script; ambiguous means ask me, unknown means stop), search the project code before installing anything, list and describe a feature and read its README before wiring it, install with two-pass conflict handling, integrate the __examples__/ patterns and verify the build passes before deleting them, mount the feature's shipped entry component instead of hand-rolling a parallel one, and resolve any <sfdxRoot> placeholder folders after every install. Source: https://raw.githubusercontent.com/forcedotcom/sf-skills/72d9f5f43614c1de9596913d887685d069ec9a73/skills/experience-ui-bundle-features-generate/SKILL.md (the skill is the whole skills/experience-ui-bundle-features-generate/ folder at that commit — SKILL.md plus its references/ and scripts/ subfolders) Pinned version: install the code at commit 72d9f5f43614c1de9596913d887685d069ec9a73 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 16, 2026: Skill Harbor regenerated this install prompt from the current upstream file. What changed since the version the previous prompt described (skill 1.1, at commit e5164d94): the skill is now version 1.2 and framework-neutral — it supports Angular as well as React, chooses the framework from the calling context or a deterministic detector script, and keeps framework-specific detail in per-framework reference files; the access check is now written as a single formula (the Sites org preference AND the Experience Cloud Customer Community / Customer Community Plus license); it warns never to use the deprecated @salesforce/ui-bundle-features-experimental package name; and it spells out the authentication feature's org-side prerequisites, including a documented CSRF-handling gap in logout (tracked as W-21253864) that must be called out rather than presented as solved. One packaging note: at this commit the repository also ships a plugin-packaged copy of this skill (under plugins/builder/experience-react/), but that copy's folder is missing files the skill itself references — the framework detector script and the per-framework reference files. This prompt therefore installs the complete copy from the repository's root skills/ folder; the SKILL.md file is byte-identical in both places (same fingerprint below). 1. Download the whole skills/experience-ui-bundle-features-generate/ folder at the pinned commit — SKILL.md and every file under references/ and scripts/ — into a temporary folder. 2. Compare SKILL.md with the fingerprint from Skill Harbor's review of October 16, 2026: - SKILL.md: SHA-256 97a6a60bfefd01de9afdf65032bea8e8f36542a4ce633d6de45f942e10838a0c If it does not match, it changed since the review: do not install it yet — tell me what you found and let me decide. 3. Read SKILL.md and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Nothing is sent anywhere during installation itself. 4. When I say yes, copy the whole folder's contents into my skills folder, in a folder named "experience-ui-bundle-features-generate", keeping every subfolder as it is. 5. Check the copy with no network calls (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do (for example: point the skill at my UI Bundle project, let it detect or confirm the framework, pick a feature from the catalog, and handle the org-side setup the authentication feature needs). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me. Never print or paste a secret value.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 72d9f5f · 2026-10-16
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.