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

Generating Lwc Components

  • 541 installs
  • 787 repo stars
  • Updated August 5, 2026
  • forcedotcom/afv-library

This is a copy of generating-lwc-components by forcedotcom - installs and ranking accrue to the original listing.

generating-lwc-components is a Salesforce frontend skill that generates, edits, and tests Lightning Web Components using the PICKLES methodology and a 165-point scoring rubric for developers working on LWC bundles, wire

About

generating-lwc-components is a forcedotcom afv-library skill at version 1.1 that guides Lightning Web Components development using the PICKLES methodology and a 165-point quality scoring system. The skill triggers when developers create or edit files under lwc/**/*.js, .html, .css, or .js-meta.xml, or ask about wire service patterns, SLDS styling, Apex and GraphQL integration, and Jest LWC tests. It explicitly excludes Apex-only, Aura, and Visualforce work. Developers reach for generating-lwc-components when building Salesforce UI features that need platform best practices baked into component structure, data wiring, and test coverage. The scoring rubric gives concrete quality checkpoints beyond generic React-style component advice.

  • Applies the PICKLES methodology with a 165-point scoring system for every LWC component
  • Handles LWC bundles, wire service patterns, Apex and GraphQL integration, SLDS 2 styling, accessibility, performance, an
  • Triggers automatically on edits to lwc/**/*.js, .html, .css, or .js-meta.xml files
  • Delegates Apex logic to generating-apex and metadata deployment to deploying-metadata
  • Ensures consistent SLDS 2, dark mode, accessibility, and Jest test quality

Generating Lwc Components by the numbers

  • 541 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/forcedotcom/afv-library --skill generating-lwc-components

Add your badge

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

Listed on Skillselion
Installs541
repo stars787
Last updatedAugust 5, 2026
Repositoryforcedotcom/afv-library

How do you build Salesforce LWC components with tests?

Generate, edit, and test Lightning Web Components following Salesforce best practices.

Who is it for?

Salesforce developers creating or editing Lightning Web Components who want PICKLES-guided patterns and scored quality checks.

Skip if: Apex-only backend work, Aura components, or Visualforce pages outside the LWC stack.

When should I use this skill?

Developer edits lwc/**/*.js, .html, .css, .js-meta.xml or asks about wire service, SLDS, or Jest LWC tests.

What you get

LWC bundles (.js, .html, .css, .js-meta.xml), wire service implementations, and Jest LWC test files.

  • LWC component bundles
  • Jest test files

By the numbers

  • 165-point PICKLES quality scoring rubric
  • Skill version 1.1 in forcedotcom/afv-library

Files

SKILL.mdMarkdownGitHub ↗

generating-lwc-components: 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 generating-lwc-components 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 → generating-apex
  • building Flow XML rather than an LWC screen component → generating-flow
  • deploying metadata → deploying-metadata

---

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:

  • generating-apex for controllers / services
  • deploying-metadata for deployment
  • running-apex-tests 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. Run the commands in scripts/local-dev-preview.sh to start a local dev session for a component, app, or Experience Cloud site.

Local Dev commands install just-in-time on first run. 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 servicegenerating-apexbackend logic
embed in Flow screensgenerating-flowdeclarative orchestration
deploy component bundledeploying-metadataorg rollout
create supporting metadata (message channels, objects)deploying-metadatametadata deployment

---

Reference File Index

Start here

  • references/component-patterns.md — component architecture patterns and bundle design
  • references/slds-design-guide.md — SLDS 2 styling, dark mode, CSS hooks
  • references/lwc-best-practices.md — high-signal rules and anti-patterns
  • references/scoring-and-testing.md — 165-point scoring rubric across 8 categories
  • references/jest-testing.md — Jest unit test patterns and async rendering helpers
  • references/slds-blueprints.json — machine-readable SLDS component blueprints
  • references/cli-commands.md — SF CLI commands for LWC development

Accessibility / performance / state

  • references/accessibility-guide.md — WCAG, ARIA, keyboard navigation patterns
  • references/performance-guide.md — lazy loading, debouncing, rerender safety
  • references/state-management.md — reactive state patterns and LMS
  • references/template-anti-patterns.md — common HTML template mistakes to avoid

Integration / advanced features

  • references/lms-guide.md — Lightning Message Service patterns
  • references/flow-integration-guide.md — Flow screen component design
  • references/advanced-features.md — Spring '26 features: TypeScript, lwc:on, GraphQL mutations
  • references/async-notification-patterns.md — toast, notifications, async flows
  • references/triangle-pattern.md — parent-child-sibling communication triangle

Asset templates

  • assets/basic-component/basicComponent.js — wire service, error/loading states, event dispatching
  • assets/datatable-component/datatableComponent.js — datatable with inline editing
  • assets/flow-screen-component/flowScreenComponent.js — Flow screen with input/output properties
  • assets/form-component/formComponent.js — form validation and DML patterns
  • assets/graphql-component/graphqlComponent.js — GraphQL wire adapter with cursor-based pagination
  • assets/jest-test/componentName.test.js.example — Jest test template (copy and rename, remove .example suffix)
  • assets/message-channel/lmsPublisher.js — LMS publisher pattern
  • assets/message-channel/lmsSubscriber.js — LMS subscriber pattern
  • assets/modal-component/modalComponent.js — modal with focus trap and ESC handling
  • assets/record-picker/recordPicker.js — record picker with search
  • assets/state-store/store.js — reactive state store for cross-component state
  • assets/typescript-component/typescriptComponent.ts — TypeScript-enabled component (Spring '26)
  • assets/workspace-api/workspaceComponent.js — workspace API for tab and focus management
  • assets/apex-controller/LwcController.cls — Apex controller with @AuraEnabled(cacheable=true) patterns

Scripts

  • scripts/local-dev-preview.sh — local dev server commands for component, app, and site preview

---

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

How it compares

Use generating-lwc-components for LWC UI work; switch to generating-apex when the task is Apex classes only.

FAQ

What files trigger generating-lwc-components?

generating-lwc-components triggers on lwc/**/*.js, .html, .css, and .js-meta.xml edits plus wire service, SLDS, or Jest LWC questions. Apex classes, Aura components, and Visualforce pages should use their dedicated Salesforce skills instead.

What is the PICKLES 165-point scoring system?

generating-lwc-components applies the PICKLES methodology with a 165-point scoring rubric to evaluate LWC bundle quality. The score covers structure, wiring, styling, testing, and Salesforce platform best practices beyond generic component patterns.

Frontend Developmentfrontendintegrations

This week in AI coding

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

unsubscribe anytime.