How do I install the Experience UI Bundle Features Generate skill?

Run npx skillmds add om-scogo/experience-ui-bundle-features-generate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Experience UI Bundle Features Generate safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Experience UI Bundle Features Generate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Experience UI Bundle Features Generate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Experience UI Bundle Features Generate?

om-scogo (@om-scogo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Experience UI Bundle Features Generate by om-scogo

Name: Experience UI Bundle Features Generate
Rating: 4.5 (4 reviews)
Author: om-scogo

Experience UI Bundle Features Generate

MUST activate when the project contains a uiBundles/*/src/ directory and the user wants to add authentication or search to their app. Use this skill when adding authentication or search to a UI bundle app. Only covers two features: authentication (login, logout, protected routes, session management) and search (global search across pages and content). Always use this skill for these two features instead of building from scratch.

om-scogo 2ca61ec 4 files · 8.5 KB Updated Sep 8, 2026 0 repo stars

File contents

UI Bundle Features

Installing Pre-built Features

Always check for an existing feature before building something from scratch. The features CLI installs pre-built, tested packages into Salesforce UI bundles — from foundational UI libraries (shadcn/ui) to full-stack capabilities (authentication, search, navigation, GraphQL, Agentforce AI).

Workflow

Search project code first — check src/ for existing implementations before installing anything. Scope searches to src/ to avoid matching node_modules/ or dist/.
Search available features — use npx @salesforce/ui-bundle-features list with --search <query> to filter by keyword. Use --verbose for full descriptions.
Describe a feature — use npx @salesforce/ui-bundle-features describe <feature> to see components, dependencies, copy operations, and example files.
Install — use npx @salesforce/ui-bundle-features install <feature> --ui-bundle-dir <name>. Key options:
- --dry-run to preview changes
- --yes for non-interactive mode (skips conflicts)
- --on-conflict error to detect conflicts, then --conflict-resolution <file> to resolve them

If no matching feature is found, ask the user before building a custom implementation — a relevant feature may exist under a different name.

Conflict Handling

In non-interactive environments, use the two-pass approach: first run with --on-conflict error to detect conflicts, then create a resolution JSON file ({ "path": "skip" | "overwrite" }) and re-run with --conflict-resolution.

Post-install: Integrating Example Files

Features may include __example__ files showing integration patterns. For each:

Read the example file to understand the pattern
Read the target file (shown in describe output)
Apply the pattern from the example into the target
Delete the example file after successful integration

Hint Placeholders

Some copy paths use <descriptive-name> placeholders (e.g., <desired-page-with-search-input>) that the CLI does not resolve. After installation, rename or relocate these files to the intended target, or integrate their patterns into an existing file.

---name: experience-ui-bundle-features-generatedescription: MUST activate when the project contains a uiBundles/*/src/ directory and the user wants to add authentication or search to their app. Use this skill when adding authentication or search to a UI bundle app. Only covers two features: authentication (login, logout, protected routes, session management) and search (global search across pages and content). Always use this skill for these two features instead of building from scratch.---# UI Bundle Features## Installing Pre-built FeaturesAlways check for an existing feature before building something from scratch. The features CLI installs pre-built, tested packages into Salesforce UI bundles — from foundational UI libraries (shadcn/ui) to full-stack capabilities (authentication, search, navigation, GraphQL, Agentforce AI).### Workflow1. **Search project code first** — check `src/` for existing implementations before installing anything. Scope searches to `src/` to avoid matching `node_modules/` or `dist/`.2. **Search available features** — use `npx @salesforce/ui-bundle-features list` with `--search <query>` to filter by keyword. Use `--verbose` for full descriptions.3. **Describe a feature** — use `npx @salesforce/ui-bundle-features describe <feature>` to see components, dependencies, copy operations, and example files.4. **Install** — use `npx @salesforce/ui-bundle-features install <feature> --ui-bundle-dir <name>`. Key options: - `--dry-run` to preview changes - `--yes` for non-interactive mode (skips conflicts) - `--on-conflict error` to detect conflicts, then `--conflict-resolution <file>` to resolve themIf no matching feature is found, ask the user before building a custom implementation — a relevant feature may exist under a different name.### Conflict HandlingIn non-interactive environments, use the two-pass approach: first run with `--on-conflict error` to detect conflicts, then create a resolution JSON file (`{ "path": "skip" | "overwrite" }`) and re-run with `--conflict-resolution`.### Post-install: Integrating Example FilesFeatures may include `__example__` files showing integration patterns. For each:1. Read the example file to understand the pattern2. Read the target file (shown in `describe` output)3. Apply the pattern from the example into the target4. Delete the example file after successful integration### Hint PlaceholdersSome copy paths use `<descriptive-name>` placeholders (e.g., `<desired-page-with-search-input>`) that the CLI does not resolve. After installation, rename or relocate these files to the intended target, or integrate their patterns into an existing file.

Frequently asked questions