ios
iOS root: SDK, app lifecycle scene-based, permissions NSUsageDescription, HIG guidelines
What this skill does
# ios
## Purpose
This skill handles core iOS development tasks using Apple's SDK, focusing on app lifecycle management (scene-based), permissions via NSUsageDescription in Info.plist, and adherence to Human Interface Guidelines (HIG) for UI/UX consistency.
## When to Use
- Building native iOS apps with Swift or Objective-C.
- Managing app states in scene-based architectures (e.g., iOS 13+).
- Requesting user permissions like camera or location.
- Ensuring apps follow HIG for accessibility and design standards.
- Integrating iOS-specific features in cross-platform projects.
## Key Capabilities
- Access iOS SDK components like UIKit and SwiftUI for UI building.
- Handle scene-based lifecycle events (e.g., sceneDidBecomeActive).
- Manage permissions by adding keys to Info.plist (e.g., NSCameraUsageDescription).
- Enforce HIG through practices like adaptive layouts and voiceover support.
- Support for Xcode tools and Apple ecosystem integration.
## Usage Patterns
- Start by setting up an Xcode project: Use `xcodegen` or create via Xcode UI, then add dependencies via Swift Package Manager.
- For app lifecycle, implement UISceneDelegate methods in your scene manifest.
- To handle permissions, edit Info.plist directly or via Xcode's property list editor, adding strings for each usage description.
- Follow HIG by using Auto Layout constraints and testing with Accessibility Inspector.
- Test apps on simulators or devices using Xcode's build scheme: Select device, then run `xcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 14' build`.
## Common Commands/API
- **CLI Commands**: Use `xcodebuild` for building: `xcodebuild -workspace MyApp.xcworkspace -scheme MyApp clean build`. For archiving: `xcodebuild -scheme MyApp -configuration Release archive`.
- **API Endpoints**: Not applicable for direct endpoints; use iOS APIs like `AVCaptureDevice.requestAccess(for: .video)` for camera permission.
- **Code Snippets**:
- Request camera permission:
```
import AVFoundation
AVCaptureDevice.requestAccess(for: .video) { granted in
if granted { print("Access granted") } else { print("Denied") }
}
```
- Handle scene lifecycle in SceneDelegate.swift:
```
func sceneDidBecomeActive(_ scene: UIScene) {
// Resume tasks, e.g., start timers
}
func sceneWillResignActive(_ scene: UIScene) {
// Pause tasks
}
```
- Add permission to Info.plist (XML format):
```
<key>NSCameraUsageDescription</key>
<string>This app uses the camera for photo capture.</string>
```
- **Config Formats**: Use Info.plist for permissions (key-value pairs) or entitlements files for capabilities like iCloud (e.g., `<key>com.apple.security.application-groups</key><string>group.com.example</string>`).
## Integration Notes
- Integrate with other tools by linking via Xcode: Add pods with CocoaPods (`pod install`) or packages in Package.swift.
- For Apple services like App Store Connect, use environment variables for API keys: Set `$APPLE_API_KEY` and reference in scripts (e.g., `xcrun altool --upload-app --file MyApp.ipa --username $APPLE_USERNAME --password $APPLE_API_KEY`).
- When combining with Android (via mobile cluster), use shared configs but handle iOS-specific code in conditional blocks (e.g., `#if os(iOS)` in Swift).
- For CI/CD, integrate with GitHub Actions: Use `actions/checkout` then run `xcodebuild` in a macOS runner.
- If using third-party SDKs, add them via Swift Package Manager: Edit Package.swift and resolve with `swift package resolve`.
## Error Handling
- For permission denials, check status with `AVAuthorizationStatus.authorized` and prompt users via UIAlertController if needed.
- Handle build errors from `xcodebuild` by parsing output: Look for "Command PhaseScriptExecution failed" and fix scripts; use `xcodebuild -verbose` for details.
- For lifecycle issues, add logging in delegate methods (e.g., `print("Scene error: \(error)")` in sceneWillEnterForeground).
- Common fixes: If Info.plist keys are missing, Xcode will error on build; add them via the project editor. For HIG violations, use Xcode's accessibility audit tool and resolve warnings.
- Use try-catch for API calls: e.g., `do { try AVAudioSession.sharedInstance().setCategory(.playAndRecord) } catch { print(error.localizedDescription) }`.
## Usage Examples
- **Example 1: Basic App with Camera Permission**
Create a new Xcode project, add NSCameraUsageDescription to Info.plist, and implement permission request in ViewController.swift:
```
import UIKit
import AVFoundation
class ViewController: UIViewController {
override func viewDidLoad() { super.viewDidLoad(); requestCamera() }
func requestCamera() { AVCaptureDevice.requestAccess(for: .video) { granted in if granted { /* Proceed */ } } }
}
```
Build and run with `xcodebuild -scheme MyApp build` to test on simulator.
- **Example 2: Managing App Lifecycle**
In a scene-based app, handle state changes in SceneDelegate.swift:
```
import UIKit
class SceneDelegate: UIResponder, UIWindowSceneDelegate {
func sceneDidBecomeActive(_ scene: UIScene) { print("App active") }
func sceneWillEnterForeground(_ scene: UIScene) { /* Reload data */ }
}
```
Use `xcodebuild test` to verify lifecycle events during app testing.
## Graph Relationships
- Related to: mobile (cluster), as it shares mobile development patterns.
- Connected to: android (skill), via cross-platform mobile integration.
- Links with: apple-ecosystem (tag), for broader Apple services.
- Associated with: sdk-tools (implied), for shared SDK usage in iOS context.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.