salesforce-component-standards
Quality standards for Salesforce Lightning Web Components (LWC), Aura components, and Visualforce pages.
How it works
What salesforce-component-standards does
Covers SLDS 2 compliance, accessibility (WCAG 2.1 AA), data access pattern selection, component communication rules, XSS prevention, CSRF enforcement, FLS/CRUD in AuraEnabled methods, view state management, and Jest test requirements.
Use this skill when building or reviewing any Salesforce UI component to enforce platform-specific security and quality standards.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
A finished result to review
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about salesforce-component-standards
Updated May 13, 2026.
What does salesforce-component-standards do?
Quality standards for Salesforce Lightning Web Components (LWC), Aura components, and Visualforce pages. Covers SLDS 2 compliance, accessibility (WCAG 2.1 AA), data access pattern selection, component communication rules, XSS prevention, CSRF enforcement, FLS/CRUD in AuraEnabled methods, view state management, and Jest test requirements. Use this skill when building or reviewing any Salesforce UI component to enforce platform-specific security and quality standards.
Who is salesforce-component-standards for?
It is designed for teams that want to hand off recurring work and review the result before it is used.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does salesforce-component-standards produce?
A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.
How much does salesforce-component-standards cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmoq1cvp402ea…
- May 13, 2026
- 1 signal
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Connections
Where salesforce-component-standards fits
Similar skills5
benchmark-optimization-loop
Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.FreeSkill · Marketingcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.FreeSkill · Product and engineeringdiagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.FreeSkill · Product and engineeringGitNexus Impact Analysis
Assess the likely consequences of a proposed or local code change with GitNexus graph evidence, then verify the result against the exact repository. Use for dependency tracing, blast-radius analysis, regression planning, and deciding whether a shared symbol is safe to change.FreeSkill · Product and engineeringintent-driven-development
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions are already clear unless the user explicitly invokes this skill.FreeHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.