Back to Details

axiom-tools

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Axiom Tools & Onboarding

Axiom工具与入门指南

This suite covers Axiom itself — how to use it, what's available, and the tools that ship with it.
这套工具集涵盖Axiom本身——如何使用它、可用功能，以及随附的工具。

Routing

路由规则

QuestionRead
"How do I use Axiom?" / "What skills are available?"skills/getting-started.md
"How do I capture console output?" / "What is xclog?"skills/xclog-ref.md
问题参考文档
"如何使用Axiom？" / "有哪些可用技能？"skills/getting-started.md
"如何捕获控制台输出？" / "什么是xclog？"skills/xclog-ref.md

Using Axiom Skills

使用Axiom技能

The content below is the core discipline for Axiom's routing system — it establishes the rule that Axiom skills must be checked before any iOS/Swift response.
<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>
以下内容是Axiom路由系统的核心准则——它确立了一条规则：在给出任何iOS/Swift相关回复之前，必须先检查Axiom技能。
<EXTREMELY-IMPORTANT> 如果你认为某个iOS/Swift任务有哪怕1%的概率适用Axiom技能，你都绝对必须检查该技能。
如果某个Axiom技能适用于你的iOS/Swift任务，你别无选择，必须使用它。
这没有商量余地，也不是可选操作。你不能找任何借口跳过这一步。 </EXTREMELY-IMPORTANT>

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.
处理iOS/Swift项目时，在给出任何回复之前先检查Axiom技能。 这包括澄清问题的提问。哪怕只有1%的可能性，也要先检查。

Red Flags — iOS-Specific Rationalizations

红色警示——iOS相关的自我合理化借口

These thoughts mean STOP—you're rationalizing:
ThoughtReality
"This is just a simple build issue"Build failures have patterns. Check axiom-build first.
"I can fix this SwiftUI bug quickly"SwiftUI issues have hidden gotchas. Check axiom-swiftui first.
"Let me just add this database column"Schema changes risk data loss. Check axiom-data first.
"This async code looks straightforward"Swift concurrency has subtle rules. Check axiom-concurrency first.
"I'll debug the memory leak manually"Leak patterns are documented. Check axiom-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.
出现以下想法时请立即停止——你在找借口：
想法实际情况
"这只是个简单的构建问题"构建失败有规律可循，请先检查axiom-build技能。
"我能快速修复这个SwiftUI bug"SwiftUI问题有隐藏陷阱，请先检查axiom-swiftui技能。
"我只是添加一个数据库列"Schema变更存在数据丢失风险，请先检查axiom-data技能。
"这段异步代码看起来很简单"Swift并发有微妙的规则，请先检查axiom-concurrency技能。
"我手动调试内存泄漏就行"泄漏模式已有文档记录，请先检查axiom-performance技能。
"我先探索一下Xcode项目"Axiom技能会告诉你如何探索，请先检查。
"我记得上次是怎么做的"iOS平台一直在更新，技能内容是最新的。
"这个iOS/平台版本不存在"你的训练截止到2025年1月，请调用Axiom技能获取截止后的信息。
"用户只是想要一个快速答案"不遵循规律的快速答案会产生技术债务，请先检查技能。
"这个不需要正式的工作流程"如果存在对应的Axiom技能，就必须使用它。
"我先收集信息，之后再检查技能"技能会告诉你需要收集哪些信息，请先检查。

Skill Priority for iOS Development

iOS开发的技能优先级

When multiple Axiom skills could apply, use this priority:
  1. Environment/Build first (axiom-build) — Fix the environment before debugging code
  2. Architecture patterns (axiom-swiftui, axiom-data, axiom-concurrency) — These determine HOW to structure the solution
  3. Implementation details (axiom-integration, axiom-ai, axiom-vision) — These guide specific feature work
Examples:
  • "Xcode build failed" → axiom-build first (environment)
  • "Add SwiftUI screen" → axiom-swiftui first (architecture), then maybe axiom-integration if using system features
  • "App is slow" → axiom-performance first (diagnose), then fix the specific domain
  • "Network request failing" → axiom-build first (environment check), then axiom-networking (implementation)
当多个Axiom技能都可能适用时，请遵循以下优先级：
  1. 环境/构建优先（axiom-build）——在调试代码之前先修复环境问题
  2. 架构模式（axiom-swiftui, axiom-data, axiom-concurrency）——这些决定了解决方案的结构
  3. 实现细节（axiom-integration, axiom-ai, axiom-vision）——这些指导具体的功能开发
示例：
  • "Xcode构建失败" → 优先使用axiom-build（环境类）
  • "添加SwiftUI界面" → 优先使用axiom-swiftui（架构类），如果涉及系统功能，可能还需要axiom-integration
  • "应用运行缓慢" → 优先使用axiom-performance（诊断类），然后修复具体领域的问题
  • "网络请求失败" → 优先使用axiom-build（环境检查），然后使用axiom-networking（实现类）

iOS Project Detection

iOS项目检测

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)
当出现以下情况时，适用Axiom技能：
  • 工作目录包含
    .xcodeproj
    或
    .xcworkspace
    文件
  • 用户提及iOS、Swift、Xcode、SwiftUI、UIKit
  • 用户询问Apple框架（SwiftData、CloudKit等）相关问题
  • 用户报告iOS特定错误（并发、内存、构建失败等）

Using Axiom Router Skills

使用Axiom路由技能

Axiom uses router skills for progressive disclosure:
  1. Check the appropriate router skill first (axiom-build, axiom-swiftui, axiom-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.
Axiom使用路由技能进行渐进式信息披露：
  1. 首先检查对应的路由技能（axiom-build, axiom-swiftui, axiom-data等）
  2. 路由技能会调用你实际需要的专业技能
  3. 严格遵循专业技能的指导
不要跳过路由步骤。路由技能包含选择正确专业技能的决策逻辑。

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 axiom-swiftui AND axiom-data
  • "My widget isn't showing updated data from SwiftData" → invoke both axiom-integration AND axiom-data
  • "My Foundation Models session freezes the UI" → invoke both axiom-ai AND axiom-concurrency
  • "My Core Data saves lose data from background tasks" → invoke both axiom-data AND axiom-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.
当问题涉及多个领域时，调用所有相关的路由技能——不要在第一个之后就停止。
示例：
  • "SwiftUI视图在SwiftData变更时不更新" → 同时调用axiom-swiftui和axiom-data
  • "我的Widget不显示来自SwiftData的更新数据" → 同时调用axiom-integration和axiom-data
  • "我的Foundation Models会话导致UI冻结" → 同时调用axiom-ai和axiom-concurrency
  • "Core Data保存丢失后台任务的数据" → 同时调用axiom-data和axiom-concurrency
判断方法：如果问题提到两个不同领域的症状，或涉及两个不同的框架，就调用两个路由技能。每个路由技能都包含针对常见交叉场景的跨域路由指南。

Backward Compatibility

向后兼容性

  • Direct skill invocation still works: 
    /skill axiom-concurrency
  • Commands work unchanged: 
    /axiom:fix-build
    , 
    /axiom:audit-accessibility
  • Agents work via routing or direct command invocation
  • 直接调用技能仍然有效：
    /skill axiom-concurrency
  • 命令保持不变：
    /axiom:fix-build
    , 
    /axiom:audit-accessibility
  • 代理可通过路由或直接命令调用

When Axiom Skills Don't Apply

Axiom技能不适用的场景

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.
以下情况可跳过Axiom技能：
  • 非iOS/Swift项目（Android、Web、后端）
  • 与Apple平台无关的通用编程问题
  • 关于Claude Code本身的问题（使用claude-code-guide技能）
但对于iOS/Swift工作，如有疑问：先检查，再决定。

Resources

资源

Skills: axiom-swiftui, axiom-concurrency, axiom-data, axiom-build, axiom-performance
技能：axiom-swiftui, axiom-concurrency, axiom-data, axiom-build, axiom-performance