sf-lwc-experience

Architect external-facing Experience Cloud front-ends using Lightning Web Components.

15|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-lwc-experience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-lwc-experience
Source: https://github.com/sfdc-brendan/Demo-Lab/tree/main/skills/sf-lwc-experience
Command: npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-lwc-experience

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architect external-facing Lightning Web Components for Experience Cloud sites with branding, guest-user security, and SEO considerations, enabling public users to access branded experiences without compromising data safety.

Core Features & Use Cases

  • Theme token consumption and brand customization for Experience Cloud sites.
  • Guest-user aware components that gracefully handle unauthenticated access.
  • Navigation patterns and Experience Builder configuration for public portals.
  • SEO-friendly markup and accessible design patterns for external audiences.

Quick Start

Create an Experience Cloud–ready LWC suite and configure a guest-friendly theme, navigation, and metadata to publish your first external site.

Frequently Asked Questions about sf-lwc-experience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build Lightning Web Components for Experience Cloud external sites?

Build Experience Cloud LWC by applying branding overrides, integrating theme tokens, and configuring guest-user security. Design components for public portals using Experience Builder configuration, ensuring accessible navigation and SEO-friendly markup for unauthenticated external audiences.

How do I secure guest-user data access in Experience Cloud LWC?

Secure guest-user access by designing Lightning Web Components that gracefully handle unauthenticated requests. Implement guest-user aware components in Experience Cloud to expose public data safely without compromising internal records or violating org-wide security policies.

What is the best way to apply branding overrides to Experience Cloud LWC?

Apply branding overrides to Experience Cloud LWC by consuming DX theme tokens within your components. This architectural approach ensures brand customization dynamically cascades across external-facing sites without hardcoding style values in individual Lightning Web Components.

How do I make Experience Cloud LWC navigation SEO-friendly?

Make Experience Cloud LWC navigation SEO-friendly by implementing accessible design patterns and proper semantic markup. Configure Experience Builder navigation for public portals to ensure search engines can crawl external-facing site links and index unauthenticated guest-user content effectively.

Does Experience Builder support custom Lightning Web Components for guest users?

Experience Builder supports custom Lightning Web Components for guest users by allowing configuration of guest-accessible sites. You can architect external-facing front-ends using LWC, applying theme integration and accessible navigation patterns specifically for unauthenticated public audiences.

Why are my custom LWC theme tokens not applying on my external Experience Cloud site?

Custom LWC theme tokens fail to apply on external Experience Cloud sites when branding overrides or DX token configurations are mismatched. Ensure your Lightning Web Components correctly consume the theme integration metadata defined within the Experience Builder configuration for guest-accessible portals.