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-style-expert.md
View on GitHub## 🎨 Style Expert Analysis Framework
### Analysis Focus
Analyze styling patterns, CSS architecture, and design token usage in the Aura component.
### Key Areas to Review
#### 1. CSS File Analysis
- Document all CSS classes and their purposes
- Identify SLDS (Salesforce Lightning Design System) usage patterns
- Note any custom CSS that may conflict with LWC styling
- Check for responsive design patterns and media queries
#### 2. Styling Token Usage
- Look for design token references and their usage
- Document theme customization patterns
- Identify brand-specific styling requirements
- Note any dynamic styling based on component state
#### 3. CSS Encapsulation Patterns
- Analyze CSS scoping and inheritance patterns
- Document any global CSS dependencies
- Identify component-specific styling isolation
- Note potential CSS conflicts or specificity issues
#### 4. Dynamic Styling
- Find any JavaScript-based style manipulation
- Document conditional styling based on component state
- Identify user preference or theme switching patterns
- Note any performance-critical styling operations
### Migration Considerations
- Aura CSS files become LWC CSS modules with different scoping
- SLDS usage patterns may need updates for LWC compatibility
- CSS custom properties and design tokens have different APIs
- Shadow DOM styling requires different approaches
- Global CSS access is more restricted in LWC
### Additional knowledge
#### Style Intent analysis
Your task is to look at the Aura Component definition, and make sure that the blueprint only describes the experiences a user may have with a component.
Developers often accidentially expose APIs that allow customization of styles or CSS classes.
Review Aura component above and fix its blueprint using following rules:
1. Look for the following patterns: an attribute name that suggests it may be used for passing styles or CSS class names.
2. For each match found, reason about the intent around the reference. Why is the style being provided and what is it used for in the component?
3. Review existing sections in the blueprint, and propose updates if necessary.
- If something appears in the 'styling' section already, verify it doesn't appear the data section.
- If something appears in both sections, the dataRequirements section should be updated to remove it.
* 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 |