A generator for Salesforce Lightning Web Components, which are reusable user-interface components built from JavaScript, HTML, and CSS. It also prepares the metadata and tests needed to deploy the component.

Use it to plan or generate components for Salesforce record, app, home, community, or Flow-screen pages. Depending on the data source, it can also provide an Apex controller stub and Jest tests.

It turns a component requirement into the files and supporting pieces expected by Salesforce. This reduces the need to assemble markup, data access, accessibility details, and Jest tests manually.

build-lwc — Command for Claude Code by BanibrataChatterjee

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-lwc/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-lwc)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-lwc"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-lwc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/build-lwc"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/build-lwc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 545 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00545
Opus 5.5	$0.00000	$0.00218
Sonnet 5.5	$0.00000	$0.00109
Haiku 4.5	$0.00000	$0.00055

Measured 2mo ago against content hash 3fee72764b45, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-lwc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/build-lwc.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/build-lwc — Generate a Lightning Web Component bundle

Wraps agents/lwc-builder/AGENT.md. Produces .js, .html, .css, .js-meta.xml, Jest tests, and — where applicable — the matching @AuraEnabled(cacheable=true) Apex controller stub.

Step 1 — Collect inputs

Ask the user:

1. Component name (camelCase)?

2. Purpose (3+ sentences — drives markup + reactivity decisions)?

3. Surface(s) it targets? (lightning__RecordPage | lightning__AppPage |
   lightning__HomePage | lightningCommunity__Page | lightning__FlowScreen | custom)

4. Data binding? (none | @wire getRecord | @wire imperative Apex | wire custom)

5. Exposed properties? (list of @api props with types)

6. Accessibility tier? (default: WCAG 2.1 AA)

If purpose is under 3 sentences or surface is unspecified, STOP.

Step 2 — Load the agent

Read agents/lwc-builder/AGENT.md + mandatory reads (lwc/component-patterns, lwc/accessibility, lwc/testing, security/lightning-locker-and-lws, plus templates under templates/lwc/).

Step 3 — Execute the plan

Choose base skeleton from templates/lwc/component-skeleton/.
Pick a pattern from templates/lwc/patterns/ where one fits.
Generate .js with reactive tracking, error handling, a11y hooks.
Generate .html with semantic markup.
Generate .css scoped to component.
Generate .js-meta.xml with surface targets + config.
Generate Jest tests (render, error, interaction, a11y).
If data binding uses imperative Apex, emit the matching @AuraEnabled(cacheable=true) controller stub with SecurityUtils.

Step 4 — Deliver the output

Summary + confidence
File bundle (fenced blocks, one per file)
Jest tests
Apex controller stub (if applicable) with test class
Deployment manifest
Process Observations
Citations

/audit-lwc after deploy
/scan-security on the controller Apex
/gen-tests if coverage needs deepening

Read the full file on GitHub · 74 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 74 lines · 0 tokens per session scan A 3fee72764b45

Subscribe to this mod's changes

build-lwc is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 545 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Frontend

build-lwc next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
build-lwcBanibrataChatterjee/AwesomeSalesforceSkills	Command	4	6mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code