Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides targeted guidance for iOS developers working with the latest Apple ecosystem updates. It focuses on the precise implementation of SwiftUI and modern frameworks to ensure apps remain compatible with current system standards.
The skills cover complex hardware integrations and system-level features, such as configuring Bluetooth and Wi-Fi accessories through AccessorySetupKit or managing real-time updates with ActivityKit.
WHO IT'S FOR
iOS developers
implementing modern Apple framework features
IoT and hardware integration engineers
configuring Bluetooth and Wi-Fi accessories
Product engineers
building real-time Lock Screen experiences
Growth and marketing engineers
measuring ad effectiveness with privacy-preserving attribution
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Select three starter skills interactively
Installs: User-selected skills from the complete 86-skill Swift iOS Skills bundle. · any agent supported by the skills CLI
Before you start
Swift 6.3 for the target project
Platform: iOS 26+ development; the repository badge also lists iOS, iPadOS, and macOS.
Run this command in a terminal. In the skills CLI UI, select swift-architecture, swift-testing, and swiftui-liquid-glass, then choose the agent or agents for which they should be installed.
A feature description or source path replacing [FEATURE_DESCRIPTION_OR_SOURCE_PATH]
Any known dependencies, navigation handoffs, and existing tests
Use the swift-architecture skill to review the single feature described in [FEATURE_DESCRIPTION_OR_SOURCE_PATH]. Identify its state owner, inputs, outputs, dependencies, side effects, navigation handoffs, and current tests. Recommend the smallest suitable pattern, explain what it adds and what stays unchanged, and outline one vertical slice with explicit dependency and test seams. Do not modify the project.
A Swift unit-test file path replacing [TEST_FILE_PATH]
The project's Xcode and Swift versions
Use the swift-testing skill to review the unit test at [TEST_FILE_PATH] and propose a focused migration of one test to Swift Testing using the appropriate @Test, #expect, or #require APIs. Preserve XCTest if the test is UI automation, performance testing, an Objective-C exception test, or depends on snapshot-test tooling. Show the proposed replacement without editing files.
A short description of which controls are tappable or focusable
Use the swiftui-liquid-glass skill to review the SwiftUI view at [VIEW_FILE_PATH]. Choose one functional control or navigation surface that is a good candidate for Liquid Glass, then propose the smallest iOS 26-gated change with an earlier-version fallback. Check modifier order, container scope, interactivity, accessibility considerations, and whether custom glass is appropriate. Do not edit the file.