Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Lwc

  • 1.5k installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/sf-skills

When and how to build Lightning Web Components with wire service, data integration, SLDS 2 styling, accessibility, and Jest tests.

About

sf-lwc guides developers through Lightning Web Component creation using the PICKLES methodology (prototype, integrate, compose, define, libraries, execute, security). Covers component scaffolding, data access patterns (LDS, Apex, GraphQL), SLDS 2 and dark mode compliance, accessibility, performance optimization, and Jest unit testing. Developers use this skill when touching lwc/**/*.js, .html, .css, or .js-meta.xml files, integrating wire service or Apex, or reviewing component quality. Includes local dev server commands for hot-reload preview without deployment. Delegates Apex backend work to sf-apex, Flow orchestration to sf-flow, and org deployment to sf-deploy.

  • PICKLES methodology: prototype, integrate, compose, define, libraries, execute, security framework
  • Data access patterns: LDS, Apex @AuraEnabled(cacheable=true), GraphQL wire adapter, Lightning Message Service
  • 165-point scoring system across 8 categories including SLDS 2 and dark mode compliance
  • Local dev preview with hot reload for .js, .html, .css changes without deployment
  • Jest testing, accessibility audit, performance rerender safety, and event contract validation

Sf Lwc by the numbers

  • 1,457 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #297 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

sf-lwc capabilities & compatibility

Capabilities
component scaffolding and bundle design · wire service and apex integration · graphql data fetching · slds 2 and dark mode styling · jest unit testing · accessibility audit · local dev preview with hot reload
Works with
salesforce
Use cases
frontend · testing · api development
Platforms
macOS · Windows · Linux
Runs
Hosted SaaS
Pricing
Free
npx skills add https://github.com/jaganpro/sf-skills --skill sf-lwc

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.5k
repo stars423
Security audit3 / 3 scanners passed
Last updatedApril 27, 2026
Repositoryjaganpro/sf-skills

What it does

Build Lightning Web Components with wire service integration, SLDS 2 styling, and Jest tests for Salesforce orgs.

Who is it for?

Frontend developers building interactive UI components, data-driven dashboards, Flow screen components, and Experience Cloud embeds in Salesforce.

Skip if: Apex business logic, Flow declarative logic, metadata deployment, or Aura/Visualforce component migration.

When should I use this skill?

User creates/edits lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, Jest LWC tests, or component architecture.

What you get

Component achieves 150+ point score (production-ready) with SLDS 2 compliance, dark mode support, accessibility audit pass, and Jest coverage.

  • LWC bundle (JS, HTML, CSS, JS-meta.xml)
  • Jest test suite with coverage
  • Accessibility audit notes

By the numbers

  • 165-point scoring system across 8 categories
  • Production-ready threshold: 150+ points
  • Local dev commands support hot reload for .js, .html, .css files

Files

SKILL.mdMarkdownGitHub ↗

sf-lwc: Lightning Web Components Development

Use this skill when the user needs Lightning Web Components: LWC bundles, wire patterns, Apex/GraphQL integration, SLDS 2 styling, accessibility, performance work, or Jest unit tests.

When This Skill Owns the Task

Use sf-lwc when the work involves:

  • lwc/**/*.js, .html, .css, .js-meta.xml
  • component scaffolding and bundle design
  • wire service, Apex integration, GraphQL integration
  • SLDS 2, dark mode, and accessibility work
  • Jest unit tests for LWC

Delegate elsewhere when the user is:

  • writing Apex controllers or business logic first → sf-apex
  • building Flow XML rather than an LWC screen component → sf-flow
  • deploying metadata → sf-deploy

---

Required Context to Gather First

Ask for or infer:

  • component purpose and target surface
  • data source: LDS, Apex, GraphQL, LMS, or external system via Apex
  • whether the user needs tests
  • whether the component must run in Flow, App Builder, Experience Cloud, or dashboard contexts
  • accessibility and styling expectations

---

Recommended Workflow

1. Choose the right architecture

Use the PICKLES mindset:

  • prototype
  • integrate the right data source
  • compose component boundaries
  • define interaction model
  • use platform libraries
  • optimize execution
  • enforce security

2. Choose the right data access pattern

NeedDefault pattern
single-record UILDS / getRecord
simple CRUD formbase record form components
complex server queryApex @AuraEnabled(cacheable=true)
related graph dataGraphQL wire adapter
cross-DOM communicationLightning Message Service

3. Start from an asset when useful

Use provided assets for:

  • basic component bundles
  • datatables
  • modal patterns
  • Flow screen components
  • GraphQL components
  • LMS message channels
  • Jest tests
  • TypeScript-enabled components

4. Validate for frontend quality

Check:

  • accessibility
  • SLDS 2 / dark mode compliance
  • event contracts
  • performance / rerender safety
  • Jest coverage when required

5. Hand off supporting backend or deploy work

Use:

  • sf-apex for controllers / services
  • sf-deploy for deployment
  • sf-testing only for Apex-side test loops, not Jest

---

High-Signal Rules

  • prefer platform base components over reinventing controls
  • use @wire for reactive read-only use cases; imperative calls for explicit actions and DML paths
  • do not introduce inaccessible custom UI
  • avoid hardcoded colors; use SLDS 2-compatible styling hooks / variables
  • avoid rerender loops in renderedCallback()
  • keep component communication patterns explicit and minimal

---

Output Format

When finishing, report in this order: 1. Component(s) created or updated 2. Data access pattern chosen 3. Files changed 4. Accessibility / styling / testing notes 5. Next implementation or deploy step

Suggested shape:

LWC work: <summary>
Pattern: <wire / apex / graphql / lms / flow-screen>
Files: <paths>
Quality: <a11y, SLDS2, dark mode, Jest>
Next step: <deploy, add controller, or run tests>

---

Local Development Server

Preview LWC components locally with hot reload — no deployment needed:

# Preview LWC components in isolation
sf lightning dev component --target-org <alias>

# Preview a Lightning Experience app locally
sf lightning dev app --target-org <alias>

# Preview an Experience Cloud site locally
sf lightning dev site --target-org <alias>

In current SF CLI releases, these Local Dev commands are installed just-in-time the first time you run them. They are long-running processes that open a browser with live preview. Changes to .js, .html, and .css files auto-reload instantly. Requires an active org connection for data and Apex callouts.

---

Cross-Skill Integration

NeedDelegate toReason
Apex controller or servicesf-apexbackend logic
embed in Flow screenssf-flowdeclarative orchestration
deploy component bundlesf-deployorg rollout
create metadata like message channelssf-metadatasupporting metadata

---

Reference Map

Start here

  • references/component-patterns.md
  • references/slds-design-guide.md
  • references/lwc-best-practices.md
  • references/scoring-and-testing.md
  • references/jest-testing.md

Accessibility / performance / state

  • references/accessibility-guide.md
  • references/performance-guide.md
  • references/state-management.md
  • references/template-anti-patterns.md

Integration / advanced features

  • references/lms-guide.md
  • references/flow-integration-guide.md
  • references/advanced-features.md
  • references/async-notification-patterns.md
  • references/triangle-pattern.md
  • assets/

---

Score Guide

ScoreMeaning
150+production-ready LWC bundle
125–149strong component with minor polish left
100–124functional but review recommended
< 100needs significant improvement

Related skills

Forks & variants (1)

Sf Lwc has 1 known copy in the catalog totaling 36 installs. They canonicalize to this original listing.

How it compares

Choose sf-lwc over generic Apex snippets when the target consumer is Lightning Web Components using @wire and @AuraEnabled rather than REST or batch Apex jobs.

FAQ

When should I use @wire vs. imperative Apex calls?

Use @wire for reactive read-only use cases and data subscriptions; use imperative calls for explicit actions and DML operations where control flow matters.

What is the PICKLES methodology?

PICKLES: Prototype, Integrate data source, Compose boundaries, define interaction model, use Libraries, optimize Execution, enforce Security.

What score should my LWC component reach?

Aim for 150+ (production-ready); 125-149 is strong with minor polish; <100 needs significant improvement across 8 categories.

Is Sf Lwc safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Frontend Developmentfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.