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
- a React Salesforce UI Bundle project (non-React bundles are not supported β the skill's verify-react-bundle.sh stops otherwise); an Experience Cloud (Customer Community / Customer Community Plus) licensed org for the auth feature (paid license required); npm/npx (>=7.0.0)
- 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:
Install
Prerequisites: a React Salesforce UI Bundle project (non-React bundles are not supported β the skill's verify-react-bundle.sh stops otherwise); an Experience Cloud (Customer Community / Customer Community Plus) licensed org for the auth feature (paid license required); npm/npx (>=7.0.0) Install "Pre-built features installer for UI Bundles" for me. It teaches the agent @forcedotcom's workflow to install pre-built, tested features into a React Salesforce UI Bundle via the @salesforce/ui-bundle-features CLI: list/search the catalog first, describe the feature and read its README before wiring, install with conflict handling (--dry-run, --on-conflict error plus a conflict-resolution file), integrate the example patterns and verify the build passes before deleting __examples__/, mount the shipped entry component instead of hand-rolling a parallel one, and resolve <sfdxRoot> placeholders after every install. Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/experience-react/skills/experience-ui-bundle-features-generate/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "experience-ui-bundle-features-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the verify script on my bundle, pick the feature, and handle any org-side setup the feature needs β like enabling Digital Experiences and granting Apex access for auth). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.