sf-lwc-constraints

To enforce Lightning Web Components naming conventions, you validate LWC folders, JS controllers, and HTML templates against explicit rules. This prevents defects early by cataloging 'Always Do' practices and anti-patterns for compliant component authoring.

The best way to check LWC accessibility and security is to validate the component artifacts against codified governance rules. This process catalogs explicit constraints and provides guardrails to catch accessibility and security violations during authoring.

You validate Salesforce LWC performance best practices by applying governance constraints to your component folders, HTML templates, JS controllers, and CSS. This identifies common anti-patterns early and enforces required performance rules across the project.

Yes, this LWC governance approach works for both authoring and review. It applies validation rules across all Lightning Web Component artifacts, providing tooling integration guardrails to ensure quality throughout the entire development lifecycle.

Common anti-patterns to avoid when creating Lightning Web Components include non-compliant naming structures, missing accessibility guidelines, and security vulnerabilities. The constraints catalog these explicitly to provide recommended practices and prevent defects.

You need explicit constraints for LWC development to meet Salesforce project governance requirements. Cataloging naming, security, accessibility, and performance rules provides clear guardrails that prevent defects early and standardize component quality.