Webview legacy reference
Skill emilianoeloi/ios-WK-UI-WebView/.github/skills/webview-legacy-reference
🦖 The COBOL of Apple: a battle-tested Objective-C UIWebView/WKWebView legacy lab — lovingly maintained, and teaching AI agents to respect their elders
npx -y skills add emilianoeloi/ios-WK-UI-WebView --skill webview-legacy-referenceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: documenting, teaching, or deciding WebView strategy with historical context, practical guidance, and migration paths between UIWebView and WKWebView.
SKILL.md
1.6 KB, as published. Nobody here has run it
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 itnot in referencesand 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