ai/ios-skills/ios-axiom-getting-started/SKILL.md
Use when first installing Axiom, unsure which skill to use, want an overview of available skills, or need help finding the right skill for your situation — interactive onboarding that recommends skills based on your project and current focus
npx skillsauth add kurko/dotfiles axiom-getting-startedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Welcome! This skill helps new users discover the most relevant Axiom skills for their situation.
Use the AskUserQuestion tool to gather context:
Question: "What brings you to Axiom today?"
Header: "Focus"
Options:
- "Debugging an issue" → Prioritize diagnostic skills
- "Optimizing performance" → Prioritize profiling skills
- "Adding new features" → Prioritize reference skills
- "Code review / quality check" → Prioritize audit commands
- "Just exploring" → Show overview
Question: "What's your primary tech stack?"
Header: "Stack"
Options:
- "SwiftUI (iOS 16+)" → SwiftUI-focused skills
- "UIKit" → UIKit-focused skills
- "Mixed SwiftUI + UIKit" → Both
- "Starting new project" → Best practices skills
Only ask if "Debugging an issue" was selected:
Question: "Which areas are you struggling with?"
Header: "Pain Points"
Multi-select: true
Options:
- "Xcode/build issues"
- "Memory leaks"
- "UI/animation problems"
- "Database/persistence"
- "Networking"
- "Concurrency/async"
- "Accessibility"
Based on answers, recommend 3-5 skills using this matrix:
Always recommend: axiom:xcode-debugging (universal starting point)
Then add based on pain points:
SwiftUI stack:
UIKit/Mixed:
Design decisions:
iOS 26+ features:
Navigation patterns:
Integrations:
Data persistence:
Start with audit commands (quick wins):
/axiom:audit-accessibility — WCAG compliance/axiom:audit-concurrency — Swift 6 violations/axiom:audit-memory — Leak patterns/axiom:audit-core-data — Migration safety/axiom:audit-networking — Deprecated APIsThen suggest:
Show the complete skill index (see below) and explain categories.
After gathering answers, output:
## Your Recommended Skills
Based on your answers, here are the skills most relevant to you right now:
### [Icon] [Category Name]
**axiom:[skill-name]** — [One-line description]
> Try: "[Example prompt they can use immediately]"
[Repeat for 3-5 skills]
### Quick Wins
Run these audit commands to find issues automatically:
- `/axiom:audit-[name]` — [What it finds]
## What's Next
1. **Try the example prompts above** — Copy/paste to see how skills work
2. **Run an audit command** — Get immediate actionable insights
3. **Describe your problem** — I'll suggest the right skill
4. **Browse the complete index below** — Explore all 34 skills
---
[Include the Complete Skill Reference below]
Include this reference section in every response for browsing:
Environment & Build Issues
Memory & Performance
UI Debugging
Liquid Glass (Material Design)
Layout & Navigation
Frameworks
Migration Guides
/axiom:audit-accessibility — VoiceOver labels, Dynamic Type, contrast, touch targets/axiom:audit-concurrency — Swift 6 violations, unsafe tasks, missing @MainActor/axiom:audit-memory — Timer leaks, observer leaks, closure captures, delegate cycles/axiom:audit-core-data — Migration risks, thread violations, N+1 queries/axiom:audit-networking — Deprecated APIs (SCNetworkReachability, CFSocket), anti-patterns/axiom:audit-liquid-glass — Glass adoption opportunities, toolbar improvements, blur migration"My build is failing" → Start: axiom:xcode-debugging → If dependency issue: axiom:build-debugging
"App is slow" → Start: axiom:performance-profiling (decision trees) → If SwiftUI: axiom:swiftui-performance → If memory grows: axiom:memory-debugging
"Memory leak" → Start: axiom:memory-debugging → If Objective-C blocks: axiom:objc-block-retain-cycles
"SwiftUI view issues" → Start: axiom:swiftui-debugging → If performance: axiom:swiftui-performance
"Navigation problems" → Start: axiom:swiftui-nav-diag (troubleshooting) → For patterns: axiom:swiftui-nav
"Which database?" → Decision guide: axiom:sqlitedata-migration → Then: axiom:swiftdata, axiom:sqlitedata, or axiom:grdb
"iOS 26 design" → Start: axiom:liquid-glass → Complete guide: axiom:liquid-glass-ref
"Code quality check"
→ Run: /axiom:audit-accessibility, /axiom:audit-concurrency, /axiom:audit-memory
→ Fix issues with relevant skills
Axiom skills load automatically — you don't need to memorize names or commands.
Automatic triggering (most common): Just describe your problem naturally. Claude detects which skill applies and loads it.
cloud-sync-diagswift-concurrencyExplicit invocation: If you know the skill name, invoke it directly:
/skill axiom-swift-concurrency/skill axiom-liquid-glassAudit commands: Run automated scans with slash commands:
/axiom:audit-memory — scans for memory leak patterns/axiom:audit-concurrency — scans for Swift 6 violationsKey insight: You don't need to know skill names. Describe what you're working on and Axiom routes to the right skill automatically.
Total: 50 skills, 12 audit commands, covering the complete iOS development lifecycle from design to deployment
data-ai
Merge the current worktree branch into main and sync main back. Use when the user says "merge to main", "ship it", "merge and continue", or after completing a task in a worktree and wanting to continue with the next one.
tools
Synchronize AI agent skills, commands, configs, permissions, hooks, and instructions across Claude Code, Codex CLI, and other Agent Skills-compatible tools. Use when the user asks to pull skills from Claude into Codex, sync Codex work back to Claude, migrate agent commands, reconcile frontmatter, update permissions, or keep agent setup files in parity.
testing
Write or update UI-independent use cases for QA. Use when the user says "write use cases", "add use cases", "QA use cases", "update use cases", "compose use cases", or when starting implementation of a new feature (after plan approval). Also activates for "what should we test", "regression cases", or "use cases for QA".
documentation
Skill on how to write a task. Use when user asks you to write a task (for Asana, Linear, Jira, Notion and equivalent). Also activates when user says "create task", "write task", or similar task creation workflow requests.