ios-WK-UI-WebView
Copilot instructions3 starsChanged 4 months agoMITView on GitHub
Copilot instructions for this legacy Objective-C iOS project focused on WKWebView/UIWebView behavior and JavaScript bridge integration.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,349 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- concise-outputSkill
- legacy-webview-analysisSkill
- legacy-webview-implementationSkill
- update-apple-webview-landscapeSkill
- webview-legacy-referenceSkill
The file
Show its rules and text
We split this copilot-instructions.md into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Keep changes minimal and localized in legacy code.
- Distinctive: line 19
Prefer Objective-C patterns already used in the project.
- Distinctive: line 20
Do not introduce SwiftUI, Combine, or large architectural rewrites unless explicitly requested.
- Distinctive: line 21
Keep public bridge APIs and protocol constants backward compatible.
- Very specific: line 26
Treat WebViewJavascriptBridge.js.txt and WebViewJavascriptBridgeBase.* as a protocol pair.
- Very specific: line 30
Keep Constants.h values centralized.
- Distinctive: line 36
Prefer focused unit tests when touching parsing, routing, or bridge message transformations.
- Distinctive: line 37
Add comments only where behavior is subtle (navigation edge cases, bridge queue logic).
- Distinctive: line 38
Keep naming stable and explicit for maintainability in an old codebase.
- Distinctive: line 42
Default tone is concise.
- Distinctive: line 47
No long summaries unless requested
- Distinctive: line 48
Keep explanations practical and code-linked
- Very specific: line 52
When the request is educational/historical or asks for best practices around Apple WebView, load skills/webview-legacy-reference/SKILL.md.
- Very specific: line 53
When the request asks for latest Apple/WebKit changes, policy updates, or browser engine scope changes, load …
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot Instructions
Project Intent
This repository is an iOS legacy playground (Objective-C, circa iOS 8/9 era) created to explore:
WKWebViewconfiguration and lifecycleUIWebViewfallback behavior- ObjC <-> JS communication using
WebViewJavascriptBridgeandWKWebViewJavascriptBridge
Primary source of truth for scope is the root README.md and existing code under ios-WK-UI-Webview/.
Workflow Rules
- Keep changes minimal and localized in legacy code.
- Prefer Objective-C patterns already used in the project.
- Do not introduce SwiftUI, Combine, or large architectural rewrites unless explicitly requested.
- Keep public bridge APIs and protocol constants backward compatible.
- Validate behavior through flow reasoning around load lifecycle and delegate callbacks.
Guardrails For This Codebase
- Treat
WebViewJavascriptBridge.js.txtandWebViewJavascriptBridgeBase.*as a protocol pair. - Preserve
wvjbschemeand queue host semantics unless migration is explicitly requested. - Be careful with observer/delegate lifecycle (avoid leaks/crashes from KVO or delegate replacement).
- Maintain fallback pathways when editing WebView controllers.
- Keep
Constants.hvalues centralized; avoid scattering literals.
Quality Baseline
- Changes should compile in Objective-C context (no mixed-language assumptions).
- The canonical build command (with the deployment-target override modern Xcode requires) lives in
AGENTS.md. - Prefer focused unit tests when touching parsing, routing, or bridge message transformations.
- Add comments only where behavior is subtle (navigation edge cases, bridge queue logic).
- Keep naming stable and explicit for maintainability in an old codebase.
Communication Efficiency
Default tone is concise.
Rules:
- Skip affirmations and filler
- Respond directly
- No long summaries unless requested
- Keep explanations practical and code-linked
For maximum token compression, load skills/concise-output/SKILL.md.
When the request is educational/historical or asks for best practices around Apple WebView, load skills/webview-legacy-reference/SKILL.md.
When the request asks for latest Apple/WebKit changes, policy updates, or browser engine scope changes, load skills/update-apple-webview-landscape/SKILL.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.