| name | webview-legacy-reference |
| description | Use when: documenting, teaching, or deciding WebView strategy with historical context, practical guidance, and migration paths between UIWebView and WKWebView. |
WebView Legacy Reference
Purpose
Turn this repository into a practical knowledge base for Apple WebView legacy topics with positive framing:
- historical evolution
- practical usage patterns
- migration decision support
- safe maintenance guidance
When To Use
Use this skill when requests involve:
- historical context of UIWebView and WKWebView
- best practices for navigation, delegation, and bridge contracts
- migration strategy in legacy Objective-C codebases
- repository-level guidance for maintainers and learners
Required Output
- Explain context with historical timeline and current relevance
- Link recommendation to concrete references in
references/
- Distinguish learning/demo advice from production-critical advice
- Provide safe next steps for this repository architecture
Rules
- Use positive language for the term legacy: stable, battle-tested, and educational value
- Do not treat legacy as obsolete without context
- Always highlight compatibility and risk management
- Keep bridge protocol semantics explicit when cited
- Ground historical and behavioral claims in the files under
references/; if a claim is not covered there, mark it not in references and cite an official Apple/WebKit source instead of asserting it from memory
Reference Index
- references/uiwebview.md
- references/wkwebview.md
- references/webview-javascript-bridge.md
- references/migration-playbook.md
