33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
---
|
|
name: swiftui-xflow-review
|
|
description: Review or reason about SwiftUI code in XFlow/Fidelity contexts, especially lifecycle, modal presentation, navigation, backend-driven UI, and UIKit bridge removal.
|
|
trigger: always_on
|
|
glob: ""
|
|
---
|
|
|
|
## When To Use
|
|
|
|
Use this skill when a SwiftUI question touches XFlow, Fid4, XFlowViewMaker, modal presentation, dismissal sequencing, navigation, `UIHostingController`, or backend-driven UI behavior.
|
|
|
|
## Review Heuristics
|
|
|
|
- Check whether behavior is driven by backend configuration before blaming local SwiftUI code.
|
|
- Identify data ownership and view lifecycle boundaries.
|
|
- Treat dismissal sequencing as high risk when delegate callbacks, `onDisappear`, or upstream state changes are involved.
|
|
- Treat UIKit bridge removal as rollout-sensitive, not just cleanup.
|
|
- Separate SwiftUI best practice from Fidelity-safe migration strategy.
|
|
|
|
## Fidelity-Specific Checks
|
|
|
|
- Does the change preserve UIKit/SwiftUI parity?
|
|
- Does it require a feature flag?
|
|
- Does it need validation in Fid4 or only XFlowSDK?
|
|
- Could XFlowViewMaker or FTFrameworks block consumer visibility?
|
|
- Is the issue external behavior, existing behavior, or a regression?
|
|
|
|
## Output Rules
|
|
|
|
- Provide a clear recommendation.
|
|
- Include risks and validation path.
|
|
- Avoid recommending a pure SwiftUI approach without noting rollout and consumer validation impact.
|