IF AN AXIOM SKILL APPLIES TO YOUR iOS/SWIFT TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
Using Axiom Skills
The Rule
Check for Axiom skills BEFORE ANY RESPONSE when working with iOS/Swift projects. This includes clarifying questions. Even 1% chance means check first.
Red Flags — iOS-Specific Rationalizations
These thoughts mean STOP—you're rationalizing:
| Thought |
Reality |
| "This is just a simple build issue" |
Build failures have patterns. Check ios-build first. |
| "I can fix this SwiftUI bug quickly" |
SwiftUI issues have hidden gotchas. Check ios-ui first. |
| "Let me just add this database column" |
Schema changes risk data loss. Check ios-data first. |
| "This async code looks straightforward" |
Swift concurrency has subtle rules. Check ios-concurrency first. |
| "I'll debug the memory leak manually" |
Leak patterns are documented. Check ios-performance first. |
| "Let me explore the Xcode project first" |
Axiom skills tell you HOW to explore. Check first. |
| "I remember how to do this from last time" |
iOS changes constantly. Skills are up-to-date. |
| "This iOS/platform version doesn't exist" |
Your training ended January 2025. Invoke Axiom skills for post-cutoff facts. |
| "The user just wants a quick answer" |
Quick answers without patterns create tech debt. Check skills first. |
| "This doesn't need a formal workflow" |
If an Axiom skill exists for it, use it. |
| "I'll gather info first, then check skills" |
Skills tell you WHAT info to gather. Check first. |
Skill Priority for iOS Development
When multiple Axiom skills could apply, use this priority:
- Environment/Build first (ios-build) — Fix the environment before debugging code
- Architecture patterns (ios-ui, axiom-ios-data, axiom-ios-concurrency) — These determine HOW to structure the solution
- Implementation details (ios-integration, axiom-ios-ai, axiom-ios-vision) — These guide specific feature work
Examples:
- "Xcode build failed" → ios-build first (environment)
- "Add SwiftUI screen" → ios-ui first (architecture), then maybe ios-integration if using system features
- "App is slow" → ios-performance first (diagnose), then fix the specific domain
- "Network request failing" → ios-build first (environment check), then ios-networking (implementation)
iOS Project Detection
Axiom skills apply when:
- Working directory contains
.xcodeproj or .xcworkspace
- User mentions iOS, Swift, Xcode, SwiftUI, UIKit
- User asks about Apple frameworks (SwiftData, CloudKit, etc.)
- User reports iOS-specific errors (concurrency, memory, build failures)
Using Axiom Router Skills
Axiom uses router skills for progressive disclosure:
- Check the appropriate router skill first (ios-build, axiom-ios-ui, axiom-ios-data, etc.)
- Router will invoke the specialized skill(s) you actually need
- Follow the specialized skill exactly
Do not skip the router. Routers have decision logic to select the right specialized skill.
Backward Compatibility
- Direct skill invocation still works:
/skill axiom-swift-concurrency
- Commands work unchanged:
/axiom:fix-build, /axiom:audit-accessibility
- Agents work via routing or direct command invocation
When Axiom Skills Don't Apply
Skip Axiom skills for:
- Non-iOS/Swift projects (Android, web, backend)
- Generic programming questions unrelated to Apple platforms
- Questions about Claude Code itself (use claude-code-guide skill)
But when in doubt for iOS/Swift work: check first, decide later.
1---2name: axiom-using-axiom-23description: Use when starting any iOS/Swift conversation - establishes how to find and use Axiom skills, requiring Skill tool invocation before ANY response including clarifying questions4license: MIT5---67<EXTREMELY-IMPORTANT>8If you think there is even a 1% chance an Axiom skill might apply to your iOS/Swift task, you ABSOLUTELY MUST check for the skill.910IF AN AXIOM SKILL APPLIES TO YOUR iOS/SWIFT TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.1112This is not negotiable. This is not optional. You cannot rationalize your way out of this.13</EXTREMELY-IMPORTANT>1415# Using Axiom Skills1617## The Rule1819**Check for Axiom skills BEFORE ANY RESPONSE when working with iOS/Swift projects.** This includes clarifying questions. Even 1% chance means check first.2021## Red Flags — iOS-Specific Rationalizations2223These thoughts mean STOP—you're rationalizing:2425| Thought | Reality |26|---------|---------|27| "This is just a simple build issue" | Build failures have patterns. Check ios-build first. |28| "I can fix this SwiftUI bug quickly" | SwiftUI issues have hidden gotchas. Check ios-ui first. |29| "Let me just add this database column" | Schema changes risk data loss. Check ios-data first. |30| "This async code looks straightforward" | Swift concurrency has subtle rules. Check ios-concurrency first. |31| "I'll debug the memory leak manually" | Leak patterns are documented. Check ios-performance first. |32| "Let me explore the Xcode project first" | Axiom skills tell you HOW to explore. Check first. |33| "I remember how to do this from last time" | iOS changes constantly. Skills are up-to-date. |34| "This iOS/platform version doesn't exist" | Your training ended January 2025. Invoke Axiom skills for post-cutoff facts. |35| "The user just wants a quick answer" | Quick answers without patterns create tech debt. Check skills first. |36| "This doesn't need a formal workflow" | If an Axiom skill exists for it, use it. |37| "I'll gather info first, then check skills" | Skills tell you WHAT info to gather. Check first. |3839## Skill Priority for iOS Development4041When multiple Axiom skills could apply, use this priority:42431. **Environment/Build first** (ios-build) — Fix the environment before debugging code442. **Architecture patterns** (ios-ui, axiom-ios-data, axiom-ios-concurrency) — These determine HOW to structure the solution453. **Implementation details** (ios-integration, axiom-ios-ai, axiom-ios-vision) — These guide specific feature work4647Examples:48- "Xcode build failed" → ios-build first (environment)49- "Add SwiftUI screen" → ios-ui first (architecture), then maybe ios-integration if using system features50- "App is slow" → ios-performance first (diagnose), then fix the specific domain51- "Network request failing" → ios-build first (environment check), then ios-networking (implementation)5253## iOS Project Detection5455Axiom skills apply when:56- Working directory contains `.xcodeproj` or `.xcworkspace`57- User mentions iOS, Swift, Xcode, SwiftUI, UIKit58- User asks about Apple frameworks (SwiftData, CloudKit, etc.)59- User reports iOS-specific errors (concurrency, memory, build failures)6061## Using Axiom Router Skills6263Axiom uses **router skills** for progressive disclosure:64651. Check the appropriate router skill first (ios-build, axiom-ios-ui, axiom-ios-data, etc.)662. Router will invoke the specialized skill(s) you actually need673. Follow the specialized skill exactly6869**Do not skip the router.** Routers have decision logic to select the right specialized skill.7071## Backward Compatibility7273- Direct skill invocation still works: `/skill axiom-swift-concurrency`74- Commands work unchanged: `/axiom:fix-build`, `/axiom:audit-accessibility`75- Agents work via routing or direct command invocation7677## When Axiom Skills Don't Apply7879Skip Axiom skills for:80- Non-iOS/Swift projects (Android, web, backend)81- Generic programming questions unrelated to Apple platforms82- Questions about Claude Code itself (use claude-code-guide skill)8384But when in doubt for iOS/Swift work: **check first, decide later.**
majiayu000