Migrate an LWC to a widget

Use the LWC to recover the user's goal and data contract, then build the closest useful widget. A widget is its own declarative artifact. platform-widget-generate authors it; a Lightning Type renderer may need separate wiring to make it reachable. This skill owns the comparison, handoff, integration check, and honest final status.

1. Decide whether to proceed

Read and apply experience-lwc-widget-assess to the component, its action output, and any existing Lightning Type/renderer. Preserve its verdict and the key findings from its report (blockers, contract change, lost interactions) in your report; do not write the assessment's own verdict.json or report.md files. Stop on pointless, blocked, review, or needsHumanReview: true. Proceed on viable only when the intended change is explicit:

• For port-declarative, preserve the current visible fields and actions.
• For needs-IA-contract-change, identify the exact bounded output fields or pre-shaped values required. A widget against a proposed contract is a draft until the action returns that contract; do not call it working.
• For not-portable with a viable adaptation, describe the replacement UX and each lost interaction. Call it a rebuild, not a faithful port.

2. Derive the generator handoff

Trace each value the proposed widget displays to the actual or proposed action output. Before authoring, verify the action contract rather than relying only on an assessment prompt's description. Pass platform-widget-generate an ordered field shape (name, type, required), nested/list item fields, the intended tile role of each visible element, and supported terminal actions. Preserve render order and field paths. Use its discovery results for tile definitions and attributes, its documented formula catalog for expressions, and its instructions for schema types and bundle layout; do not maintain a second catalog here. A formula can cover supported scalar/date/regex operations, while collection restructuring may require pre-shaped output.

If an LWC fixture or action example contains sample data, it can help infer the shape; sample data is optional and is not a documented generator input or a substitute for the action contract. Do not invent sample fields. For an action such as sendMessage, verify that the required context reaches the agent and that the agent has a way to perform the requested work. Do not assume a widget input form can submit collected values without a discovered, validated mechanism.

3. Generate and connect