abdullah4ai/apple-developer-toolkit

Overview

This skill bundles three Apple developer tools into a single unified binary (appledev) for documentation search, App Store Connect management, and AI-powered multi-platform app building. It provides instant offline-style access to Apple docs and WWDC sessions, a full-featured App Store Connect CLI, and a Swift/SwiftUI app generator with build, fix, and run capabilities. Credential requirements vary by feature: documentation needs none, App Store Connect requires an API key, and the app builder requires an LLM API key plus Xcode. The binary is designed for developer workflows that stay inside the Apple ecosystem.

How this skill works

The binary exposes three subcommands: documentation search (no credentials), store (App Store Connect CLI, requires .p8 API key), and build (AI-driven app builder, requires LLM key and Xcode). Documentation search indexes frameworks, symbols, sample code, and 1,267 WWDC sessions (2014–2025) for fast lookups. The store command maps 120+ App Store Connect operations to CLI actions (builds, TestFlight, submissions, metadata, analytics, webhooks), while the build workflow analyzes your natural-language description, generates a file-level plan, writes Swift/SwiftUI code, auto-fixes compile issues, and can launch a simulator or open the project in Xcode.

When to use it

• Lookup Apple framework docs, symbols, sample code, or WWDC talks without signing in.
• Automate App Store Connect tasks: uploads, test flights, submissions, metadata, analytics, and Xcode Cloud runs.
• Generate full Swift/SwiftUI apps from a feature description and iterate with auto-fix and simulator testing.
• Create or update localizations, pricing, IAPs, subscriptions, and release pipelines via CLI.
• Prototype multi-platform apps (iOS, iPad, macOS, watchOS, tvOS, visionOS) with AI-assisted scaffolding.

Best practices

• Use documentation search for rapid API checks and WWDC context before coding.
• Store CLI operations should use an App Store Connect API key stored in environment variables or a secure profile.
• Run appledev build setup to validate Xcode, XcodeGen, and LLM access before starting a project.
• Keep metadata and localization in version control and use metadata pull/diff commands before publishing.
• Iterate with build chat and /fix to minimize manual debugging; open in Xcode for final polish.

Example use cases

• Search for NavigationStack examples and related WWDC talks to design a SwiftUI navigation flow.
• Upload an IPA, wait for processing, publish to TestFlight, and add release notes in one script.
• Generate a multi-screen SwiftUI app from a product brief, auto-fix all compile errors, and launch the simulator.
• Pull app metadata, update localized metadata and screenshots, then submit the app for review.
• Run weekly analytics and insights to identify churn and create targeted win-back offers.