Update Swiftui Apis

Update SwiftUI APIs

Systematically scan Apple's developer documentation via the Sosumi MCP, identify deprecated SwiftUI APIs and their modern replacements, and update ../swiftui-expert-skill/references/latest-apis.md (sibling skill directory, relative to this skill's own directory).

Prerequisites

• Sosumi MCP must be enabled and available (provides searchAppleDocumentation, fetchAppleDocumentation, fetchAppleVideoTranscript, fetchExternalDocumentation). Verify before starting by calling searchAppleDocumentation with a trivial query (e.g. SwiftUI); if the tool is unavailable or errors, Sosumi is not usable.
• If Sosumi is unavailable: stop and tell the user it's required. As a fallback, manually browse https://developer.apple.com/documentation/swiftui and relevant WWDC session pages for deprecation notices, citing them the same way Sosumi output would be cited, then continue from Step 4.
• Write access to this repository (or a fork)

Workflow

1. Understand current coverage

Read ../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 ../swiftui-expert-skill/references/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. Run git status to confirm a clean working tree before starting (no unrelated uncommitted changes).
2. Create and switch to a branch from main named update/latest-apis-YYYY-MM (use current year and month): git checkout -b update/latest-apis-YYYY-MM main.
3. Commit changes to ../swiftui-expert-skill/references/latest-apis.md.
4. Confirm the branch is ahead of main (git log main..HEAD) before opening the PR.
5. 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

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.