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 Lwc Base Components Integrate

by forcedotcom in forcedotcom/sf-skills

Pick the right Lightning Base Component (lightning-) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC…

Apache-2.0Auto-check passedFrontend & Design

Install Experience Lwc Base Components Integrate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill experience-lwc-base-components-integrate -a claude-code

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills experience-lwc-base-components-integrate --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-lwc-base-components-integrate .claude/skills/experience-lwc-base-components-integrate && 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-lwc-base-components-integrate
GitHub stars
1.1k
Token cost
~2.1k tokens
SKILL.md length
914 words
Files
5 (incl. scripts, references)
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pick the right Lightning Base Component (lightning-) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC…

  • Works in 6 steps: Read the entire component index first → Narrow to the most specific fit per… → Share the shortlist and confirm → …
  • Users say I need a Lightning modal / datatable / combobox / record form
  • SKILL.md covers When to Use This Skill, Prerequisites, Workflow and Examples, plus 2 more sections
  • Runs Shell scripts from its folder

What it does

Experience Lwc Base Components Integrate is an agent skill from forcedotcom/sf-skills. Pick the right Lightning Base Component (lightning-) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC .html, .js, and .css files) without breaking SLDS. Use this skill when users say "I need a Lightning modal / datatable / combobox / record form", ask which lightning- component fits a use case, want a shortlist of LBC candidates, are about to hand-roll a UI that a base component already provides, or are editing an LWC…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/lbc-expert-guidance.md`, `references/lightning-component-index.md` and `references/lightning-components.md`).

It sits in Frontend & Design, covering Design systems and Design tokens. It works with Salesforce. 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

  • Users say I need a Lightning modal / datatable / combobox / record form
  • Ask which lightning- component fits a use case
  • Want a shortlist of LBC candidates
  • Are about to hand-roll a UI that a base component already provides

Example prompts

  • “I need a Lightning modal / datatable / combobox / record form”
  • “Lightning base component”
  • “lightning-combobox”
  • “/experience-lwc-base-components-integrate”

Requirements

  • A Bash shell

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read the entire component index first
  2. Narrow to the most specific fit per feature
  3. Share the shortlist and confirm
  4. Retrieve full API docs
  5. Produce integration guidance
  6. Respect LBC styling rules

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. 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

    Ships 1 file in scripts/ (Shell), which the agent can run.

    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 Lwc Base Components Integrate loads about 2.1k tokens when it runs, and up to ~120k if it reads all its reference files. Until then it costs about 242 tokens; SKILL.md has 914 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 914 words, ~2,121 tokens.

Download SKILL.mdSave it as .claude/skills/experience-lwc-base-components-integrate/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
experience-lwc-base-components-integrate
description
Pick the right Lightning Base Component (`lightning-*`) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC `.html`, `.js`, and `.css` files) without breaking SLDS. Use this skill when users say "I need a Lightning modal / datatable / combobox / record form", ask which `lightning-*` component fits a use case, want a shortlist of LBC candidates, are about to hand-roll a UI that a base component already provides, or are editing an LWC bundle's `.html` / `.js` / `.css` and need to select or wire a base component. Also triggers on "Lightning base component", "LBC", "lightning-combobox", "lightning-datatable", "use `lightning-` tag". DO NOT TRIGGER for applying SLDS design tokens, blueprints, or styling guidance in general — that is `design-systems-slds-apply`; this skill only selects and wires `lightning-*` base components.
metadata.version
1.0
metadata.domains
Experience
metadata.relatedSkills
design-systems-slds-apply
<!-- adk-managed-skill -->

Using Lightning Base Components

Lightning Base Components (LBC) are the lightning-* web components shipped by Salesforce. This skill routes an agent through the right decision sequence so the final component choice is as specific as possible and backed by real API docs — not a hand-rolled reimplementation of something that already exists.

When to Use This Skill

  • User describes a UI need ("searchable dropdown", "record edit form", "modal with footer") and asks which lightning-* component fits.
  • User is about to build a primitive (button group, combobox, toast) and should be using LBC instead.
  • User asks you to review LWC markup for LBC-related issues — specifically overriding SLDS classes or restyling LBC internals.
  • User needs the authoritative props/events/slots for a specific lightning-* tag.

Prerequisites

  • Knowledge of which LBC namespace your org uses (lightning is the default public namespace; some platforms expose lightning-community or others — the user's meta files will clarify).
  • The skill ships authoritative API docs for every Lightning Base Component in references/lightning-components.md. Each component is a # Component API Structure block; grep for **Name:** <camelCaseName> (e.g. **Name:** datatable) to jump to its Properties / Methods / Events / Slots. Read this rather than relying on cached knowledge — LBC evolves and the reference is the source of truth.

Workflow

Step 1 — Read the entire component index first

Open lightning-component-index.md and scan all entries before making any selection. This is non-negotiable: LBC's value comes from picking the most specialized component, and skipping the scan leads to reinventing compound widgets out of primitives.

As you scan, compile a candidate list — every component whose description touches any aspect of the use case. Do not filter or rank yet.

Step 2 — Narrow to the most specific fit per feature

Once the scan is complete:

  • For each feature in the use case, select the most specific component that covers it. Prefer a specialized compound (lightning-record-form, lightning-tabset, lightning-datatable) over a generic primitive (lightning-input, lightning-button) when the specialized one covers the scenario end-to-end.
  • Avoid duplication: if lightning-record-form already renders fields for a record, do not pair it with lightning-input-field unless you're explicitly overriding behavior.
Step 3 — Share the shortlist and confirm

Present the final shortlist to the developer with a one-line rationale per component. Wait for explicit confirmation before pulling full API docs. This prevents the agent from burning context on components the developer has already mentally ruled out.

Step 4 — Retrieve full API docs

Once confirmed, use the bundled helper to pull the exact API blocks — this avoids ad-hoc grepping across a large reference:

bash
scripts/extract-component-docs.sh <camelCaseName> [<camelCaseName>...]

Convert lightning-<foo> tags to camelCase (no lightning- prefix):

  • lightning-datatable → datatable
  • lightning-record-edit-form → recordEditForm
  • lightning-button-icon → buttonIcon

Each returned block has the same shape: Basic Information (tag, namespace, type), Properties (name, type, default, description), Methods, Events, Slots, and (where applicable) usage notes. This skill is about picking the components; the bundled reference is about wiring them.

Step 5 — Produce integration guidance

Using the per-component reference, walk the developer through:

  • The exact <lightning-...> tag and required attributes.
  • Which events to bind (onchange, oncommit, onsuccess, …) and what the event payload contains.
  • Any slots to fill (headers, footers, custom content).
  • Known constraints from the component docs (e.g. lightning-record-form requires object-api-name and record-id for edit/view modes).
Show full SKILL.md (394 more words)Show less
Step 6 — Respect LBC styling rules

Do not override SLDS classes on LBC internals. See lbc-expert-guidance.md for specifics. Common issues:

  • Targeting .slds-button or .slds-input in the host component's CSS to restyle an LBC — LBC ships inside a shadow root, so these selectors either leak into sibling components or get stripped entirely. Use the component's documented styling hooks (--sds-c-button-*, etc.) instead.
  • Wrapping an LBC just to mutate its internal markup. You can't — the markup is hidden behind the shadow root. If the component doesn't expose the slot/prop you need, that's a platform-level gap, not a restyling job.

Examples

Example — "I need a multi-select combobox with typeahead"
  1. Scan the component index end-to-end.
  2. Candidate list includes: lightning-combobox, lightning-dual-listbox, lightning-record-picker.
  3. Shortlist: lightning-dual-listbox (the documented multi-select base component). Rule out lightning-combobox — its documented API is single-select; it has no type="multi" and no multi-select mode. Flag that lightning-record-picker only fits if the values are record IDs.
  4. Developer confirms lightning-dual-listbox.
  5. Run scripts/extract-component-docs.sh dualListbox.
  6. Return the options, value, onchange payload, and required label props from the block's Properties / Events sections.
Example — "I'm going to write my own modal"
  1. Scan finds lightning-modal, lightning-modal-body, lightning-modal-footer, lightning-modal-header.
  2. Shortlist is the 4 modal components.
  3. Confirm.
  4. Run scripts/extract-component-docs.sh modal modalHeader modalBody modalFooter → full modal API (how to extend LightningModal, the static .open() pattern, slotting the header/body/footer).
  5. Steer the developer away from rolling their own dialog.

Verification Checklist

  • The full component index was scanned before any selection (no keyword-search shortcutting).
  • Candidate list included every component that touches the use case.
  • Final shortlist selects the most specific component per feature.
  • Developer confirmed the shortlist before the bundled component reference was opened.
  • Integration guidance cites props / events / slots from the real API docs (not inferred).
  • No suggestions to restyle LBC by overriding SLDS classes.

Troubleshooting

  • Grep for **Name:** <name> returns no match — name is wrong, or the reference uses a different camelCase. Double-check against the component index (lightning-record-form → recordForm, lightning-record-view-form → recordViewForm, lightning-button-icon → buttonIcon).
  • Proposed component doesn't have the prop you expected — trust the real API doc over memory. LBC evolves; cached knowledge lies.
  • Developer resists the shortlist — don't skip Step 4. Still retrieve the docs for the developer's preferred choice so they see the actual trade-offs.
  • Developer wants to restyle LBC internals — redirect to styling hooks (see the LBC Expert reference). Refusing shadow DOM penetration is the correct answer.

© 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 4 other files (scripts, references) in skills/experience-lwc-base-components-integrate of forcedotcom/sf-skills.

  • SKILL.md
  • references/lbc-expert-guidance.md
  • references/lightning-component-index.md
  • references/lightning-components.md
  • scripts/extract-component-docs.sh

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Experience Lwc Base Components Integrate 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 Lwc Base Components Integrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Experience Lwc Base Components Integrate this skillforcedotcom/sf-skills1.1k—~2.1kAutomated safety check: PassApache-2.0
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Design SystemOhh-889/skyroc79511 repos~1.7kAutomated safety check: PassMIT
Design Dnazanwei/design-dna1.9k1 repos~2.1kAutomated safety check: PassMIT
Stitch Taste Design Systemgoogle-labs-code/stitch-skills8.4k15 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Figma Design System Builder

    warpdotdev/warp

    Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed

  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed

  • Design Dna

    zanwei/design-dna

    Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…

    1.9k GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed

  • Stitch Taste Design System

    google-labs-code/stitch-skills

    Official

    Generates a DESIGN.md design-language file for Google Stitch that encodes color, typography, layout, component behavior and motion rules to avoid generic AI-looking UI.

    8.4k GitHub starsUsed in 15 repos~3.1k tokens
    Frontend & DesignAuto-check passed

  • Scalar Design System

    scalar/scalar

    Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library.

    16k GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed

More from forcedotcom/sf-skills

All 251 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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Works with

Categories

Questions about Experience Lwc Base Components Integrate

What does Experience Lwc Base Components Integrate do?

Pick the right Lightning Base Component (lightning-) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC…. Experience Lwc Base Components Integrate is an agent skill from forcedotcom/sf-skills.css files) without breaking SLDS.

When should I use Experience Lwc Base Components Integrate?

Experience Lwc Base Components Integrate fits situations like: users say I need a Lightning modal / datatable / combobox / record form; ask which lightning- component fits a use case; want a shortlist of LBC candidates; are about to hand-roll a UI that a base component already provides.

How do I install Experience Lwc Base Components Integrate in Claude Code?

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

How do I install Experience Lwc Base Components Integrate in Codex?

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

Can I use Experience Lwc Base Components Integrate 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-lwc-base-components-integrate -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-lwc-base-components-integrate, .gemini/skills/experience-lwc-base-components-integrate, .github/skills/experience-lwc-base-components-integrate and .opencode/skills/experience-lwc-base-components-integrate in your project.

What does Experience Lwc Base Components Integrate need to run?

Going by SKILL.md and its folder, Experience Lwc Base Components Integrate needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Experience Lwc Base Components Integrate 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 Lwc Base Components Integrate 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Experience Lwc Base Components Integrate use?

Experience Lwc Base Components Integrate 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 Lwc Base Components Integrate use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 118k tokens, read only when the agent opens those files.

What are the alternatives to Experience Lwc Base Components Integrate?

Skills that share tags, products or a category with Experience Lwc Base Components Integrate: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Design System (Ohh-889/skyroc, 795 stars) and Design Dna (zanwei/design-dna, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Experience Lwc Base Components Integrate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 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.