locker-lwr-compat

Detect Locker and LWR runtime compatibility issues in Lightning Web Components.

4|Updated May 6, 2026
One-click install
npx skills add https://github.com/tucario/Tucario-LWC-Toolkit --skill locker-lwr-compat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: locker-lwr-compat
Source: https://github.com/tucario/Tucario-LWC-Toolkit/tree/main/.claude/skills/locker-lwr-compat
Command: npx skills add https://github.com/tucario/Tucario-LWC-Toolkit --skill locker-lwr-compat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patterns that work in LWR but break or get sandbox-rejected in Lightning Locker can silently cause customer failures. This skill helps teams detect and flag such issues before release.

Core Features & Use Cases

  • Flag common Locker-incompatible patterns to prevent runtime failures in subscriber orgs.
  • Distinguish between BLOCKER, HIGH, and INFORMATIONAL patterns and provide guidance for remediation.
  • Run runtime-detection with a developer workflow to ensure cross-runtime compatibility across LWR, LWS, and Locker.

Quick Start

Run /locker-check to scan your LWC codebase for Locker/LWR compatibility issues and generate a remediation report.

Frequently Asked Questions about locker-lwr-compat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my LWC codebase for Locker and LWR compatibility issues?

To check for Locker and LWR compatibility issues, scan your LWC codebase to identify known runtime conflicts and generate a report with recommended fixes. This detects patterns that break or get sandbox-rejected in Lightning Locker before release.

Why does my Lightning Web Component work in LWR but fail in Locker?

Lightning Web Components fail in Locker because certain patterns work in LWR but get sandbox-rejected by Locker's runtime restrictions. Detecting these incompatible patterns early prevents silent customer failures in subscriber orgs.

How do I prevent AppExchange LWC runtime failures in subscriber orgs?

Prevent AppExchange LWC runtime failures by running cross-runtime compatibility checks during development and testing. This flags Locker-incompatible patterns and provides remediation guidance to ensure code works across LWR, LWS, and Locker.

Can I detect Lightning Locker compatibility issues during my development workflow?

Yes, you can detect Lightning Locker compatibility issues during your development workflow by running runtime-detection scans. This ensures cross-runtime compatibility across LWR, LWS, and Locker before entering release workflows.

What severity levels are assigned to Locker and LWR compatibility conflicts?

Locker and LWR compatibility conflicts are categorized as BLOCKER, HIGH, or INFORMATIONAL severity levels. This distinction helps teams prioritize remediation guidance for incompatible patterns found in Lightning Web Components.

What are the limitations of automated Locker and LWR compatibility scanning?

Automated Locker and LWR compatibility scanning focuses on detecting known patterns rather than executing runtime behavior. It applies to AppExchange-targeted code and developer orgs using LWR, LWS, or Locker during development, testing, and release workflows.