forcedotcom/sf-skills / skills/experience-ui-bundle-features-generate
experience-ui-bundle-features-generate
VerifiedMUST activate when the project contains a uiBundles/*/src/ directory (React or Angular) and the user wants to add a pre-built feature — such as authentication (login, logout, protected routes, session management) or search (global search across pages and content) — instead of building it from scratch. Always run list first to see the current feature catalog, since it can include more than authentication and search. Always use this skill for installing pre-built features rather than hand-building them. DO NOT TRIGGER for Agentforce conversational client or file-upload features — use experience-ui-bundle-agentforce-client-generate and experience-ui-bundle-file-upload-generate respectively.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.2 KB |
| references/angular/features.md | markdown | 3.0 KB |
| references/common/conflict-resolution-schema.json | config | 628 B |
| references/react/features.md | markdown | 2.1 KB |
| scripts/detect-framework.shexecutable | script | 2.2 KB |
references/angular/features.md
View on GitHub# Angular UI Bundle Features
Framework reference for the **Angular** path of `experience-ui-bundle-features-generate`. Read
this alongside the workflow spine in `SKILL.md`. The `@salesforce/ui-bundle-features` CLI
installs the Angular variant of each feature into an Angular UI bundle (an `angular.json` at/
above the bundle, `@angular/core` in `package.json`, standalone components as `.ts` + `.html`
pairs under `src/app/`).
## Example files
Features ship integration examples under `__examples__/` as Angular sources — a standalone
component is a **`.ts`** class + its **`.html`** template (e.g. `account-search.ts` +
`account-search.html`), often full working pages, not bare stubs. Integrate the pattern into
the target named in `describe` output, then verify before deleting the `__examples__/` dir.
> Do not assume file names or a `.component` infix — Angular UI bundle starters name
> components without it (`home.ts`, not `home.component.ts`). The `describe` `Copy Operations`
> destination and the copied-in source are the version-matched truth for what was installed.
## Files features may rewrite
Angular features commonly touch app wiring:
- `src/app/app.routes.ts` — route registration (route-based features add routes here)
- `src/app/app.ts` + `src/app/app.html` — root component and its template
- the app-layout component under `src/app/components/layout/` — the shell some features mount into
These are the paths to expect as conflicts in the two-pass conflict flow; resolve them per
`SKILL.md` → *Conflict Handling* (the exact paths are whatever the CLI prints).
## Mount the feature's entry component
Mount the OOTB component the feature ships rather than hand-rolling a parallel one. Angular
mounts by **selector** (in a template) or by **route** (lazy-loaded standalone component) —
use whichever `describe`/README specifies. For search mounted on a results page template:
```html
<!-- search-results.html — use the feature's selector; do NOT hand-roll a results page -->
<sf-search />
```
Or as a route in `src/app/app.routes.ts`:
```ts
export const routes: Routes = [
{ path: "search", loadComponent: () =>
import("./features/search/search").then((m) => m.Search) }, // path per describe output
];
```
Import the feature's standalone component into whichever component's `imports:` array hosts it.
## Build & verify
Build command (run from the UI bundle dir):
```bash
npm run build
```
Worked grep for the *verify-before-delete* check — Angular splits usage across `.ts` (selector
registration, service imports, route entry) and `.html` (the mounted selector). Adjust the
symbol to one from the example you integrated:
```bash
grep -rq "sf-search\|SearchService" src/app --include='*.ts' --include='*.html' 2>/dev/null || {
echo "ERROR: Pattern from example not found in target files - integration incomplete"
echo "Do NOT delete __examples__/ until the pattern is confirmed present"
exit 1
}
```
Only `rm -rf __examples__/` after the build passes **and** this grep confirms the pattern is
present in the target.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |