Index of every page on this site: llms.txt
All skills
avdlee avatar

/update-swiftui-apis

@62bd760
Run it yourself

Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements. Use when asked to "update latest APIs", "refresh deprecated SwiftUI APIs", "check for new SwiftUI deprecations", "scan for API changes", or after a new iOS/Xcode release. Requires the Sosumi MCP to be available.

Use this Skill: https://skilld.dev/gh/avdlee/swiftui-agent-skill/update-swiftui-apis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈87 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈1.5k more on demand in 1 file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈350 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Update SwiftUI APIs

Systematically scan Apple's developer documentation via the Sosumi MCP, identify deprecated SwiftUI APIs and their modern replacements, and update skills/swiftui-expert-skill/references/latest-apis.md.

Prerequisites

  • Sosumi MCP must be enabled and available (provides searchAppleDocumentation, fetchAppleDocumentation, fetchAppleVideoTranscript, fetchExternalDocumentation)
  • Write access to this repository (or a fork)

Workflow

1. Understand current coverage

Read skills/swiftui-expert-skill/references/latest-apis.md to understand:

  • Which deprecated-to-modern transitions are already documented
  • The version segments in use (iOS 15+, 16+, 17+, 18+, 26+)
  • The Quick Lookup Table at the bottom

2. Load the scan manifest

Read references/scan-manifest.md (relative to this skill). It contains the categorized list of API areas, documentation paths, search queries, and WWDC video paths to scan.

3. Scan Apple documentation

For each category in the manifest:

  1. Call searchAppleDocumentation with the listed queries to discover relevant pages.
  2. Call fetchAppleDocumentation with specific documentation paths to get full API details.
  3. Look for deprecation notices, "Deprecated" labels, and "Use ... instead" guidance.
  4. Note the iOS version where the modern replacement became available.
  5. Optionally call fetchAppleVideoTranscript for WWDC sessions that announce API changes.

Batch related searches together for efficiency. Focus on finding new deprecations not yet in latest-apis.md.

4. Compare and identify changes

Compare findings against existing entries. Categorize results:

  • New deprecations: APIs not yet documented in latest-apis.md
  • Corrections: Existing entries that need updating (wrong version, better replacement available)
  • New version segments: If a new iOS version introduces deprecations, add a new section

5. Update latest-apis.md

Follow the established format exactly. Each entry must include:

Section placement -- place under the correct version segment:

  • "Always Use (iOS 15+)" for long-deprecated APIs
  • "When Targeting iOS 16+" / "17+" / "18+" / "26+" for version-gated changes

Entry format:

**Always use `modernAPI()` instead of `deprecatedAPI()`.**

\```swift
// Modern
View()
    .modernAPI()

// Deprecated
View()
    .deprecatedAPI()
\```

Quick Lookup Table -- add a row at the bottom of the file:

| `deprecatedAPI()` | `modernAPI()` | iOS XX+ |

Keep the attribution line at the top of the file:

Based on a comparison of Apple's documentation using the Sosumi MCP, we found the latest recommended APIs to use.

6. Open a pull request

  1. Create a branch from main named update/latest-apis-YYYY-MM (use current year and month).
  2. Commit changes to skills/swiftui-expert-skill/references/latest-apis.md.
  3. Open a PR via gh pr create with:
    • Title: "Update latest SwiftUI APIs (Month Year)"
    • Body: Summary of new/changed entries, attribution to Sosumi MCP

Sosumi MCP Tool Reference

Tool Parameters Returns
searchAppleDocumentation query (string) JSON with results[] containing title, url, description, breadcrumbs, tags, type
fetchAppleDocumentation path (string, e.g. /documentation/swiftui/view/foregroundstyle(_:)) Markdown documentation content
fetchAppleVideoTranscript path (string, e.g. /videos/play/wwdc2025/10133) Markdown transcript
fetchExternalDocumentation url (string, full https URL) Markdown documentation content

Tips

  • Start broad with searchAppleDocumentation queries, then drill into specific paths with fetchAppleDocumentation.
  • Apple's deprecation docs typically say "Deprecated" in the page and link to the replacement.
  • WWDC "What's new in SwiftUI" sessions are the best source for newly introduced replacements.
  • When unsure about the exact iOS version for a deprecation, verify by checking the "Availability" section in the fetched documentation.
  • If an API is deprecated but no direct replacement exists, note this rather than suggesting an incorrect alternative.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts12d5 checks · Risk SAFE
  • Gen Agent Trust Hub14d

    The skill is generally safe and designed to automate the process of updating SwiftUI API documentation. It carries a low security risk as an indirect prompt injection surface because it fetches and processes external documentation content from Apple and other URLs, which could theoretically contain instructions intended to influence the agent's behavior during file updates and pull request creation.

  • Socket12d

    No alerts

  • Snyk14d

    Risk: LOW · No issues

  • Runlayer8mo

    2 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 62bd760. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago

README badge

README badge for avdlee/swiftui-agent-skill/update-swiftui-apis