Individual skill
experience-aura-lwc-migrate
Use this skill to analyze a Salesforce Aura component bundle (.cmp, .app, .evt, .intf, Controller.js, Helper.js, Renderer.js) and produce a framework-agnostic migration blueprint (PRD.yaml / PRD.md / PRD.json) capturing public API, data requirements, slots, events, states, accessibility, styling, localization, and security posture. This is Phase 1 (analysis + PRD) only — it does NOT author or edit component code, wire adapters, or Jest tests, and does not write .html/.js/.css/.js-meta.xml. TRIGGER when the user says "analyze this Aura component", "migrate Aura", "convert .cmp", "produce a migration blueprint", "generate a PRD for this Aura component", or mentions aura:attribute, aura:handler, force:recordData, $Label, $Resource, component.get, cmp.find, or an input directory containing .cmp files. DO NOT TRIGGER when there is no Aura source (delegate downstream LWC authoring to experience-lwc-generate), for post-migration scoring, or for refactoring an existing modern component.
plugins/builder/experience-lwc/skills/experience-aura-lwc-migrate/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,934 bytesSKILL.mdcore · 13,934 bytesSKILL.mdcore · 13,934 bytesSKILL.mdcore · 13,934 bytesreferences/aura-api-expert.mddoc · 8,581 bytesreferences/aura-data-expert.mddoc · 12,986 bytesreferences/aura-migration-guidelines.mddoc · 8,424 bytesreferences/aura-prd-framework.mddoc · 3,799 bytesreferences/aura-redundant-code-expert.mddoc · 1,566 bytesreferences/aura-reference-expert.mddoc · 9,558 bytesreferences/aura-resolver-expert.mddoc · 5,945 bytesreferences/aura-slots-expert.mddoc · 3,192 bytesreferences/aura-style-expert.mddoc · 2,504 bytesreferences/aura-to-lwc-completeness-checklist.mddoc · 8,071 bytesreferences/aura-values-expert.mddoc · 2,588 bytes
Read excerpt
<!-- adk-managed-skill -->
# Migrating Aura to LWC
Migrate an existing Salesforce Aura component bundle to a Lightning Web Component using a PRD-driven workflow. The Aura source is analyzed through eight expert lenses (static references, data, API surface, slots, styling, default values, unknown dependencies, redundant-code cleanup) to produce a framework-agnostic PRD, which is handed to the LWC authoring skills and verified against the Aura→LWC completeness checklist.
## When to Use
- Porting an Aura bundle (`.cmp`, `.controller.js`, `.helper.js`, `.renderer.js`, `.css`, `.design`, `.evt`, `.intf`) to LWC.
- Producing a framework-agnostic PRD from Aura source so a sibling team can implement the LWC equivalent.
- Auditing an Aura component for patterns that need explicit mapping before LWC conversion (facets, `aura:id` DOM access, `force:recordData`, application events).
Do NOT use this skill for:
- Authoring a brand-new LWC from a Figma or PRD with no Aura source (delegate to `experience-lwc-generate`).
- Refactoring an existing LWC (delegate to `experience-lwc-generate`).