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-values-expert.md
View on GitHub## 💎 Values Expert Analysis Framework
### Analysis Focus
Analyze default values, configuration patterns, and value initialization in the Aura component.
### Key Areas to Review
#### 1. Default Value Analysis
- Document all attribute default values and their significance
- Identify initialization patterns and timing requirements
- Note any computed default values or dynamic initialization
- Check for environment-specific default value variations
#### 2. Configuration Management
- Analyze configuration attribute patterns and their usage
- Document how configuration values affect component behavior
- Identify any configuration validation or constraint patterns
- Note any hierarchical configuration inheritance
#### 3. Value Validation and Constraints
- Document any validation logic for attribute values
- Identify data type constraints and format requirements
- Note any business rule validation patterns
- Check for error handling of invalid values
#### 4. Value Transformation
- Analyze any value formatting or transformation logic
- Document currency, date, or number formatting patterns
- Identify any localization-specific value handling
- Note any value normalization or sanitization
### Migration Considerations
- Aura default values need equivalent LWC property initialization
- Configuration patterns may need LWC-specific approaches
- Validation logic needs to be migrated to LWC methods
- Value transformation may require different utility approaches
### Additional knowledge
#### Default Values analysis
Your task is to make sure that default values of Aura attributes are assigned to JavaScript properties of LWC component.
Review Aura component above and add default value of the attribute to the "what" property:
1. If default value is a constant, add its type and value even if the value is empty string or null.
For example for <aura:attribute name="index" type="String" default="0">
"""
"name": "index",
"what": "The index of the row being edited. Default value is string \"0\"."
"""
2. If default value points to a static resource, infer namespace and name of the resource, not its value.
For example for <aura:attribute name="label" default="{!$Label.myOrg.myLabelName}">, default value should be mentioned like so:
"""
"name": "label",
"what": "The label next to input. Default value is a label from namespace \"myOrg\" with the name \"myLabelName\"".
"""
- 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 |