agentleFS
Sign inStart free
emilianoeloiemilianoeloi/ios-WK-UI-WebView/.github/skills/update-apple-webview-landscape/SKILL.md

update-apple-webview-landscape

Skill3 starsChanged 4 months agoMITView on GitHub

Use when: checking official Apple/WebKit updates and keeping this repository references current about WebView, browser engines, and compatibility boundaries.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep repository references current with official changes in Apple WebView and browser engine policies.

    line 10
  2. Distinctive:

    after WWDC, Safari, or WebKit release waves

    line 14
  3. Distinctive:

    when README/reference docs need refresh

    line 15
  4. Distinctive:

    when deciding if a new platform capability changes maintenance strategy

    line 16
  5. Distinctive:

    Prefer Apple Developer and WebKit official sources

    line 27
  6. Distinctive:

    Never generalize EU-only policy to global behavior

    line 29
  7. Very specific:

    If official sources do not confirm a change, write not confirmed — do not extrapolate from secondary coverage

    line 32

≈ “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

Update Apple WebView Landscape

Purpose

Keep repository references current with official changes in Apple WebView and browser engine policies.

When To Use

  1. after WWDC, Safari, or WebKit release waves
  2. when README/reference docs need refresh
  3. when deciding if a new platform capability changes maintenance strategy

Required Output

  1. What changed (official source and date)
  2. Scope boundaries (where it applies and where it does not)
  3. Impact on this repository (none, low, medium, high)
  4. Recommended docs/skills updates

Verification Rules

  • Prefer Apple Developer and WebKit official sources
  • Explicitly distinguish WKWebView API updates vs browser-engine policy updates
  • Never generalize EU-only policy to global behavior
  • Include at least one source URL for each important claim
  • Stamp every landscape claim with an explicit "as of <month year>" so future refreshes can tell what is stale
  • If official sources do not confirm a change, write not confirmed — do not extrapolate from secondary coverage

Source Priority

  1. Apple Developer documentation/support pages
  2. WebKit Blog release notes and feature posts
  3. Official vendor docs for agent tooling references

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