Back to Details

axiom-using-axiom

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<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>
<EXTREMELY-IMPORTANT> 如果你认为你的iOS/Swift任务有哪怕1%的概率可以应用Axiom技能，你都必须绝对要检查该技能。
如果某款Axiom技能适用于你的iOS/Swift任务，你别无选择，必须使用它。
这没有商量余地，也不是可选操作。你无法找理由规避这一要求。 </EXTREMELY-IMPORTANT>

Using Axiom Skills

使用Axiom技能

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 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.
出现以下想法时请立刻停止——你在找借口:
想法实际情况
"这只是个简单的构建问题"构建失败存在规律，先检查ios-build技能。
"我能快速修复这个SwiftUI bug"SwiftUI问题存在隐藏陷阱，先检查ios-ui技能。
"我只是要添加一个数据库列"架构变更存在数据丢失风险，先检查ios-data技能。
"这段异步代码看起来很简单"Swift并发有微妙的规则，先检查ios-concurrency技能。
"我要手动调试内存泄漏问题"泄漏模式已有文档记录，先检查ios-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 (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)
当多个Axiom技能都可能适用时，请遵循以下优先级:
  1. 环境/构建优先（ios-build）——在调试代码前先修复环境问题
  2. 架构模式（ios-ui, axiom-ios-data, axiom-ios-concurrency）——这些技能决定了解决方案的架构方式
  3. 实现细节（ios-integration, axiom-ios-ai, axiom-ios-vision）——这些技能指导具体的功能开发
示例:
  • "Xcode构建失败" → 优先使用ios-build（环境类）
  • "添加SwiftUI页面" → 优先使用ios-ui（架构类），如果使用系统功能可能还需要ios-integration
  • "应用运行缓慢" → 优先使用ios-performance（诊断类），然后修复具体领域的问题
  • "网络请求失败" → 优先使用ios-build（环境检查），然后使用ios-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 (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.
Axiom使用路由技能来逐步披露信息:
  1. 先检查对应的路由技能（ios-build, axiom-ios-ui, axiom-ios-data等）
  2. 路由技能会调用你实际需要的专业技能
  3. 严格遵循专业技能的要求操作
不要跳过路由技能。路由技能包含决策逻辑，能够选择合适的专业技能。

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
  • 直接调用技能仍然有效: 
    /skill axiom-swift-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相关工作中存疑时: 先检查，再决定。