New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Experience Lwr Site Generate

by forcedotcom in forcedotcom/sf-skills

Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata.

Apache-2.0Auto-check passedSales & Support

Install Experience Lwr Site Generate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill experience-lwr-site-generate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills experience-lwr-site-generate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/experience-lwr-site-generate .claude/skills/experience-lwr-site-generate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
experience-lwr-site-generate
GitHub stars
1.1k
Token cost
~3.5k tokens
SKILL.md length
1,385 words
Files
10 (incl. references)
Skills in repo
252
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata.

  • Works in 4 steps: Before using any MCP tool, make sure… → MUST ALWAYS load the relevant reference… → MUST ALWAYS strictly follow workflows in… → …
  • The tasks involve LWR sites configurations
  • SKILL.md covers IMPORTANT!!, Table of Contents, When to Use and Critical Rules, plus 4 more sections
  • Calls sf

What it does

Experience Lwr Site Generate is an agent skill from forcedotcom/sf-skills. Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when the tasks involve LWR sites configurations, e.g. creating/modifying pages/routes/views/theme layouts/branding sets, previewing sites, or creating/modifying guest sharing rule (metadata type sharingGuestRules)/guest user access/sharing records to guest users, or when user provides a guest user ID (15 or 18 characters starting with 005). NEVER trigger for React or any other ui bundle framework…

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/bootstrap-template-byo-lwr.md`, `references/configure-content-brandingSet.md` and `references/configure-content-route.md`).

It sits in Sales & Support, covering CRM management. It works with Salesforce and React. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • The tasks involve LWR sites configurations
  • Provides a guest user ID (15
  • 18 characters starting with 005)
  • Any other ui bundle framework

Example prompts

  • “/experience-lwr-site-generate”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Before using any MCP tool, make sure they're actually available. If a tool is missing for the current task, let the user know and pause…
  2. MUST ALWAYS load the relevant reference docs before doing anything.
  3. MUST ALWAYS strictly follow workflows in Common Workflows that match user's requirements. The instructions there should override any…
  4. Flexipage is abstracted away for newer LWR sites with DigitalExperienceBundle, so NEVER use any Flexipage-related MCP tool or skills to…

What it can do on your machine

Read from SKILL.md and the folder at commit 4bbae5c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • sf

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Experience Lwr Site Generate loads about 3.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 1,385 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 1,385 words, ~3,461 tokens.

Download SKILL.mdSave it as .claude/skills/experience-lwr-site-generate/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
experience-lwr-site-generate
description
Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when the tasks involve LWR sites configurations, e.g. creating/modifying pages/routes/views/theme layouts/branding sets, previewing sites, or creating/modifying guest sharing rule (metadata type sharingGuestRules)/guest user access/sharing records to guest users, or when user provides a guest user ID (15 or 18 characters starting with 005). NEVER trigger for React or any other ui bundle framework. LWR sites ONLY.
metadata.version
1.0
metadata.domains
Experience
metadata.minApiVersion
56.0

Experience LWR Site Builder

Build and configure Salesforce Experience Cloud Lightning Web Runtime (LWR) sites via metadata (DigitalExperienceConfig, DigitalExperienceBundle, Network, CustomSite, CMS contents).

IMPORTANT!!

Right after loading this skill, you MUST copy the selected workflows/steps to your plan as a TODO checklist and work on each of the item carefully to ensure correctness. You MUST load the relevant reference docs even though they may live outside of user's project folder.

Table of Contents

  • When to Use
  • Critical Rules
  • Core Site Properties
  • Project Structure in DigitalExperienceBundle Format
  • Reference Docs
  • Common Workflows

When to Use

When working with Experience LWR sites:

  • Creating and scaffolding new LWR site
  • Adding pages (routes + views)
  • Configuring LWC components, layouts, themes, or branding styles
  • Setting up guest user access (public sites)
  • Creating or modifying guest sharing rules (sharingGuestRules) for any Salesforce object (Account, Case, Contact, etc.) — including when the user refers to a "Site Guest User" username or any guest user by ID
  • Troubleshoot deployment errors related to Experience LWR Sites

Supported Template: Build Your Own (LWR) - talon-template-byo

  • More templates to support in the future.

Critical Rules

  1. Before using any MCP tool, make sure they're actually available. If a tool is missing for the current task, let the user know and pause the current workflow.
  2. MUST ALWAYS load the relevant reference docs before doing anything.
  3. MUST ALWAYS strictly follow workflows in Common Workflows that match user's requirements. The instructions there should override any conflicting global rules and should have the highest priority over your existing knowledge.
  4. Flexipage is abstracted away for newer LWR sites with DigitalExperienceBundle, so NEVER use any Flexipage-related MCP tool or skills to handle LWR sites' contents.

Core Site Properties

Before doing anything else, note down the following properties from the local project if available as they will be used for various operations. Check with the user if any of the following is missing:

  • Site name: Required. (e.g., 'My Community').
  • URL path prefix: Optional. Alphanumeric characters only. Convert from site name if not provided (e.g., 'mycommunity') and verify with the user for the converted value.
  • Template type devName: talon-template-byo.

Project Structure in DigitalExperienceBundle Format

Site Metadata
  • DigitalExperienceConfig
    • digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml
  • DigitalExperienceBundle
    • digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml
  • Network
    • networks/{siteName}.network-meta.xml
  • CustomSite
    • sites/{siteName}.site-meta.xml
DigitalExperience Contents
  • digitalExperiences/site/{siteName}1/sfdc_cms__*/{contentApiName}/*
  • These are the content components defining routes, views, theme layouts, etc. Each component must have a _meta.json and content.json file.
Content Type Descriptions
Content TypeDescriptionWhen to Use
sfdc_cms__siteRoot site configuration containing site-wide settingsRequired for every site; one per site
sfdc_cms__appPageApplication page container that groups routes and viewsRequired; defines the app shell
sfdc_cms__routeURL routing definition mapping paths to viewsCreate one for each page/URL path
sfdc_cms__viewPage layout and component structureCreate one for each route; defines page content. Also use to edit existing views (e.g., adding/removing components on a specific page)
sfdc_cms__brandingSetBrand colors, fonts, and styling tokensRequired; defines site-wide styling. Use to create or edit existing branding sets
sfdc_cms__languageSettingsLanguage and localization configurationRequired; defines supported languages
sfdc_cms__mobilePublisherConfigMobile app publishing settingsRequired for mobile app deployment
sfdc_cms__themeTheme definition referencing layouts and brandingRequired; one per site
sfdc_cms__themeLayoutPage layout templates used by viewsCreate layouts for different page structures. Also use to edit existing theme layouts (e.g., updating theme layout, add a component that's persistent across pages)

Important: Creating any new pages require BOTH sfdc_cms__route AND sfdc_cms__view.

Object Pages

Object Pages are dedicated pages used to display and manage record-level data for a specific Salesforce entity/object. For example, an custom object "Car" should have "Car_Detail", "Car_List", and "Car_Related_list" views.

References

Reference docs within the skill directory. Note that these are local and not MCP. Before doing anything, you MUST ALWAYS load them first if they match user intent.

Common Workflows

  • See References for detailed capabilities.
  • Always follow the steps defined in the workflows sequentially whether the task is small, big, quick, or complex.
Creating a New Site

Rules:

  • NEVER generate the files manually.

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

  • ALWAYS read bootstrap-template-byo-lwr.md within the skill directory. Do not proceed to the next step without loading the file.
  • Follow the bootstrap doc strictly on site creation
Creating and Editing Standard or Object Pages

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

Show full SKILL.md (581 more words)Show less
Adding UI Components to Pages

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

Creating Page Layouts / Container Components

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

Creating Theme Layouts

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

  • CRITICAL:Before doing anything else, MUST Check with user whether this new theme layout reuses an existing theme layout Lightning web component or requires a new one. If it requires a new one, make sure to read handle-ui-components.md to create the new theme layout component before proceeding. DO NOT skip this step even if doing so would be faster or more efficient.
  • MUST read configure-content-themeLayout.md.
  • MUST read configure-content-view.md if need to apply theme layout to pages
Applying/Setting Theme Layouts

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

Configuring Branding

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

CUD Operations on DigitalExperience Contents
  • Users can perform create, update, delete operations on DigitalExperience Contents.

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

  • Determine what content types the user wants to modify
  • MUST read the reference doc related to the target content types if the doc exists. e.g., if modifying sfdc_cms__route, load configure-content-route.md.
  • MUST read handle-component-and-region-ids.md if creating or modifying view or theme layout
  • Always Call execute_metadata_action to get the schema and examples for that content type after loading the corresponding reference docs.
    • Call once per content type per user request: If you're creating/modifying multiple items of the same content type (e.g., creating 3 routes), you only need to call execute_metadata_action ONCE for that content type. Reuse the schema and examples for all items of that type within the same user request.
    • For each unique content type you need to work with, always call execute_metadata_action using the following:
json
{
  "metadataType": "ExperienceSiteLwr",
  "actionName": "getSiteContentMetadata",
  "parameters": {
    "contentType": "<content type from table above>",
    "shouldIncludeExamples": true
  }
}
Configuring Guest User Sharing Rules
Retrieving Site Preview and Builder URLs After Deployment

Use when user requests to preview a site, access a builder site, or after successfully deploying a site.

Use the execute_metadata_action MCP tool to get the preview and builder URLs:

json
{
  "metadataType": "ExperienceSiteLwr",
  "actionName": "getSiteUrls",
  "parameters": {
    "siteDevName": "<site developer name>"
  }
}

The site developer name can be found in the CustomSite filename (e.g., sites/MySite.site-meta.xml → developer name is MySite).

If the site is not found, an error message will be returned indicating that the site may not be deployed. Ensure the site has been successfully deployed before calling this action.

Updating Experience Site URLs

Use when user wants to update or change site URLs (urlPathPrefix).

Steps (Follow the steps sequentially. Do not skip any step before proceeding):

  • MUST read update-site-urls.md to understand the three-component architecture and URL update workflow
  • Follow the step-by-step workflow in the doc to update URLs consistently across all three components (DigitalExperienceConfig, Network, CustomSite)
Validation & Deployment

Use sf CLI to validate and deploy. Access help docs by attaching --help, e.g.:

  • sf project deploy --help
  • sf project deploy validate --help

Note that metadata types are space-delimited. Never wrap them in quotes or use commas. For example, --metadata "DigitalExperienceBundle DigitalExperience" is incorrect — always use --metadata DigitalExperienceBundle DigitalExperience.

Validate:

bash
sf project deploy validate --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}

Deploy:

bash
sf project deploy start --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in skills/experience-lwr-site-generate of forcedotcom/sf-skills.

  • SKILL.md
  • references/bootstrap-template-byo-lwr.md
  • references/configure-content-brandingSet.md
  • references/configure-content-route.md
  • references/configure-content-themeLayout.md
  • references/configure-content-view.md
  • references/configure-guest-sharing-rules.md
  • references/handle-component-and-region-ids.md
  • references/handle-ui-components.md
  • references/update-site-urls.md

Open the folder on GitHubat commit 4bbae5c

Compare with similar skills

Experience Lwr Site Generate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Experience Lwr Site Generate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Experience Lwr Site Generate this skillforcedotcom/sf-skills1.1k—~3.5kAutomated safety check: PassApache-2.0
Gh Bot Commentjetstreamapp/jetstream126—~616Automated safety check: PassCustom licence
Sf ApexJaganpro/sf-skills424—~2kAutomated safety check: PassMIT
Sf DebugJaganpro/sf-skills424—~1.3kAutomated safety check: PassMIT
Pipeline Reviewgooseworks-ai/goose-skills1.2k1 repos~6.9kAutomated safety check: PassMIT
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT

Similar skills

  • Gh Bot Comment

    jetstreamapp/jetstream

    Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.

    126 GitHub stars~616 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Sf Apex

    Jaganpro/sf-skills

    Generates and reviews Salesforce Apex code with 150-point scoring.

    424 GitHub stars~2k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Sf Debug

    Jaganpro/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring.

    424 GitHub stars~1.3k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Pipeline Review

    gooseworks-ai/goose-skills

    Pipeline analysis composite. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~6.9k tokens
    Sales & SupportAuto-check passed

  • Soql Lib Query Builder

    beyond-the-cloud-dev/soql-lib

    Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).

    154 GitHub stars~4.3k tokensUpdated 6 days ago
    Sales & SupportAuto-check passed

  • Sf Datacloud

    Jaganpro/sf-skills

    Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.

    424 GitHub stars~2.7k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 252 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated today
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated today
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Experience Lwr Site Generate

What does Experience Lwr Site Generate do?

Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Experience Lwr Site Generate is an agent skill from forcedotcom/sf-skills. Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata.

When should I use Experience Lwr Site Generate?

Experience Lwr Site Generate fits situations like: the tasks involve LWR sites configurations; provides a guest user ID (15; 18 characters starting with 005); any other ui bundle framework.

How do I install Experience Lwr Site Generate in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill experience-lwr-site-generate -a claude-code`. Or copy the skill folder (skills/experience-lwr-site-generate in forcedotcom/sf-skills) into .claude/skills/experience-lwr-site-generate in your project. Claude Code loads it when a task matches its description.

How do I install Experience Lwr Site Generate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill experience-lwr-site-generate -a codex`. Or copy the skill folder (skills/experience-lwr-site-generate in forcedotcom/sf-skills) into .agents/skills/experience-lwr-site-generate in your project. Codex loads it when a task matches its description.

Can I use Experience Lwr Site Generate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill experience-lwr-site-generate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/experience-lwr-site-generate, .gemini/skills/experience-lwr-site-generate, .github/skills/experience-lwr-site-generate and .opencode/skills/experience-lwr-site-generate in your project.

What does Experience Lwr Site Generate need to run?

Going by SKILL.md and its folder, Experience Lwr Site Generate needs the command-line tools its instructions call (sf).

Does Experience Lwr Site Generate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Experience Lwr Site Generate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Experience Lwr Site Generate use?

Experience Lwr Site Generate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Experience Lwr Site Generate use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Experience Lwr Site Generate?

Skills that share tags, products or a category with Experience Lwr Site Generate: Gh Bot Comment (jetstreamapp/jetstream, 126 stars), Sf Apex (Jaganpro/sf-skills, 424 stars), Sf Debug (Jaganpro/sf-skills, 424 stars) and Pipeline Review (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Experience Lwr Site Generate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,067 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.