agentleFS
Sign inStart free
emilianoeloiemilianoeloi/ios-WK-UI-WebView/.github/skills/webview-legacy-reference/SKILL.md

webview-legacy-reference

Skill3 starsChanged 4 months agoMITView on GitHub

Use when: documenting, teaching, or deciding WebView strategy with historical context, practical guidance, and migration paths between UIWebView and WKWebView.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when requests involve:

    line 19
  2. Distinctive:

    Use positive language for the term legacy: stable, battle-tested, and educational value

    line 35
  3. Distinctive:

    Do not treat legacy as obsolete without context

    line 36
  4. Distinctive:

    Always highlight compatibility and risk management

    line 37
  5. Distinctive:

    Keep bridge protocol semantics explicit when cited

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. historical context of UIWebView and WKWebView
  2. best practices for navigation, delegation, and bridge contracts
  3. migration strategy in legacy Objective-C codebases
  4. repository-level guidance for maintainers and learners

Required Output

  1. Explain context with historical timeline and current relevance
  2. Link recommendation to concrete references in references/
  3. Distinguish learning/demo advice from production-critical advice
  4. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free