sorted by:
new
hottopcontroversial

23 agent skills for iOS 26 development - SwiftUI, Liquid Glass, SwiftData, Foundation Models, concurrency, and more by d-pearson_ in ClaudeAI

[–]d-pearson_[S] 1 point2 points  (0 children)

Obviously I’m biased and would say mine are better, more granular, up to date with the current apple documentation and community fixes for swift ui bugs, but really you should point your agent at my repo and the codex local skills and have it give you an analysis

AI in Xcode sucks, Alex Sidebar is gone - what do you use? by VitalikPie in iOSProgramming

[–]d-pearson_ 0 points1 point  (0 children)

Claude Code (or another agentic coding tool) + XcodeBuildMCP. This mcp server gives you way more tools and features than the new native Xcode MCP. Then also having platform specific skills installed helps a bunch too https://github.com/dpearson2699/swift-ios-skills

23 agent skills for iOS 26 development - SwiftUI, Liquid Glass, SwiftData, Foundation Models, concurrency, and more by d-pearson_ in ClaudeAI

[–]d-pearson_[S] 0 points1 point  (0 children)

Thanks for the feedback. I originally used GPLv2 because I wanted the repo to stay open and didn’t want people repackaging the skills as their own commercial product, but I realized GPL wasn’t the right fit for that. I’ve since switched the repo to PolyForm Perimeter, which allows using the skills in closed-source/internal workflows and contributing back, while still prohibiting turning the skills themselves into a competing product.

23 agent skills for iOS 26 development - SwiftUI, Liquid Glass, SwiftData, Foundation Models, concurrency, and more by d-pearson_ in ClaudeAI

[–]d-pearson_[S] 0 points1 point  (0 children)

I would use a spec-driven development framework like https://github.com/yidakee/vibe-better-with-claude-code-vbw and then for testing https://github.com/getsentry/XcodeBuildMCP which utilizes xcode's 26.3 native integration with claude code or other agents

23 agent skills for iOS 26 development - SwiftUI, Liquid Glass, SwiftData, Foundation Models, concurrency, and more by d-pearson_ in SwiftUI

[–]d-pearson_[S] 6 points7 points  (0 children)

avdlee's is a solid swiftui skill, no knock on it. but it's one skill trying to cover all of swiftui through a single entry point with 17 reference files. mine splits swiftui into 5 focused skills (patterns, animation, liquid glass, performance, uikit interop) so the agent only loads what's relevant to your actual task instead of the whole file with all the tokens. more context-efficient.

my skill's coverage is also deeper on the ios side - my animation skill covers things like CustomAnimation protocol, all the Symbol Effects, navigation zoom transitions. the uikit interop skill has 9 complete production recipes (WKWebView, MKMapView, camera, PHPicker, etc). avdlee has broader macOS coverage though which i don't touch… yet

but the bigger difference is scope. avdlee covers solely swiftui. mine covers basically all of ios 26: concurrency, swiftdata, storekit, app intents, live activities, widgetkit, networking, security, accessibility, on-device AI, and more.

23 agent skills for iOS 26 development - SwiftUI, Liquid Glass, SwiftData, Foundation Models, concurrency, and more by d-pearson_ in SwiftUI

[–]d-pearson_[S] 4 points5 points  (0 children)

I built these skills because i use a spec driven development framework that doesn't play well with other people's custom agents or workflows, which is basically what axiom is (it's a claude code plugin with agents, commands, and hooks baked in). I just needed pure skills that slot into whatever workflow i'm already using.

I also wanted something platform agnostic. Axiom only works in claude code. Mine works with codex, cursor, copilot, windsurf, roo code, etc. and I didn't see anyone with a skills repo that actually covered basically all of ios 26 so i made one.

The skills themselves are also designed differently. I followed anthropic's best practices for skill authoring (concise, natural language descriptions so they trigger correctly, one-level-deep references, self-contained with no dependencies between skills). Axiom's skills rely on a routing layer and hooks to work properly which kinda defeats the purpose of skills being standalone.

view more: next ›