Agent skill · forcedotcom

experience-ui-bundle-project-generate

Generates a minimal, ready-to-develop SFDX starter project from template instead of hand-scaffolding files. Use this skill when starting a brand-new Salesforce UI bundle app (React or Angular) and the initial project must be scaffolded — trigger phrases include create, start, or scaffold a new UI bundle app, generate a starter project, or use a prebuilt/starter template. DO NOT TRIGGER when: editing, styling, or adding pages or components to an EXISTING app (use experience-ui-bundle-frontend-generate); configuring ui-bundle.json or metadata files (use experience-ui-bundle-metadata-generate); deploying to an org (use experience-ui-bundle-deploy); or when the user explicitly says they want to hand-scaffold from scratch.

What it needs

About 4k tokens when loaded.

What this skill does

Using a UI Bundle Template Before building a Salesforce UI bundle app from scratch, offer the user a prebuilt starter template. The Salesforce CLI generates these — a complete, deployable SFDX project (UI bundle + toolchain + an npm run setup automation) — in one command. Starting from a starter is faster and less error-prone than hand-scaffolding. The CLI command is sf template generate project. Step 1: Offer the choice Determine the framework. It is normally already decided by the calling context — either passed down by the root/coordinator skill that invoked this one, or stated in the user's request. Use that. The frameworks this skill supports are exactly the reference files under <SKILLDIR>/references/, each named <framework>-project-generate.md (so react → <SKILLDIR>/references/react-project-generate.md). This is the single source of truth — adding a framework means adding a reference file, nothing here changes. If the framework is known — open <SKILLDIR>/references/<framework>-project-generate.md. If it is unknown (a standalone run where nobody said which) — list <SKILLDIR>/references/, derive the supported set by stripping the -project-generate.md suffix from each filename, and ask the user to pick one of those. If the user names a framework with no matching reference file, it is not supported here — hand off to experience-ui-bundle-app-coordinate to scaffold from scratch. Each reference lists that framework's --template flags and what each starter contains. Pick the one that fits the user's audience (internal vs. external). If the user prefers to start from scratch (or neither template fits), stop here and let experience-ui-bundle-app-coordinate scaffold a new project. This skill is opt-in — do not force a template. Once the user picks, carry the chosen --template flag into Step 2. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills forcedotcom/experience-ui-bundle-project-generate--f3a800

View the source on GitHub

Browse the @skills marketplace