axiom using axiom
- Repo stars 0
- Author repo skills-registry
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
<EXTREMELY-IMPORTANT>
If 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.
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.
</EXTREMELY-IMPORTANT>
# 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:
1. **Environment/Build first** (ios-build) — Fix the environment before debugging code
2. **Architecture patterns** (ios-ui, axiom-ios-data, axiom-ios-concurrency) — These determine HOW to structure the solution
3. **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:
1. Check the appropriate router skill first (ios-build, axiom-ios-ui, axiom-ios-data, etc.)
2. Router will invoke the specialized skill(s) you actually need
3. Follow the specialized skill exactly
**Do not skip the router.** Routers have decision logic to select the right specialized skill.
### Multi-Domain Questions
When a question spans multiple domains, **invoke ALL relevant routers — don't stop after the first one.**
Examples:
- "My SwiftUI view doesn't update when SwiftData changes" → invoke **both** ios-ui AND ios-data
- "My widget isn't showing updated data from SwiftData" → invoke **both** ios-integration AND ios-data
- "My Foundation Models session freezes the UI" → invoke **both** ios-ai AND ios-concurrency
- "My Core Data saves lose data from background tasks" → invoke **both** ios-data AND ios-concurrency
**How to tell**: If the question mentions symptoms from two different domains, or involves two different frameworks, invoke both routers. Each router has cross-domain routing guidance for common overlaps.
## 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.**
---
> Source: [ComeOnOliver/skillshub](https://github.com/ComeOnOliver/skillshub) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Sections and files
Listed in source order.
sections -> The Rule → Red Flags — iOS-Specific Rationalizations → Skill Priority for iOS Development → iOS Project Detection → Using Axiom Router Skills → Multi-Domain Questions
terms -> Check for Axiom skills BEFORE ANY RESPONSE when working with iOS/Swift projects. · Environment/Build first · Architecture patterns · Implementation details · router skills · Do not skip the router. · invoke ALL relevant routers — don't stop after the first one. · both
files/cmd -> .xcodeproj · .xcworkspace · /skill axiom-swift-concurrency · /axiom:fix-build · /axiom:audit-accessibility
body sha256 -> 7a184fc09628
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.
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:
iOS Project Detection
Axiom skills apply when: Working directory contains
.xcodeprojor.xcworkspaceUser 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.