swiftui-performance-audit

Redirect legacy swiftui-performance-audit prompts to the ios-performance workflow.

8|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill swiftui-performance-audit-choshimwy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swiftui-performance-audit
Source: https://github.com/ChoshimWy/iOSAgentSkills/tree/main/skills/swiftui-performance-audit
Command: npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill swiftui-performance-audit-choshimwy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Compatibility layer for the legacy swiftui-performance-audit prompt so that tasks are automatically redirected to the standardized ios-performance workflow.

Core Features & Use Cases

  • Redirects legacy swiftui-performance-audit prompts to ios-performance to ensure consistent handling.
  • Provides clear messaging when the old prompt name is encountered and guide users to the new flow.
  • Enables a smooth handoff to ios-performance for analysis, metrics collection, and validation in real projects.
  • Use Case: A project documents a reference to swiftui-performance-audit; the skill routes the work to ios-performance and instructs verification via verify-ios-build.

Quick Start

Route legacy swiftui-performance-audit tasks to ios-performance and perform verify-ios-build validation in the project context.

Frequently Asked Questions about swiftui-performance-audit

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

FAQPage Schema
How do I migrate legacy SwiftUI performance audit prompts to a modern workflow?▼

Migrating legacy SwiftUI performance audit prompts involves mapping them to the standardized ios-performance workflow. This ensures consistent handling and redirects outdated prompt names to the current analysis pipeline.

What is the best way to handle deprecated SwiftUI performance prompts in existing documentation?▼

Handling deprecated SwiftUI performance prompts requires routing them to the ios-performance workflow. This provides clear messaging that the old name is deprecated and guides tasks to the new flow automatically.

Does the ios-performance workflow require build validation on connected devices?▼

The ios-performance workflow requires final validation under verify-ios-build. It prefers using .xcworkspace files and connected devices to ensure accurate performance metrics and compatibility checks.

How do I validate SwiftUI performance analysis results in a real project context?▼

Validating SwiftUI performance analysis results requires running verify-ios-build in the project context. This step confirms metrics collected by the ios-performance workflow function correctly within the actual environment.

Why should I transition my SwiftUI performance tasks away from the old audit prompt?▼

Transitioning SwiftUI performance tasks away from the old audit prompt ensures standardized analysis through the ios-performance workflow. Continuing with deprecated names risks inconsistent handling and lacks modern validation support.

Can I use ios-performance metrics collection for legacy SwiftUI compatibility checks?▼

Using ios-performance metrics collection for legacy SwiftUI compatibility checks is fully supported. The workflow accepts redirected tasks from swiftui-performance-audit and performs comprehensive analysis on real projects.