Mastodawn

Paul Hudson Mar 11

Last week I released SwiftUI Pro, a free and open-source agent skill to help everyone write better SwiftUI code using agents such as Codex and Claude. It's already at 1800 stars on GitHub and rising, but it was just the beginning. https://github.com/twostraws/SwiftUI-Agent-Skill

GitHub - twostraws/SwiftUI-Agent-Skill: SwiftUI agent skill for Claude Code, Codex, and other AI tools.

SwiftUI agent skill for Claude Code, Codex, and other AI tools. - twostraws/SwiftUI-Agent-Skill

GitHub

Paul Hudson Mar 11

Today I'm pleased to announce three new agent skills that will power up agentic coding for app developers, all available now.

First up is Swift Concurrency Pro, designed to help you get maximum performance from your code *without* fighting the compiler. https://github.com/twostraws/swift-concurrency-agent-skill

GitHub - twostraws/Swift-Concurrency-Agent-Skill: Swift Concurrency agent skill for Claude Code, Codex, and other AI tools.

Swift Concurrency agent skill for Claude Code, Codex, and other AI tools. - twostraws/Swift-Concurrency-Agent-Skill

GitHub

Paul Hudson Mar 11

Next up is SwiftData Pro: an agent skill that helps AI coding tools write better SwiftData code. Covers Model, Query, predicates, indexes, migrations, relationships, iCloud sync, and lots of sharp edges. Works with all agents out of the box. https://github.com/twostraws/SwiftData-Agent-Skill

GitHub - twostraws/SwiftData-Agent-Skill: SwiftData agent skill for Claude Code, Codex, and other AI tools.

SwiftData agent skill for Claude Code, Codex, and other AI tools. - twostraws/SwiftData-Agent-Skill

GitHub

Paul Hudson Mar 11

Last but not least is Swift Testing Pro: an agent skill that helps AI coding tools write better tests using Swift Testing. Covers the Test macro, #expect and #require, parameterized testing, confirmations, exit tests, and more. https://github.com/twostraws/Swift-Testing-Agent-Skill

Aleksandar Vacić Mar 11

Now, you're probably thinking "this is great! But how would I have known about these if you hadn't told me?" Well, I'm also releasing a new GitHub repository curating agent skills for Swift developers – SwiftUI, SwiftData, accessibility, ASO, and more. https://github.com/twostraws/Swift-Agent-Skills

Paul Hudson Mar 11

Or maybe you're thinking, "great, but how do I use these with Xcode?" Boom: I've got that covered too, with a new article and YouTube video. Get them here: https://www.hackingwithswift.com/articles/283/how-to-install-and-use-ai-agent-skills-in-xcode

Agent skills in Xcode: How to install and use them today

Get agent skills for Swift, SwiftUI, Swift Testing, and more

Hacking with Swift

Paul Hudson Mar 11

In there I show you exactly how to use the skills today no matter whether you're using Xcode, Codex, or something else; I show you how to find great iOS/Swift skills *and* how to check their quality; and also explain what makes agent skills and AGENTS.md different. It's packed!

Paul Hudson Mar 11

As you might imagine, getting all this done took a huge amount of work, and it's all free to benefit the Apple development community. If it's useful to you, please share with others. Thank you! 🙇‍♂️

Paul Hudson Mar 11

PS: You have *no idea* how many times I've written "Claude Codex" rather than "Claude Code" in the last week 💀 (I have read, re-read, and re-re-read each repository countless times, and yet it's only a matter of time until someone spots the first comedy mistake.)

Richard Jones Mar 11

@twostraws thank you so much for sharing these! 🙏 Would you recommend referencing these skills/when to use them from my repo’s AGENTS.md or is that unnecessary? I’m wondering what the best way is to make sure my agent uses these skills when necessary without having to explicitly call it out each time.

Paul Hudson Mar 11

@richardjones Agents are able to infer when each skill is useful, so you can keep them installed and let your agents do their thing. I would probably suggest *against* adding them to your AGENTS.md file as an always-run or similar – perhaps add it as a command? "When I ask you to do a full review of this project, you should…"

Richard Jones Mar 11

@twostraws that makes sense, thank you again!

Chiron Codex Mar 11

@twostraws *feels seen*

Kyle Bashour Mar 12

@twostraws we should adopt that as the name to refer to either of them 😄

@twostraws How the hell are you able to do all that? Thank you!

Paul Hudson Mar 11

@fromtibo I have such a vast library of material to draw on, and regularly write "What's new in Swift/SwiftUI", so it is – comparatively! – straightforward for me. But… yeah, it took a *lot* to really dig through, prioritize stuff, condense it down to be token-friendly, then check everything repeatedly. At some point I had to stop second-guessing myself and just release it all, because I was starting to go around in circles 😅

@twostraws I can imagine your organization must be very efficient! From the outside, it just looks like you manage to be everywhere 😄
Thanks again for giving all that to the community. (And I must say it's a bit reassuring for us mortals to read that even you sometimes second-guess yourself ^^)

Ken of Earth Mar 11

@twostraws What can one say except:
Dude.
Thank you.

@twostraws Just incredible, Paul.

andyzoom01 Mar 12

@twostraws fantastic! Thank you. One question: what is the benefit of using the npx command in the Terminal app for installing skills vs. just using git clone in the Terminal and setting up symlink to use the skills in the Xcode codex folder. I understand the git approach and that if there are updates you make to your GutHub repos I can use git pull. What about npx install approach and using npx skills Terminal command. I haven’t used npx before so I’m try to learn pros/cons vs. just git clone and git pull. Thank you!!

Paul Hudson Mar 12

@andyzoom01 The `npx` command installs to all agents you select (Codex, Claude, etc), and also has a single `update` command to update all skills simultaneously.

andyzoom01 Mar 12

@twostraws the npx command approach to installation seem to work great and just like you I confirmed that Xcode codex coding assistant sees that installation of the agent skills in the ~/.agents directory. Given that, I’m wondering why Xcode is not requiring the skills.MD file to be in its special Xcode codex directory in the library path in order for Xcode to use the skills.

Paul Hudson Mar 12

@andyzoom01 That’s above my pay grade 🙂

andyzoom01 Mar 12

@twostraws 🙂 fair enough. I just went through your YouTube video again and you do mention in a couple places that even though there’s a special Xcode directory for Codex, just like Claude Code, Codex in Xcode just seems to understand the default .agents directory where the agent skill was installed from the npx add command so it just seems to work magically and the skills folder stays empty in the Xcode codex directory in the library just as you mentioned. So you do mention it, it’s just we can’t figure out why Apple doesn’t need to see stuff in there for Codex and can use the .agents folder whereas Claude code cannot. Thanks for all your help. This was so very helpful.!

@twostraws I’ve an a11y skill that also does wcag audit: https://github.com/ramzesenok/iOS-Accessibility-Audit-Skill/

Are PRs welcome?

GitHub - ramzesenok/iOS-Accessibility-Audit-Skill: A Skill that will help agents audit your app or concrete features against accessibility norms

A Skill that will help agents audit your app or concrete features against accessibility norms - ramzesenok/iOS-Accessibility-Audit-Skill

GitHub

Paul Hudson Mar 11

@ramzesenok Yes! Please check the Contributing section in the README.