- Home
- Skills
- Mobile Development
- Apple App Audit
Works with the AI Agents you already use
Apple App Audit
Stop stale Apple API advice — source-grounded Swift audits via WWDC MCP.
$19
Apple App Audit
Example session with this skill installed
Use Apple App Audit. Verify WWDC MCP ingest status, then audit this iOS 17 SwiftUI app for NavigationView → NavigationStack/NavigationSplitView migration. Return P0–P3 sourced findings with a validation plan. Do not edit code yet.
- Read your context and instructions
- Compiled the apple app audit
Summary
Verified WWDC MCP trust/freshness and audited the NavigationView migration path. The broad audit returned noisy hits, so the result was narrowed to Apple’s navigation guidance before assigning severity.
Apple App Audit — Navigation modernization
Scope: iOS 17 · SwiftUI · NavigationView / NavigationLink(destination:) → NavigationStack / NavigationSplitView
Evidence consulted
| Source | Why |
|---|---|
| The SwiftUI cookbook for navigation (WWDC22-10054) | Apple’s primary explanation of NavigationStack, path-based navigation, and NavigationSplitView |
| SwiftUI Navigation documentation | Current navigation container guidance |
| HIG navigation guidance | UX and accessibility constraints |
Findings
P2 — Modernize NavigationView when the app needs the newer navigation model
Sourced fact: Apple’s WWDC22 session says the existing link-based navigation API works well for basic navigation and can continue to be used. NavigationStack and NavigationSplitView add richer programmatic navigation, deep linking, restoration, and multi-column control.
Repo observation: This fixture uses a simple NavigationView with NavigationLink(destination:) and shows no concrete correctness, compatibility, accessibility, App Review, or runtime failure.
Judgment: This is modernization, not a P1 defect. Adopt NavigationStack when the app needs the newer model or when touching this flow for related work.
Smallest safe correction: Replace only the root container first. Add navigationDestination(for:) or a NavigationPath only when the app actually needs data-driven routing. Use NavigationSplitView only for a real multi-column iPad/macOS information architecture.
Validate: Build for the deployment target; UI-test push/pop and any existing deep links; run a VoiceOver navigation pass.
P3 — Do not introduce extra navigation state without a product requirement
Sourced fact: WWDC22-10054 presents path-based navigation for programmatic control and restoration; it is not required merely because a basic NavigationLink works.
- Judgment: Keep the simple route simple unless deep linking, restoration, or centralized routing is needed.
Tool and corpus limitations
- The broad swift_app_audit result over-ranked unrelated evidence, so it was not used as the final severity signal.
- Live apple_doc_lookup was unavailable during one check; the audit disclosed that limitation and used indexed Apple/WWDC evidence instead.
- Nonzero ingest errors in individual source families must be reported rather than hidden by an overall healthy corpus.
Validation plan
- Xcode build for the actual deployment target.
- UI test push → pop and any supported deep-link/restoration path.
- iPad size-class check only if a split view is introduced.
- VoiceOver pass on navigation titles, back behavior, and focus.
Next steps
- Treat the current code as a P2 modernization unless a concrete navigation defect is demonstrated.
- If modernization is approved, change one flow first and validate behavior.
- Re-run Apple App Audit on the migrated flow before expanding the change.
Connects securely to your tools. The creator never sees your data.
About this skill
Modernizing Apple-platform apps requires navigating a constant stream of WWDC updates, API deprecations, and evolving App Review guidelines. Relying on model training data leads to stale recommendations that break builds or cause App Store rejections.
This skill connects to a WWDC MCP server to perform source-grounded audits of Swift, SwiftUI, UIKit, and StoreKit projects. It verifies current documentation, Swift Evolution proposals, and HIG requirements to provide evidence-based corrections.
What it does
- API modernizations identifies deprecated symbols and maps them to modern replacements like NavigationStack or Swift Concurrency.
- Risk assessment flags potential App Store Review violations by checking code against current Apple guidelines.
- Source-grounded auditing retrieves specific WWDC session transcripts and official docs to justify every suggested change.
- Migration planning generates step-by-step technical plans for adopting new framework features or platform capabilities.
- Validation mapping provides exact build, unit test, and accessibility checks to verify the safety of proposed corrections.
How it works
- Verify environment by checking the status of the WWDC MCP and ensuring the documentation index is fresh.
- Execute audit by targeting specific frameworks, features, or symptoms within your source code.
- Deep dive into findings using targeted searches across Swift Evolution, HIG, and API availability tools.
- Report findings categorized by priority (P0–P3) with explicit labels for sourced facts versus engineering judgment.
Frameworks & tools
Built for the Apple ecosystem including Swift, SwiftUI, AppKit, StoreKit, and App Intents. Requires a connected WWDC Model Context Protocol (MCP) server for live documentation and session retrieval.
Marketplace setup
Agensi MCP loads the purchased Apple App Audit skill for the signed-in Agensi account. WWDC MCP is a separate evidence dependency that supplies current Apple documentation, WWDC sessions, HIG guidance, and API history. Marketplace buyers need both connections for a source-grounded audit; connecting Agensi alone does not provide the WWDC evidence tools.
Why this beats prompting it yourself
Generic LLMs frequently hallucinate Apple API signatures or suggest patterns deprecated three versions ago. This skill forces the agent to cite specific WWDC sessions and official documentation, ensuring your migration plans are based on current engineering standards rather than outdated training data.
Use cases
- Migrating legacy SwiftUI NavigationView hierarchies to the modern NavigationStack API.
- Auditing StoreKit 2 implementations for renewal path compliance and API deprecations.
- Reviewing Swift Concurrency annotations in app extensions to prevent runtime hangs.
- Preparing for App Store submission by checking against the latest Review Guidelines.
Known limitations
Does not perform App Store Connect mutations, credential management, or signing. Limited to read-only analysis; it will not modify your source files directly.
Does not perform App Store Connect mutations, credential management, or signing. Limited to read-only analysis; will not modify source files directly. Requires a connected WWDC MCP. Does not prove App Review approval, on-device runs, or compile success without the buyer’s own project/toolchain.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 26 days ago
Requires
Permissions
Allowed Hosts
File Scopes
Read Files: inspect the buyer’s Swift/Xcode project for the feature under audit. Network Access: call the connected WWDC MCP for WWDC sessions, Apple docs, HIG, Swift Evolution, API history, and App Review guidance. No write, shell, browser, env, or credential access.