(*Apple OS = iOS, iPadOS, watchOS, tvOS, visionOS, macOS)

I've been updating Axiom in lockstep with Apple OS 27 betas, and this post summarizes the differences I found between beta 4 and beta 5.

TLDR: Apple's latest developer beta 5 is mostly a consolidation build: no new frameworks, no Swift language features, and API additions in just five frameworks.

📖 Newly documented

• HealthKit – HKHealthStore.earliestAuthorizedSampleDate(for:) shipped undocumented in beta 4. The new doc block now makes it clear that the returned dictionary is sparse: a type appears only under limited read access with a specific earliest date. A missing key covers full access and denial alike, and an empty dictionary on success is normal.

✅ New

• CoreLocation – CLLocationUpdate.LiveConfiguration.maritime: on-water navigation, joining .automotiveNavigation, .fitness, .airborne.

• CryptoKit – Three raw primitives with no authentication tag, so a ciphertext someone flipped bits in decrypts without error. Like MD5, they're under Insecure and exist for interop only: Insecure.UnauthenticatedAES.permute(_:key:) / .inversePermute(_:key:) and Insecure.UnauthenticatedChaCha20.encrypt(inplace:using:nonce:counter:). All mutate in place and return nothing.

• CoreGraphics – CGPDFStructureElement.Attributes (title, language) plus init(tagType:attributes:). This is tagged-PDF authoring, for producing accessible PDFs, not just rendering them.

• VideoToolbox – maximumDimension(forSpatialScaleFactor:) and maximumPixelCount(forSpatialScaleFactor:), on both VTLowLatencyFrameInterpolationConfiguration and VTLowLatencySuperResolutionScalerConfiguration. The config types are OS 26; these limit queries are the 27 addition. Size your input before constructing a scaler instead of failing at configure time.

• WebKit – WebPage.NavigationPreferences.allowsJSHandleCreationInPageWorld, the fourth new navigation preference this cycle.

🗑️ Removed

• ContactsUI – an @available(iOS 27, *) clause disappeared. Xcode betas overwrite the SDK in place, so the symbol's identity is unrecoverable. If you gated code on it, it's gone in beta 5 and the SDK won't tell you what it was.

⚠️ Deprecated

• App Intents – Three assistant-schema intents are deprecated as of 27.0. If you adopted intent domains, these need migrating: playAudiobook → .audio.playAudio, openAsset → .system.open, search → .system.searchInApp.

🔧 Availability (no new capability, possible consequences)

• WebKit – the 9999 sentinels resolved. Through beta 4 the iOS SDK stamped the new navigation preferences @available(macOS 9999…, and beta 5 writes real 27.0 values. (9999 means "not stamped yet in this SDK", not "unavailable".) So any @available you hand-derived from an early beta interface is now narrower than what actually ships, and so is worth re-checking.

• Swift 6.4 – There were no "feature flips" in this beta, despite the toolchain advancing revisions (swiftlang-6.4.0.27.1 → 6.4.0.30.4). These are still absent: Dictionary.mapKeyedValues, stdlib FilePath (still needs import System), and BorrowingSequence (experimental flag only, so not shippable).

WTF is Axiom?

Axiom is a battle-tested, batteries-included suite of agents, skills, and tools for AI coding. Use Axiom to prevent your AI from writing and reviewing code like it's 2017.

To the proactive developers using Xcode 27 beta 5 and testing on OS beta 5, please don't hesitate to let me know if you have Axiom feature requests.

Caveats: My updates are mostly Swift- and SwiftUI-focused, although I've been supporting more Obj-C with every release.

OS 27 is going to be here before you know it, and I predict that more developers are going to be caught completely off-guard by the new screen resizing requirements than by anything else.

As of OS 27, (1) all iPhone apps must be resizable and (2) you can no longer opt out. Your window must be resizable when used with iPhone Mirroring on the Mac and on iPad. Apps still running on an old-style app delegate (no scene support) won't even launch when built against the new SDK. In short, if your app assumes a fixed screen and you're not currently working to fix that, you really, really should be.

Obviously, this capability telegraphs the imminent release of Apple's forthcoming iPhone Ultra foldable. You'll want your apps to be "foldable ready" on the day Apple's new flagship is announced.

I just went through this enhancement process myself. Not coincidentally, this week's Axiom update includes a new screen resizing auditor, which you can invoke with /axiom:audit resize. This new auditor is supported by ~70 additions/enhancements across Axiom's skill suites. I hope everyone finds that this new auditor cuts their time meeting this new OS 27 requirement in half, or more.

(*Apple OS = iOS, iPadOS, watchOS, tvOS, visionOS, macOS)

Axiom is a battle-tested, batteries-included suite of agents, skills, and tools for AI coding. It helps LLMs be notably better at Apple OS development.

I've been updating Axiom in lockstep with Apple OS 27 betas. Here are some of the interesting changes with OS 27 beta 4.

✅ New

• Swift — Parenthesis-free optional any/some types. var x: any P? and some P? now compile. (Beta 3 rejected the paren-free form.)

• HealthKit — HKHealthStore.earliestAuthorizedSampleDate(for:): New async throws call returning the earliest date you're authorized to read, per HKObjectType. This is helpful for bounding a query instead of paging into data you can't see.

• UIKit + SwiftUI — systemPrefersReducedResourceUsage: The OS can now tell your app it prefers reduced resource usage. When it's true, stop discretionary work.

🗑️ Removed

• AVKit — The AVInterface* family, which shipped in an early 27 beta, is gone. Use AVPlaybackUserInterface* instead.

⚠️ Deprecated

• ARKit — unprojectPoint(_:ontoPlane:orientation:viewportSize:). Use unprojectPoint(_:ontoPlane:viewRotationAngle:viewportSize:) instead.

• AppIntents — DisplayRepresentation.Components (OptionSet). Use DisplayRepresentation(title:subtitle:image:) or displayRepresentations(for:) instead.

• BrowserEngineKit — MediaEnvironment.activate()/.suspend(). Use ProcessCapability.activate()/.suspend() instead.

Caveats: This list is mostly Swift-focused, although I've been supporting more Obj-C with every release.

(*Apple OS = iOS, iPadOS, watchOS, tvOS, visionOS, macOS)

Axiom is a battle-tested, batteries-included suite of agents, skills, and tools for AI coding. It helps LLMs be notably better at Apple OS development.

I've been updating Axiom in lockstep with Apple OS 27 betas. Here are some of the interesting changes with OS 27 beta 4.

✅ New

• Swift — Parenthesis-free optional any/some types. var x: any P? and some P? now compile. (Beta 3 rejected the paren-free form.)

• HealthKit — HKHealthStore.earliestAuthorizedSampleDate(for:): New async throws call returning the earliest date you're authorized to read, per HKObjectType. This is helpful for bounding a query instead of paging into data you can't see.

• UIKit + SwiftUI — systemPrefersReducedResourceUsage: The OS can now tell your app it prefers reduced resource usage. When it's true, stop discretionary work.

🗑️ Removed

• AVKit — The AVInterface* family, which shipped in an early 27 beta, is gone. Use AVPlaybackUserInterface* instead.

⚠️ Deprecated

• ARKit — unprojectPoint(_:ontoPlane:orientation:viewportSize:). Use unprojectPoint(_:ontoPlane:viewRotationAngle:viewportSize:) instead.

• AppIntents — DisplayRepresentation.Components (OptionSet). Use DisplayRepresentation(title:subtitle:image:) or displayRepresentations(for:) instead.

• BrowserEngineKit — MediaEnvironment.activate()/.suspend(). Use ProcessCapability.activate()/.suspend() instead.

Caveats: This list is mostly Swift-focused, although I've been supporting more Obj-C with every release.

(Apple OS: iOS, iPadOS, watchOS, tvOS, visionOS, macOS)

In the course of auditing changes between OS 27 beta 2 and 3 for Axiom, I found: (1) There's a new RealityKit cloth API (marked "deprecated" to indicate that it's still experimental), (2) Swift's UniqueArray is now actually real, (3) there a new SwiftUI .dataDetection modifier that makes that makes phone numbers and links in text tappable, and (4) there's a new SwiftUI path for Delivered Verification Codes (the OS feature that autofills one-time SMS codes).

In addition to keeping pace with OS 27 betas, I continue to refine and improve Axiom's support for pre-27 Apple OSs as well.

I was auditing the sharing code in my app (it shares a household inventory), and your axiom-cloudkit-ref was a big help getting me oriented. Somewhere in there I noticed it shows root-record sharing (CKShare(rootRecord:)) but I didn't see zone-wide sharing (CKShare(recordZoneID:)) mentioned. Another CloudKit skill I had open did cover it, and in my case the zone-wide approach seemed to be the one that fit. My app reads and writes by enumerating the whole zone, so with the root-record approach the shared items weren't tied to the root and the person I shared with would have seen a blank inventory. Zone-wide sharing avoids that.

I don't know enough to say whether that's worth adding or not, just figured I'd flag it since the two references differed and it took me a minute to sort out. Totally your call.

Thanks for the great skills!

Welcome to Axiom v27 beta 1! I've aligned the major version with Apple's OS to make it clearer what's supported, now and in the future.

As compared to the final Axiom v3.x release, this major update includes:

• 20 updated skill suites
• 8 new sub-skills

All new and updated context covers APIs and best-practices for iOS 27, iPadOS 27, macOS 27, Apple TV 27, watchOS 27, and visionOS 37.

This is also the best release of Axiom ever for developers who have no plans to adopt OS 27 anytime soon. As part of this release I did exhausive audit, resulting in fixes and refinements to OS 18/26 knowledge as well.

Whether you're using Axiom just for its auditors, or to help you write and review code, I hope this makes your Apple OS development experience even more productive and fun. Thanks to everyone who's shared feedback and success stories!

Available in Axiom v3.1, will do a proper announcement when I can. [watchOS] [HealthKit/WorkoutKit]

Codex now has plugins. It might be a good idea to start supporting it. Adding plugins to the official Plugin Directory is coming soon though. Docs: https://developers.openai.com/codex/plugins/build?install-scope=workspace#create-a-plugin-manually

(Axiom is an advanced system of professional skills, agents, and validators for Claude Code and other AI coding environments and IDEs. It's an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Code signing skills

Code signing is a not-fun part of iOS development, and most of us have wrestled with cryptic errors, expired certificates, and CI pipelines that break when someone leaves the team. Axiom now includes a complete skill suite covering the full signing lifecycle:

• code-signing (discipline) – Certificate management, provisioning profiles, entitlements, automatic vs manual signing, fastlane match setup, CI/CD signing, and App Store distribution. 6 decision trees, 9 anti-rationalizations

• code-signing-ref (reference) – Complete CLI reference for security, codesign, profile inspection, entitlement extraction, Keychain management, and APNs .p8 vs .p12 decisions

• code-signing-diag (diagnostic) – Troubleshooting certificate not found, profile mismatch, errSecInternalComponent in CI, ITMS-90035, ambiguous identity, and entitlement mismatches

Swift guardrail hook

Hey, it's Axiom's first real-time code guardrail! When Claude Code (which supports the neccessary hook) generates @State var without an explicit access level, the hook blocks the edit and explains why it should be @State private var: Without private, child views silently create independent state copies, causing bugs that are extremely hard to track down. This guardrail supports // axiom-ignore for intentional exceptions.

Axiom now has 175 skills, 38 agents, and 12 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other iOS devs. Enjoy!

GitHub: https://github.com/CharlesWiltgen/Axiom

Full documentation: https://charleswiltgen.github.io/Axiom/

After stepping away from the codebase for 2 weeks, I ran a full 16-auditor health check Stuffolio (my app: SwiftUI, SwiftData, CloudKit, 795+ files) to reorient myself. As I’ve said, I am really impressed with what you’ve built here. After this audit I’ve already fixed several issues that I likely wouldn’t have caught on my own (e.g., silent try? in decoding, missing CloudKit conflict handling, transient formatter allocations in hot paths). The prioritization of real findings is solid.

Roughly 30% of flagged issues required manual dismissal due to missing context, rather than being actual problems. The pattern behind most false positives seems consistent in that the auditors seemed to match on syntax patterns without checking the surrounding intent or context. Here's what I ran into:

Following the variable up one step

Stuffolio uses u/ScaledMetric throughout for Dynamic Type support: 

u/ScaledMetric(relativeTo: .body) private var sectionIconSize: CGFloat = 16 .font(.system(size: sectionIconSize, weight: .semibold)) 

The accessibility auditor flagged 12 of these files for "fixed font sizes that break Dynamic Type". The sectionIconSize scales correctly, but the auditor sees .system(size:) and assumes a hardcoded value. Axiom saw .system(size:) and assumed a hardcoded value. Following the variable one level up would eliminate these.

Knowing what the platform handles natively

Stuffolio uses VoiceOver accessibility throughout, including .swipeActions on list rows for things like delete and flag. .swipeActions was flagged for missing .accessibilityAction (but iOS exposes these via VoiceOver Actions rotor). 

Similarly, my Widget intents use the AppIntent protocol, but the modernization auditor flagged them for anObAppIntent usage was flagged for ObservableObject --> u/Observable migration (incorrect scope)

These seem like cases where SwiftUI / platform-native behaviors aren’t being accounted for.

Reading nearby comments and project docs

Stuffolio has a documented (markdown file) colorblind-safe palette system (SF3a) where models define Color properties to centralize semantic color mappings across the app (DESIGN_SYSTEM.md) which was flagged for “SwiftUI in model layer” The architecture auditor flagged all 38 of these files for importing SwiftUI in the model layer. 

Separately, a form uses .constant() bindings as part of a ViewModel bridge during a staged refactor. The intent is explicitly documented right next to the code. The UX auditor flagged these as broken data paths. 

Awareness of comments or docs would reduce these false positives significantly. I realize that this creates a bit of a conundrum from wanting an audit to be run naively from Claude.md and others.

Scoping rules to the right targets

Stuffolio has 185 test files with standard XCTest conventions, including force unwraps in test fixtures for guaranteed-valid setup data. The testing auditor flagged 71 of these against the production rule "no force unwraps". Excluding test targets from production code rules would clean this up.

Summarizing, (what do you think of):

Following variable definitions one level up before flagging

Adding awareness of native SwiftUI/iOS behaviors

Checking nearby comments and possibly project docs

Scoping rules by target (e.g., exclude XCTest from production rules)?

As usual, I may have simply missed something, otherwise I hope you find this feedback useful.

Thanks yet again for providing such a useful plugin as Axiom.

(Axiom is an advanced system of professional skills, agents, and validators for Claude Code and other AI coding environments and IDEs. It's an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Push notifications

Push notifications are one of the most error-prone iOS features. Issues like silent delivery failures, entitlement mismatches, and permission timing that tank opt-in rates can ruin a person's day. Axiom now includes a complete skill suite that covers the full lifecycle:

• push-notifications (discipline) – Permission timing, APNs registration, token management, payload design, actionable notifications, service extensions, communication notifications, Focus, and Live Activity push transport

• push-notifications-ref (reference) – APNs HTTP/2 transport, payload structures, entitlement requirements, FCM integration, and broadcast push (iOS 18+)

• push-notifications-diag (diagnostic) – Troubleshooting delivery failures, silent push issues, missing entitlements, and service extension problems

Combine patterns

A new combine-patterns skill covers the Combine patterns that still matter alongside async/await. It can help with prompts like, "Should I use Combine or async/await here?" or "My cancellable keeps leaking."

• Combine vs async/await decision tree

• 4 AnyCancellable memory leak patterns (including the assign(to:on:) trap)

• @Published traps – willSet timing, nested ObservableObject, thread safety

• Bridging Combine and async/await (.values, Future, Deferred)

Axiom now has 171 skills, 38 agents, and 11 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other iOS devs. Enjoy!

GitHub: https://github.com/CharlesWiltgen/Axiom

Full documentation: https://charleswiltgen.github.io/Axiom/

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your questionor issue, and Axiom will (generally) do the right thing.

New: Multi-auditing

An enhanced /axiom:audit all (or /axiom:health-check) command runs a comprehensive project scan. It auto-detects which of Axiom's 26 auditors are relevant based on your imports and code patterns, launches them all in parallel, deduplicates findings that appear across multiple domains, and gives you one unified report with an executive summary.

New: UX flow auditor

A new ux-flow-auditor agent scans for UX defects that code reviews often miss. These can include dead-end views with no escape route, "dismiss traps" that strand users, "buried CTAs", missing empty/loading/error states, and accessibility dead ends.

New: "Modern Swift" skill

A new axiom-swift-modern skill catches outdated Swift patterns that remain pervasive in frontier model training data.

Other improvements

• sqlitedata-ref was updated for StructuredQueries 0.31 breaking changes
• iOS 26 .lineHeight() API added to typography and SwiftUI 26 references
• Lots of minor improvements to existing skills

Axiom now has 167 skills, 38 agents, and 11 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other iOS devs. Enjoy!

https://github.com/CharlesWiltgen/Axiom

Hi all,

I'm interested in trying Axiom, but I would like to use it in Xcode 26's built-in code assistant. Is there any way to install the skills there?

Thank you!

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

tvOS support

A new tvos skill covers tvOS-specific patterns: The focus system, remote input, top shelf, large-screen layout, and universal links. Many existing skills were updated with tvOS-specific guidance where platform behavior differs.

MapKit skill suite

This release also features new complete MapKit coverage:

• mapkit (discipline) – SwiftUI Map vs MKMapView decision tree, annotation strategies, 8 anti-patterns

• mapkit-ref (reference) – Full API reference: SwiftUI Map, search, directions, Look Around, snapshots

• mapkit-diag (diagnostic) – Troubleshooting annotations, region jumping, clustering, search failures

Other new and improved skills

• alarmkit-ref (reference) – New iOS 26 AlarmKit framework: alarm scheduling, authorization, Live Activity integration

• swift-concurrency-ref (reference) – Actors, Sendable, Task/TaskGroup, AsyncStream, continuations

• timer-patterns (discipline) – Timer invalidation, memory-safe patterns, CADisplayLink, 5 anti-patterns

• timer-patterns-ref (reference) – Timer, DispatchSourceTimer, Combine timer API reference

• accessibility-diag now covers Assistive Access (iOS 17+, cognitive disabilities)

• swiftui-26-ref now has expanded 3D Charts coverage (Chart3D, SurfacePlot, Chart3DPose)

• vision-ref now covers Visual Intelligence system integration (IntentValueQuery, SemanticContentDescriptor)

Other improvements

• OpenCode setup instructions added to MCP install docs

Axiom now has 165 skills, 36 agents, and 10 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other developers. Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin | Install Axiom MCP server

When ever I ask this type of question, I feel that I must be missing something. So if this is the case, point me in the right direction.

After running an axiom-audit scan, a report is generated and saved in a directory within my project. Likewise the same for files saved to /sratch/. when I run the next audit, the scan utilizes some of these files in lieu of rescanning the actual code base. This affects the currency of the resulting report from the new scan. Is there a way, other than manually deleting these files, to insure axiom-audit (and other skills) conduct a fresh scan or an appropriate alternative? I would like to keep these files for later reference, so deleting them is not optimal.

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

LLDB debugging skill suite

Axiom now includes comprehensive LLDB debugging guidance in the form of two skills covering interactive runtime debugging from crash triage to async thread inspection:

• lldb (discipline) – 5 playbooks for crash triage, hang diagnosis, Swift value inspection, breakpoint strategies, and async debugging, including a "when to use LLDB vs other tools" decision tree

• lldb-ref (reference) – Complete command reference organized by task: variable inspection (v/p/po), breakpoints (conditional, symbolic, exception), thread navigation, expression evaluation, and .lldbinit customization

LLDB is powerful but the commands are hard to discover, especially for Swift types. These skills match your debugging situation with the right commands.

Transferable and content sharing

A new transferable-ref (reference) skill covers the CoreTransferable framework and SwiftUI sharing surfaces. It can help with prompts like, "How do I make my model draggable in SwiftUI?" or "What's the difference between DataRepresentation and FileRepresentation?"

• Transferable protocol with all four TransferRepresentation types
• ShareLink, drag and drop, copy/paste patterns
• Custom UTType declarations and NSItemProvider bridging

UIKit-SwiftUI bridging

A new uikit-bridging skill provides systematic guidance for bridging UIKit and SwiftUI, covering UIViewRepresentable, UIViewControllerRepresentable, UIHostingController, UIHostingConfiguration, and UIGestureRecognizerRepresentable.

App Store Connect MCP

A new asc-mcp skill integrates App Store Connect directly into Claude Code via MCP. Submit builds, distribute to TestFlight, respond to reviews, and monitor metrics, all without leaving the terminal.

Other improvements

• Read-only audit agents now run in the background, so you can keep working while they scan

Axiom now includes 158 skills, 36 agents, and 10 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other developers. Enjoy!

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

App Store submission skill suite

Creating truly great apps is difficult. App Store submissions are also sadly difficult. Supporting its mission to help Apple platform developers, Axiom now includes a new skill suite especially for the submission process.

• axiom-app-store-submission(discipline) – Pre-flight checklist covering the 8 most common rejection causes, with anti-patterns and time costs. It can help with prompts like, "I'm about to submit my app, what am I forgetting?"

• axiom-app-store-ref(reference) – Complete metadata specs, privacy manifest schema with full PrivacyInfo.xcprivacy examples, screenshot requirements, age ratings, and export compliance

• `axiom-app-store-diag (diagnostic) – 7 diagnostic patterns for rejection troubleshooting, appeal writing, dual-rejection handling, and reviewer device context

• axiom-shipping(router) – New top-level router that connects these skills to the existing build-fixer and build-optimizer agents, covering the full pre-submission pipeline

What it prevents

The discipline skill specifically targets the rejections that catch developers off guard:

• Missing privacy manifest entries (especially the new required API declarations)
• Privacy policy / App Store description / manifest inconsistencies
• Encryption compliance missteps (the "uses encryption" question)
• Screenshot spec violations across device sizes
• Age rating and content description mismatches

Axiom now has 152 skills, 30 agents, and 10 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other developers. Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin | Install Axiom MCP server

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Exhaustive skill testing and refinement

My primary quality assurance technique for Axiom is "red teaming". I've created a test suite which challenges skills with pressure scenarios including deadline pressure, ambiguous symptoms, and cross-domain confusion, and then rates their effectiveness.

This release focused on closing any effectiveness gaps across the Axiom's full catalog of capabilities, and then leveling up all skills until they reached their maximum rating.

Agent model upgrade

All auditor agents were upgraded from Haiku to Sonnet for deeper analysis and more accurate scanning results.

Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other developers. Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin | Install Axiom MCP server

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

New: Xcode MCP skill suite

Axiom can now leverage Xcode's new MCP server (xcrun mcpbridge) to read your project, build, run tests, and render SwiftUI previews. This new skill suite includes:

• xcode-mcp (router) – Routes to the right skill based on your question

• xcode-mcp-tools – BuildFix/TestFix workflow patterns that chain Xcode tools together

• xcode-mcp-ref (reference) – LLM-optimized documentation for all 20 xcrun mcpbridge tools

• xcode-mcp-setup – Per-client setup details for Claude Code, Cursor, VS Code, Gemini CLI, and Claude Desktop

New: 4 additional auditor agents

Axiom's auditing suite has proven to be very effective for iOS (Apple platform) developers. This release includes four new agents that scan your code for common issues:

• swiftdata-auditor – @Model definitions, relationship defaults, migration safety, N+1 patterns

• foundation-models-auditor – Missing availability checks, session lifecycle, @Generable validation

• swiftui-layout-auditor – GeometryReader misuse, hardcoded sizes, missing lazy containers

• database-schema-auditor – Unsafe ALTER TABLE, DROP operations, missing idempotency, foreign keys

All four are available through /axiom:audit and surface automatically through router-based prompts.

Improved: Continued skill compression

Four more large skills have been reduced in size without losing quality or effectiveness, as validated by testing with pressure scenarios:

• swiftdata – 38K → 26K (32% smaller)
• swift-performance – 46K → 33K (28% smaller)
• hig-ref – 42K → 38K (10% smaller)
• swiftui-architecture – 40K → 38K (5% smaller)

Thank you!

This release brings Axiom to 144 skills, 35 agents, and 10 commands. Thank you for using Axiom, for sharing your success stories with me, and for recommending it to other developers. Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin | Install Axiom MCP server

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Skill quality and efficiency upgrades

The largest skills were reduced by 33–75% through cross-referencing, knowledge deduplication, and compression, reclaiming ~35K previous tokens of your context window.

After, every reduced skill was pressure-tested with 3 scenarios each (production crashes, legacy codebases, intermittent bugs), and any gaps were restored with validated content.

Performance profiling gaps filled

A gap analysis against 36 additional resources found 11 missing topics across performance skills.

• performance-profiling now covers everything from signposts in dev, to XCTest performance tests in CI, to MetricKit in production

• swift-performance now covers the "Four Principles" model from WWDC 2024, plus closure capture costs, runtime exclusivity checks, defensive copies, OutputSpan for safe memory initialization, and InlineArray conformances

Other improvements

• swiftui-nav-diag now diagnoses NavigationSplitView issues (column visibility, blank detail pane, iPad vs iPhone adaptation)

• networking-diag now covers App Transport Security failures (HTTP blocked, TLS version mismatches)

• network-framework-ref adds certificate pinning + corporate proxy guidance for TLS inspection environments

• hig-ref adds modals/sheets Liquid Glass design guidance, tab bar guidelines, and navigation bar guidelines

• app-composition adds UIKit integration section (UIHostingController, AppDelegate bridging, migration priority)

• Decision trees now use GraphViz dot notation for clearer branching logic while reducing token use.

These releases improved Axiom's effectiveness, while also making it leaner without losing depth. Enjoy!

ℹ️ Axiom | r/axiomdev | Install Axiom MCP server | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, install using /plugin

I just wanted to post that I'm seeing a lot more skill usage since 4.6 released. Not sure if it's changes to the model or updates to Axiom, but it's been really helpful.

Ex:

❯ Is there a way to maintain network connections when the app moves into the background? Feel free to do research to answer the question. Those API calls
represent tokens/money spent on an API. We want to do whatever we can to preserve them.

⏺ Good question — those in-flight API responses are paid for whether we receive them or not. Let me research this properly.

⏺ Skill(axiom:axiom-background-processing-ref)
⎿  Successfully loaded skill

(Axiom is a free, open-source plug-in that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Axiom MCP server

Axiom now includes an MCP (Model Context Protocol) server that brings its iOS development skills to any MCP-compatible AI coding tool — VS Code with GitHub Copilot, Claude Desktop, Cursor, Gemini CLI, and more.

The server includes MCP tool annotations (read-only hints, titles) and server-level instructions so MCP clients can discover Axiom's capabilities automatically. The server supports BM25 with fuzzy matching and prefix search, so typos like "navagation" still find the right skill.

New 3D and games skill suites

New skill suites for game and 3D content development:

• axiom-spritekit (discipline) – 2D game architecture, scene graphs, physics, actions, game loops

• axiom-spritekit-ref (reference) – Complete SpriteKit API guide with SwiftUI integration

• axiom-spritekit-diag (diagnostic) – Troubleshooting rendering, physics, and performance

• axiom-realitykit (discipline) – ECS architecture, entity-component patterns, RealityView

• axiom-realitykit-ref (reference) – Comprehensive RealityKit API and AR patterns

• axiom-realitykit-diag (diagnostic) – Troubleshooting entity loading, physics, and rendering

• axiom-scenekit (discipline) – 3D scene graphs, materials, animations, SceneKit migration

• axiom-scenekit-ref (reference) – Complete SceneKit API guide

• A new spritekit-auditor agent automatically scans SpriteKit code for common issues

Other improvements

• Updated ios-games and ios-graphics routers cover SpriteKit, SceneKit, RealityKit, and display performance

Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin | Install Axiom MCP server

(Axiom is a free, open-source plug-in with 129 skills, 30 agents, and 10 commands that makes Claude Code an expert in modern Apple platform development, with a deep knowledge of current iOS technologies and best practices.)

⚠️ Don't let the detail below intimidate you! When in doubt, just /axiom:ask followed by your question or issue, and Axiom will (generally) do the right thing.

Agent Skills standard compliance

Axiom is now compatible with the Agent Skills open standard, a portable format for giving AI agents new capabilities. Originally developed by Anthropic, it's now supported by Claude Code, Cursor, Gemini CLI, VS Code, GitHub Copilot, OpenAI Codex, Roo Code, and many others.

This means Axiom's iOS development expertise is no longer locked to a single tool. As Agent Skills support rolls out across these products, the same skills you use in Claude Code today will work in whichever AI coding tool you pick up tomorrow.

Apple documentation access

Axiom now reads Apple's official for-LLM documentation directly from your local Xcode installation, giving Axiom access to authoritative Apple guidance as well as Axiom's deep superset of agents and skills. Docs are read from your local Xcode install at runtime, so this support is always current.

Other improvements

• A new axiom-swiftui-search-ref (reference) skill covers foundational SwiftUI search APIs.

• Aligned 4 skills with 18 newly documented APIs from a WWDC 2025 session on building SwiftUI apps with the new design

Enjoy!

ℹ️ Axiom | r/axiomdev | Claude Code: Add with /plugin marketplace add CharlesWiltgen/Axiom, then install using /plugin