| name | legacy-webview-analysis |
| description | Use when: analyzing Objective-C WebView legacy flows, fallback behavior, and bridge contracts before implementing changes. Read-only: produces a behavior map and a safe patch checklist, never code edits. |
Legacy WebView Analysis
Purpose
Use this skill to understand and document the real runtime behavior of the project before changing code.
Required Output
- Objective and scope
- What the app demonstrates according to README and code
- Which flow is being analyzed (WK, UI fallback, bridge, sharing)
- Runtime map
- Entry controller(s)
- Delegate chain
- Navigation/load lifecycle
- Observer interactions
- Bridge contract map
- Handler registration points
- Handler call points
- Queue protocol and JS bridge file coupling
- Risk points
- Crash risks (KVO/delegate lifecycle)
- Behavioral regressions (redirect/share/forward)
- Backward compatibility risks
- Safe patch checklist
- Minimal file touch set
- Verification strategy
- Rollback considerations
Rules
- Always cite concrete files/symbols
- Every technical claim must be verifiable in files read during this analysis
- If the information does not exist in the code, write
not found — do not fill gaps with assumptions
- No rewrite proposals by default
- No implementation in analysis-only tasks
Anti-example (do not produce)
"The bridge probably uses evaluateJavaScript under the hood, so the change should be safe."
Speculation without a citation. Either point to the exact call site in WKWebViewJavascriptBridge.m or write not found.
