audit-swiftui-api-currency

Detects deprecated, renamed, and hallucinated SwiftUI APIs in macOS projects.

2|1|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/yigitkonur/plugin-swiftui --skill audit-swiftui-api-currency-yigitkonur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-swiftui-api-currency
Source: https://github.com/yigitkonur/plugin-swiftui/tree/main/plugins/swiftui/skills/audit-swiftui-api-currency
Command: npx skills add https://github.com/yigitkonur/plugin-swiftui --skill audit-swiftui-api-currency-yigitkonur

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI-generated SwiftUI code often contains stale APIs learned from old training data, freshly deprecated macOS 26.5 calls, or entirely hallucinated modifier names that compile-looking but never existed. This Skill audits a macOS SwiftUI codebase to find every API that has drifted out of currency and, where safe, applies mechanical fixes. ## Core Features & Use Cases - 14-rule defect index (curr-01 to curr-14): Covers deprecated symbols like NavigationView, .foregroundColor, 1-param onChange, and .accentColor, plus hallucinated names like .glassBackground() and visionOS-only APIs misused on macOS. - Hybrid lint engine: Combines tier-1 grep tells with tier-2 ast-grep structural rules (e.g., detecting 1-param onChange closures and inline NavigationLink inside List) that flat grep cannot express, emitting unified JSON and SARIF output. - Corpus-grounded verification: Confirms findings against 1,857 real shipping macOS apps via the swiftui-ctx CLI and Apple docs via Sosumi, with auto-fix only for four mechanical renames under a fix-safety protocol. - Use Case: Run it on an AI-generated macOS SwiftUI project before release to catch a deprecated NavigationView, an invented .liquidGlass() modifier, and an ungated macOS-26-only call, then auto-fix the safe renames with one commit per finding. ## Quick Start Audit my macOS SwiftUI project for deprecated and hallucinated APIs and fix the safe mechanical renames.

Frequently Asked Questions about audit-swiftui-api-currency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find deprecated SwiftUI APIs in a macOS project?

Run the shared lint runner with this skill's rule set against your sources; it locates candidates via grep tells and ast-grep structural rules, then you read each hit in full and confirm deprecations against the swiftui-ctx corpus and Apple docs before reporting.

How to detect hallucinated SwiftUI modifiers that don't exist?

Check the candidate name with swiftui-ctx lookup; an exit 3 not-found result with a did-you-mean suggestion corroborates that no shipping Mac app uses the symbol. Names like .glassBackground(), .liquidGlass(), and .cardStyle() are hard-fail findings.

Which deprecated SwiftUI APIs get auto-fixed versus flagged?

Only four mechanical renames are auto-fixed: .foregroundColor to .foregroundStyle, .cornerRadius to .clipShape, MagnificationGesture/RotationGesture renames, and .accentColor to .tint. Everything else is flagged with the correct idiom for the developer to apply.

Does this work for iOS SwiftUI code or only macOS?

It is macOS-only by design. All deprecation floors, replacement idioms, and availability gates are validated against the macOS SDK, and iOS appears only as a contrast case in the references.

Why does the lint runner report parse warnings on some files?

A parse warning means the file did not fully parse, so structural ast-grep rules may have missed matches there. You must read those files by hand rather than treating them as clean.