forcedotcom/sf-skills / plugins/builder/experience-lwc/skills/experience-aura-lwc-migrate
experience-aura-lwc-migrate
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.6 KB |
| references/aura-api-expert.md | markdown | 8.4 KB |
| references/aura-data-expert.md | markdown | 12.7 KB |
| references/aura-migration-guidelines.md | markdown | 8.2 KB |
| references/aura-prd-framework.md | markdown | 3.7 KB |
| references/aura-redundant-code-expert.md | markdown | 1.5 KB |
| references/aura-reference-expert.md | markdown | 9.3 KB |
| references/aura-resolver-expert.md | markdown | 5.8 KB |
| references/aura-slots-expert.md | markdown | 3.1 KB |
| references/aura-style-expert.md | markdown | 2.4 KB |
| references/aura-to-lwc-completeness-checklist.md | markdown | 7.9 KB |
| references/aura-values-expert.md | markdown | 2.5 KB |
references/aura-slots-expert.md
View on GitHub## 🎰 Slots Expert Analysis Framework
### Analysis Focus
Analyze component composition patterns, content projection, and child component integration in the Aura component.
### Key Areas to Review
#### 1. Aura Facet Analysis
- Look for `<aura:facet>` declarations and usage
- Document how facets are used for content projection
- Identify dynamic facet content and conditional rendering
- Note any nested facet patterns or complex compositions
#### 2. Body Content Patterns
- Analyze `{!v.body}` usage for content projection
- Document how child components are composed
- Identify conditional rendering of body content
- Note any iteration patterns over child elements
#### 3. Component Composition
- Find all child components and their content patterns
- Document how content is passed to child components
- Identify any wrapper or container component patterns
- Note any dynamic component creation or destruction
#### 4. Content Distribution
- Analyze how different content types are distributed
- Document named slots vs default content patterns
- Identify any content transformation or filtering
- Note accessibility considerations for content structure
### Migration Considerations
#### Default Slot Analysis
Your task is to identify a placeholder for an anonymous block of markup that translates into a default slot in LWC.
Named slots or other elements and attributes are not part of this analysis and will be covered separately.
In Aura an anonymous block of markup is injected using the expression "{!v.body}" or "{#v.body}".
Review Aura component above and fix its blueprint using following rules:
1. Every occurance of the expression "{!v.body}" or "{#v.body}" should be present as an element in the "contentRequirements" section.
2. If such element has already been added, do not add another one but update one that has been added by adding "default slot" in "what" section.
3. LWC components can have only one default slot, so it's crucial to include conditions under which this fragment is present in "what".
- For each issue found, provide a separate, detailed report.
- Keep issues concise, avoid duplicated issues or unnecessary or non-applicable problems.
#### Named Slot Analysis
In Aura, placeholders for blocks of markup are added by declaring attributes with type "Aura.Component" or "Aura.Component[]" for one or more component instances.
Such placeholders are similar to slots in LWC web components.
Review Aura component above and fix its blueprint using following rules:
1. Every `<aura:attribute>` with type "Aura.Component" or "Aura.Component[]" should be added as an element in the "contentRequirements" section.
2. Only elements for `<aura:attribute>` with type "Aura.Component" or "Aura.Component[]" can be added as part of this review. Ignore all other elements.
3. The "name" of the included element should be set to the name of the attribute.
4. The "what" of the included element should be set to "named slot inside <name of other existing item inside contentRequirements or root>".
- For each issue found, provide a separate, detailed report.
- Keep issues concise, avoid duplicated issues or unnecessary or non-applicable problems.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |