axiom-build

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Build & Environment

构建与环境

You MUST use this skill for ANY build, environment, or Xcode-related issue before debugging application code.

在调试应用代码前，遇到任何构建、环境或Xcode相关问题时，必须使用此技能。

When to Use

使用场景

Use this router when you encounter:

Build failures (
```
BUILD FAILED
```
, compilation errors, linker errors)
Test crashes or hangs
Simulator issues (won't boot, device errors)
Xcode misbehavior (stale builds, zombie processes)
Dependency conflicts (CocoaPods, SPM)
Build performance issues (slow compilation)
Environment issues before debugging code

当你遇到以下情况时，使用此路由：

构建失败（
```
BUILD FAILED
```
、编译错误、链接器错误）
测试崩溃或挂起
模拟器问题（无法启动、设备错误）
Xcode运行异常（构建缓存残留、僵尸进程）
依赖冲突（CocoaPods、SPM）
构建性能问题（编译缓慢）
调试代码前出现的环境问题

Routing Logic

路由逻辑

This router invokes specialized skills based on the specific issue:

此路由会根据具体问题调用专门的技能：

1. Environment-First Issues → xcode-debugging

1. 优先排查环境的问题 → xcode-debugging

Triggers:

```
BUILD FAILED
```
without obvious code cause
Tests crash in clean project
Simulator hangs or won't boot
"No such module" after SPM changes
Zombie
```
xcodebuild
```
processes
Stale builds (old code still running)
Clean build differs from incremental build

Why xcode-debugging first: 90% of mysterious issues are environment, not code. Check this BEFORE debugging code.

Invoke:

skills/xcode-debugging.md

触发场景:

无明显代码原因的
```
BUILD FAILED
```
干净项目中测试崩溃
模拟器挂起或无法启动
修改SPM后出现"No such module"
僵尸
```
xcodebuild
```
进程
构建缓存残留（运行的仍是旧代码）
干净构建与增量构建结果不同

为什么优先用xcode-debugging：90%的疑难问题源于环境而非代码。调试代码前务必先检查环境。

调用:

skills/xcode-debugging.md

2. Slow Builds → build-performance

2. 构建缓慢 → build-performance

Triggers:

Compilation takes too long
Type checking bottlenecks
Want to optimize build time
Build Timeline shows slow phases

Invoke:

skills/build-performance.md

触发场景:

编译耗时过长
类型检查瓶颈
希望优化构建时间
Build Timeline显示阶段耗时过长

调用:

skills/build-performance.md

3. SPM Dependency Conflicts → spm-conflict-resolver (Agent)

3. SPM依赖冲突 → spm-conflict-resolver (Agent)

Triggers:

SPM resolution failures
"No such module" after adding package
Duplicate symbol linker errors
Version conflicts between packages
Swift 6 package compatibility issues
Package.swift / Package.resolved conflicts

Why spm-conflict-resolver: Specialized agent that analyzes Package.swift and Package.resolved to diagnose and resolve Swift Package Manager conflicts.

Invoke: Launch

spm-conflict-resolver

agent

触发场景:

SPM解析失败
添加包后出现"No such module"
重复符号链接器错误
包之间的版本冲突
Swift 6包兼容性问题
Package.swift / Package.resolved冲突

为什么用spm-conflict-resolver：这是专门的Agent，可分析Package.swift和Package.resolved来诊断并解决Swift Package Manager冲突。

调用: 启动

spm-conflict-resolver

agent

4. Security & Privacy Audit → security-privacy-scanner (Agent)

4. 安全与隐私审计 → security-privacy-scanner (Agent)

Triggers:

App Store submission prep
Privacy Manifest requirements (iOS 17+)
Hardcoded credentials in code
Sensitive data storage concerns
ATS violations
Required Reason API declarations

Why security-privacy-scanner: Specialized agent that scans for security vulnerabilities and privacy compliance issues.

Invoke: Launch

security-privacy-scanner

agent or

/axiom:audit security

触发场景:

App Store提交准备
隐私清单要求（iOS 17+）
代码中存在硬编码凭据
敏感数据存储隐患
ATS违规
Required Reason API声明

为什么用security-privacy-scanner：专门的Agent，可扫描安全漏洞和隐私合规问题。

调用: 启动

security-privacy-scanner

agent或执行

/axiom:audit security

5. iOS 17→18 Modernization → modernization-helper (Agent)

5. iOS 17→18现代化迁移 → modernization-helper (Agent)

Triggers:

Migrate ObservableObject to @Observable
Update @StateObject to @State
Adopt modern SwiftUI patterns
Deprecated API cleanup
iOS 17+ migration

Why modernization-helper: Specialized agent that scans for legacy patterns and provides migration paths with code examples.

Invoke: Launch

modernization-helper

agent or

/axiom:audit modernization

触发场景:

将ObservableObject迁移至@Observable
将@StateObject更新为@State
采用现代SwiftUI模式
清理废弃API
iOS 17+迁移

为什么用modernization-helper：专门的Agent，可扫描遗留模式并提供带代码示例的迁移方案。

调用: 启动

modernization-helper

agent或执行

/axiom:audit modernization

6. Build Failure Auto-Fix → build-fixer (Agent)

6. 构建失败自动修复 → build-fixer (Agent)

Triggers:

BUILD FAILED with no clear error details
Build sometimes succeeds, sometimes fails
App builds but runs old code
"Unable to boot simulator" error
Want automated environment-first diagnostics

Why build-fixer: Autonomous agent that checks zombie processes, Derived Data, SPM cache, and simulator state before investigating code. Saves 30+ minutes on environment issues.

Invoke: Launch

build-fixer

agent or

/axiom:fix-build

触发场景:

BUILD FAILED但无明确错误详情
构建时而成功时而失败
应用构建成功但运行旧代码
"Unable to boot simulator"错误
需要自动化的优先环境诊断

为什么用build-fixer：自主Agent，会先检查僵尸进程、Derived Data、SPM缓存和模拟器状态，再排查代码问题。可节省30分钟以上的环境问题排查时间。

调用: 启动

build-fixer

agent或执行

/axiom:fix-build

7. Slow Build Optimization → build-optimizer (Agent)

7. 构建速度优化 → build-optimizer (Agent)

Triggers:

Builds take too long
Want to identify slow type checking
Expensive build phase scripts
Suboptimal build settings
Want parallelization opportunities

Why build-optimizer: Scans Xcode projects for build performance optimizations — slow type checking, expensive scripts, suboptimal settings — to reduce build times by 30-50%.

Invoke: Launch

build-optimizer

agent or

/axiom:optimize-build

触发场景:

构建耗时过长
希望识别缓慢的类型检查环节
构建阶段脚本开销过大
构建设置不理想
寻找并行化优化机会

为什么用build-optimizer：扫描Xcode项目以优化构建性能——包括缓慢的类型检查、高开销脚本、不理想的设置等，可将构建时间缩短30-50%。

调用: 启动

build-optimizer

agent或执行

/axiom:optimize-build

8. General Dependency Issues → build-debugging

8. 通用依赖问题 → build-debugging

Triggers:

CocoaPods resolution failures
"Multiple commands produce" errors
Framework version mismatches
Non-SPM dependency graph conflicts

Invoke:

skills/build-debugging.md

触发场景:

CocoaPods解析失败
"Multiple commands produce"错误
Framework版本不匹配
非SPM依赖图冲突

调用:

skills/build-debugging.md

9. TestFlight Crash Triage → testflight-triage

9. TestFlight崩溃分类排查 → testflight-triage

Triggers:

Beta tester reported a crash
Crash reports in Xcode Organizer
Crash logs aren't symbolicated
TestFlight feedback with screenshots
App was killed but no crash report

Why testflight-triage: Systematic workflow for investigating TestFlight crashes and reviewing beta feedback. Covers symbolication, crash interpretation, common patterns, and Claude-assisted analysis.

Invoke: See axiom-shipping (skills/testflight-triage.md)

触发场景:

Beta测试人员反馈崩溃
Xcode Organizer中的崩溃报告
崩溃日志未符号化
带截图的TestFlight反馈
应用被终止但无崩溃报告

为什么用testflight-triage：用于调查TestFlight崩溃和评审Beta反馈的系统化流程。涵盖符号化、崩溃解读、常见模式及Claude辅助分析。

调用: 参见axiom-shipping (skills/testflight-triage.md)

10. App Store Connect Navigation → app-store-connect-ref

10. App Store Connect导航指南 → app-store-connect-ref

Triggers:

How to find crashes in App Store Connect
ASC metrics dashboard navigation
Understanding crash-free users percentage
Comparing crash rates between versions
Exporting crash data from ASC
App Store Connect API for crash data

Why app-store-connect-ref: Reference for navigating ASC crash analysis, metrics dashboards, and data export workflows.

Invoke: See axiom-shipping (skills/app-store-connect-ref.md)

触发场景:

如何在App Store Connect中查找崩溃
ASC指标仪表板导航
理解无崩溃用户百分比
对比不同版本的崩溃率
从ASC导出崩溃数据
用于崩溃数据的App Store Connect API

为什么用app-store-connect-ref：用于导航ASC崩溃分析、指标仪表板和数据导出流程的参考文档。

调用: 参见axiom-shipping (skills/app-store-connect-ref.md)

11. Crash Log Analysis → crash-analyzer (Agent)

11. 崩溃日志分析 → crash-analyzer (Agent)

Triggers:

User has .ips or .crash file to analyze
User pasted crash report text
Need to parse crash log programmatically
Identify crash pattern from exception type
Check symbolication status

Why crash-analyzer: Autonomous agent that parses crash reports, identifies patterns (null pointer, Swift runtime, watchdog, jetsam), and generates actionable analysis.

Invoke: Launch

crash-analyzer

agent or

/axiom:analyze-crash

触发场景:

用户需要分析.ips或.crash文件
用户粘贴了崩溃报告文本
需要以编程方式解析崩溃日志
根据异常类型识别崩溃模式
检查符号化状态

为什么用crash-analyzer：自主Agent，可解析崩溃报告、识别模式（空指针、Swift运行时、看门狗、jetsam）并生成可操作的分析结果。

调用: 启动

crash-analyzer

agent或执行

/axiom:analyze-crash

12. MetricKit API Reference → metrickit-ref

12. MetricKit API参考 → metrickit-ref

Triggers:

MetricKit setup and subscription
MXMetricPayload parsing (CPU, memory, launches, hitches)
MXDiagnosticPayload parsing (crashes, hangs, disk writes)
MXCallStackTree decoding and symbolication
Field crash/hang collection
Background exit metrics

Why metrickit-ref: Complete MetricKit API reference with setup patterns, payload parsing, and integration with crash reporting systems.

Invoke: See axiom-performance (

skills/metrickit-ref.md

)

触发场景:

MetricKit设置与订阅
MXMetricPayload解析（CPU、内存、启动次数、卡顿）
MXDiagnosticPayload解析（崩溃、挂起、磁盘写入）
MXCallStackTree解码与符号化
现场崩溃/挂起收集
后台退出指标

为什么用metrickit-ref：完整的MetricKit API参考，包含设置模式、负载解析及与崩溃报告系统的集成方法。

调用: 参见axiom-performance (

skills/metrickit-ref.md

)

13. Hang Diagnostics → hang-diagnostics

13. 挂起诊断 → hang-diagnostics

Triggers:

App hangs or freezes
Main thread blocked for >1 second
UI unresponsive to touches
Xcode Organizer shows hang diagnostics
MXHangDiagnostic from MetricKit
Watchdog terminations (app killed during launch/background transition)

Why hang-diagnostics: Systematic diagnosis of hangs with decision tree for busy vs blocked main thread, tool selection (Time Profiler, System Trace), and 8 common hang patterns with fixes.

Invoke: See axiom-performance (

skills/hang-diagnostics.md

)

触发场景:

应用挂起或冻结
主线程阻塞超过1秒
UI对触摸无响应
Xcode Organizer显示挂起诊断
MetricKit的MXHangDiagnostic
看门狗终止（应用在启动/后台切换时被杀死）

为什么用hang-diagnostics：系统化的挂起诊断流程，包含繁忙线程 vs 阻塞主线程的决策树、工具选择（Time Profiler、System Trace），以及8种常见挂起模式的修复方案。

调用: 参见axiom-performance (

skills/hang-diagnostics.md

)

14. Live Debugging → axiom-lldb

14. 实时调试 → axiom-lldb

Triggers:

Need to reproduce a crash interactively
Want to set breakpoints and inspect state
Crash report analyzed, now need live investigation
Need to attach debugger to running app

Why axiom-lldb: Crash reports tell you WHAT crashed. LLDB tells you WHY.

Invoke:

skills/lldb.md

触发场景:

需要交互式重现崩溃
希望设置断点并检查状态
已分析崩溃报告，现在需要实时调查
需要将调试器附加到运行中的应用

为什么用axiom-lldb：崩溃报告告诉你崩溃的对象是什么，而LLDB告诉你崩溃的原因。

调用:

skills/lldb.md

16. Runtime Console Capture → xclog-ref

16. 运行时控制台捕获 → xclog-ref

Triggers:

Need to see what the app is logging at runtime
App crashes but no crash report (need console output)
Silent failures (network, data, auth) with no UI feedback
Want to capture print()/os_log() output from simulator
Need structured log output for analysis
"What is the app printing?"

Why xclog-ref: Xcode's debug console isn't accessible externally. xclog combines simctl stdout/stderr with

log stream

JSON to capture everything print(), NSLog(), os_log(), and Logger emit — with structured fields (level, subsystem, category) for automated analysis.

Invoke:

/axiom:console

触发场景:

需要查看应用运行时的日志
应用崩溃但无崩溃报告（需要控制台输出）
无UI反馈的静默失败（网络、数据、认证）
希望捕获模拟器的print()/os_log()输出
需要结构化日志输出用于分析
"应用在打印什么？"

为什么用xclog-ref：Xcode的调试控制台无法外部访问。xclog结合simctl标准输出/错误输出与

log stream

JSON，可捕获所有print()、NSLog()、os_log()和Logger输出——并包含结构化字段（级别、子系统、类别）以支持自动化分析。

调用:

/axiom:console

15. Code Signing Issues → code-signing

15. 代码签名问题 → code-signing

Triggers:

"No signing certificate found"
"Provisioning profile doesn't include signing certificate"
errSecInternalComponent in CI
ITMS-90035 Invalid Signature on upload
Ambiguous identity / multiple certificates
Entitlement mismatch or missing capability
Setting up CI/CD code signing (GitHub Actions, fastlane match)
Certificate expired or revoked

Why code-signing: Code signing errors are NEVER code bugs — they are 100% configuration (certificates, profiles, entitlements, keychains). Diagnosing with CLI tools takes 5 minutes vs hours of guessing.

Invoke: See axiom-security (skills/code-signing.md) (workflows) or See axiom-security (skills/code-signing-diag.md) (troubleshooting)

触发场景:

"No signing certificate found"
"Provisioning profile doesn't include signing certificate"
CI中出现errSecInternalComponent
上传时出现ITMS-90035无效签名
身份模糊/多个证书
权限不匹配或缺失功能
设置CI/CD代码签名（GitHub Actions、fastlane match）
证书过期或被吊销

为什么用code-signing：代码签名错误绝不是代码bug——100%是配置问题（证书、配置文件、权限、钥匙串）。使用CLI工具诊断仅需5分钟，而非数小时的猜测。

调用: 参见axiom-security (skills/code-signing.md)（工作流）或参见axiom-security (skills/code-signing-diag.md)（故障排查）

Decision Tree

决策树

Mysterious/intermittent/clean build fails? → xcode-debugging (environment-first)
SPM dependency conflict? → spm-conflict-resolver (Agent)
CocoaPods/other dependency conflict? → build-debugging
Slow build time? → build-performance
Security/privacy/App Store prep? → security-privacy-scanner (Agent)
Want automated build fix (environment-first diagnostics)? → build-fixer (Agent)
Want build time optimization scan? → build-optimizer (Agent)
Modernization/deprecated APIs? → modernization-helper (Agent)
TestFlight crash/feedback? → testflight-triage
Navigating App Store Connect? → app-store-connect-ref
Have a crash log (.ips/.crash)? → crash-analyzer (Agent)
MetricKit setup/parsing? → metrickit-ref
App hang/freeze/watchdog? → hang-diagnostics
Need to reproduce crash interactively / inspect runtime state? → axiom-lldb
Code signing error (certificate, profile, entitlement, Keychain)? → code-signing / code-signing-diag
Need to see runtime console output (print/os_log)? → xclog-ref or
```
/axiom:console
```

疑难/间歇性/干净构建失败？→ xcode-debugging（优先排查环境）
SPM依赖冲突？→ spm-conflict-resolver (Agent)
CocoaPods/其他依赖冲突？→ build-debugging
构建速度缓慢？→ build-performance
安全/隐私/App Store准备？→ security-privacy-scanner (Agent)
需要自动化构建修复（优先环境诊断）？→ build-fixer (Agent)
需要构建时间优化扫描？→ build-optimizer (Agent)
现代化/废弃API？→ modernization-helper (Agent)
TestFlight崩溃/反馈？→ testflight-triage
导航App Store Connect？→ app-store-connect-ref
有崩溃日志(.ips/.crash)？→ crash-analyzer (Agent)
MetricKit设置/解析？→ metrickit-ref
应用挂起/冻结/看门狗终止？→ hang-diagnostics
需要交互式重现崩溃/检查运行时状态？→ axiom-lldb
代码签名错误（证书、配置文件、权限、钥匙串）？→ code-signing / code-signing-diag
需要查看运行时控制台输出(print/os_log)？→ xclog-ref或
```
/axiom:console
```

Anti-Rationalization

常见误区纠正

Thought	Reality
"I know how to fix this linker error"	Linker errors have 4+ root causes. xcode-debugging diagnoses all in 2 min.
"Let me just clean the build folder"	Clean builds mask the real issue. xcode-debugging finds the root cause.
"It's just an SPM issue, I'll fix Package.swift"	SPM conflicts cascade. spm-conflict-resolver analyzes the full dependency graph.
"The simulator is just slow today"	Simulator issues indicate environment corruption. xcode-debugging checks systematically.
"I'll skip environment checks, it compiles locally"	Environment-first saves 30+ min. Every time.
"I'll read the crash report more carefully instead of reproducing"	Crash reports show WHAT crashed, not WHY. Reproducing in LLDB with breakpoints reveals the actual state. axiom-lldb has the workflow.
"I know my certificate is fine, let me check the code"	Code signing errors are NEVER code bugs. 100% configuration. code-signing diagnoses with CLI in 5 min.
"I can't see what the app is logging without Xcode"	xclog captures print() + os_log from the simulator. Structured JSON output with level, subsystem, category. `/axiom:console` .

错误想法	实际情况
"我知道怎么修复这个链接器错误"	链接器错误有4种以上根本原因。xcode-debugging可在2分钟内完成所有诊断。
"我先清理构建文件夹就好"	干净构建会掩盖真实问题。xcode-debugging能找到根本原因。
"这只是SPM问题，我修改Package.swift就行"	SPM冲突会连锁反应。spm-conflict-resolver会分析完整的依赖图。
"今天模拟器只是慢而已"	模拟器问题表明环境已损坏。xcode-debugging会进行系统化检查。
"我跳过环境检查，本地能编译就行"	优先排查环境每次都能节省30分钟以上。
"我仔细读崩溃报告就行，不用重现"	崩溃报告只显示崩溃的对象，不显示原因。在LLDB中通过断点重现才能揭示实际状态。axiom-lldb提供对应的工作流。
"我知道我的证书没问题，我先检查代码"	代码签名错误绝不是代码bug。100%是配置问题。code-signing用CLI工具5分钟就能完成诊断。
"没有Xcode我看不到应用的日志"	xclog可捕获模拟器的print() + os_log输出。包含级别、子系统、类别的结构化JSON输出。执行 `/axiom:console` 即可。

When NOT to Use (Conflict Resolution)

请勿使用场景（冲突处理）

Do NOT use axiom-build for these — use the correct router instead:

Error Type	Correct Router	Why NOT axiom-build
Swift 6 concurrency errors	`/skill axiom-concurrency`	Code error, not environment
SwiftData migration errors	`/skill axiom-data`	Schema issue, not build environment
"Sending 'self' risks data race"	`/skill axiom-concurrency`	Language error, not Xcode issue
Type mismatch / compilation errors	Fix the code	These are code bugs

axiom-build is for environment mysteries, not code errors:

✅ "No such module" when code is correct
✅ Simulator won't boot
✅ Clean build fails, incremental works
✅ Zombie xcodebuild processes
❌ Swift concurrency warnings/errors
❌ Database migration failures
❌ Type checking errors in valid code

请勿使用axiom-build处理以下问题——请使用正确的路由：

错误类型	正确路由	为什么不用axiom-build
Swift 6并发错误	`/skill axiom-concurrency`	代码错误，而非环境问题
SwiftData迁移错误	`/skill axiom-data`	架构问题，而非构建环境问题
"Sending 'self' risks data race"	`/skill axiom-concurrency`	语言错误，而非Xcode问题
类型不匹配/编译错误	修复代码	这些是代码bug

axiom-build用于排查环境疑难问题，而非代码错误：

✅ 代码正确但出现"No such module"
✅ 模拟器无法启动
✅ 干净构建失败，增量构建成功
✅ 僵尸xcodebuild进程
❌ Swift并发警告/错误
❌ 数据库迁移失败
❌ 有效代码中的类型检查错误

Example Invocations

调用示例

User: "My build failed with a linker error" → Invoke:

skills/xcode-debugging.md

(environment-first diagnostic)

User: "Builds are taking 10 minutes" → Invoke:

skills/build-performance.md

User: "SPM won't resolve dependencies" → Invoke:

spm-conflict-resolver

agent

User: "Two packages require different versions of the same dependency" → Invoke:

spm-conflict-resolver

agent

User: "Duplicate symbol linker error" → Invoke:

spm-conflict-resolver

agent

User: "I need to prepare for App Store security review" → Invoke:

security-privacy-scanner

agent

User: "Do I need a Privacy Manifest?" → Invoke:

security-privacy-scanner

agent

User: "Are there hardcoded credentials in my code?" → Invoke:

security-privacy-scanner

agent

User: "How do I migrate from ObservableObject to @Observable?" → Invoke:

modernization-helper

agent

User: "Update my code to use modern SwiftUI patterns" → Invoke:

modernization-helper

agent

User: "Should I still use @StateObject?" → Invoke:

modernization-helper

agent

User: "A beta tester said my app crashed" → Invoke: See axiom-shipping (skills/testflight-triage.md)

User: "I see crashes in App Store Connect but don't know how to investigate" → Invoke: See axiom-shipping (skills/testflight-triage.md)

User: "My crash logs aren't symbolicated" → Invoke: See axiom-shipping (skills/testflight-triage.md)

User: "I need to review TestFlight feedback" → Invoke: See axiom-shipping (skills/testflight-triage.md)

User: "How do I find crashes in App Store Connect?" → Invoke: See axiom-shipping (skills/app-store-connect-ref.md)

User: "Where's the crash-free users metric in ASC?" → Invoke: See axiom-shipping (skills/app-store-connect-ref.md)

User: "How do I export crash data from App Store Connect?" → Invoke: See axiom-shipping (skills/app-store-connect-ref.md)

User: "Analyze this crash log" [pastes .ips content] → Invoke:

crash-analyzer

agent or

/axiom:analyze-crash

User: "Parse this .ips file: ~/Library/Logs/DiagnosticReports/MyApp.ips" → Invoke:

crash-analyzer

agent or

/axiom:analyze-crash

User: "Why did my app crash? Here's the report..." → Invoke:

crash-analyzer

agent or

/axiom:analyze-crash

User: "How do I set up MetricKit to collect crash data?" → Invoke: See axiom-performance (

skills/metrickit-ref.md

)

User: "How do I parse MXDiagnosticPayload?" → Invoke: See axiom-performance (

skills/metrickit-ref.md

)

User: "What's in MXCallStackTree and how do I decode it?" → Invoke: See axiom-performance (

skills/metrickit-ref.md

)

User: "My app hangs sometimes" → Invoke: See axiom-performance (

skills/hang-diagnostics.md

)

User: "The main thread is blocked and UI is unresponsive" → Invoke: See axiom-performance (

skills/hang-diagnostics.md

)

User: "Xcode Organizer shows hang diagnostics for my app" → Invoke: See axiom-performance (

skills/hang-diagnostics.md

)

User: "My app was killed by watchdog during launch" → Invoke: See axiom-performance (

skills/hang-diagnostics.md

)

User: "I have a crash report and need to reproduce it in the debugger" → Invoke:

skills/lldb.md

User: "How do I set breakpoints to catch this crash?" → Invoke:

skills/lldb.md

User: "My build is failing with BUILD FAILED but no error details" → Invoke:

build-fixer

agent or

/axiom:fix-build

User: "Build sometimes succeeds, sometimes fails" → Invoke:

build-fixer

agent or

/axiom:fix-build

User: "How can I speed up my Xcode build times?" → Invoke:

build-optimizer

agent or

/axiom:optimize-build

User: "No signing certificate found when I try to build" → Invoke: See axiom-security (skills/code-signing-diag.md)

User: "errSecInternalComponent in my GitHub Actions CI" → Invoke: See axiom-security (skills/code-signing-diag.md)

User: "How do I set up code signing for GitHub Actions?" → Invoke: See axiom-security (skills/code-signing.md)

User: "What is my app printing to the console?" → Invoke:

/axiom:console

User: "I need to see the simulator console output" → Invoke:

/axiom:console

User: "The app fails silently, no error in the UI" → Invoke:

/axiom:console

用户: "我的构建因链接器错误失败" → 调用:

skills/xcode-debugging.md

（优先环境诊断）

用户: "构建需要10分钟" → 调用:

skills/build-performance.md

用户: "SPM无法解析依赖" → 调用:

spm-conflict-resolver

agent

用户: "两个包需要同一依赖的不同版本" → 调用:

spm-conflict-resolver

agent

用户: "重复符号链接器错误" → 调用:

spm-conflict-resolver

agent

用户: "我需要为App Store安全审核做准备" → 调用:

security-privacy-scanner

agent

用户: "我需要隐私清单吗？" → 调用:

security-privacy-scanner

agent

用户: "我的代码中有硬编码凭据吗？" → 调用:

security-privacy-scanner

agent

用户: "如何从ObservableObject迁移到@Observable？" → 调用:

modernization-helper

agent

用户: "更新我的代码以使用现代SwiftUI模式" → 调用:

modernization-helper

agent

用户: "我还应该用@StateObject吗？" → 调用:

modernization-helper

agent

用户: "Beta测试人员说我的应用崩溃了" → 调用: 参见axiom-shipping (skills/testflight-triage.md)

用户: "我在App Store Connect中看到崩溃，但不知道如何调查" → 调用: 参见axiom-shipping (skills/testflight-triage.md)

用户: "我的崩溃日志未符号化" → 调用: 参见axiom-shipping (skills/testflight-triage.md)

用户: "我需要评审TestFlight反馈" → 调用: 参见axiom-shipping (skills/testflight-triage.md)

用户: "如何在App Store Connect中查找崩溃？" → 调用: 参见axiom-shipping (skills/app-store-connect-ref.md)

用户: "ASC中的无崩溃用户指标在哪里？" → 调用: 参见axiom-shipping (skills/app-store-connect-ref.md)

用户: "如何从App Store Connect导出崩溃数据？" → 调用: 参见axiom-shipping (skills/app-store-connect-ref.md)

用户: "分析这个崩溃日志" [粘贴.ips内容] → 调用:

crash-analyzer

agent或执行

/axiom:analyze-crash

用户: "解析这个.ips文件: ~/Library/Logs/DiagnosticReports/MyApp.ips" → 调用:

crash-analyzer

agent或执行

/axiom:analyze-crash

用户: "我的应用为什么崩溃？这是报告..." → 调用:

crash-analyzer

agent或执行

/axiom:analyze-crash

用户: "如何设置MetricKit来收集崩溃数据？" → 调用: 参见axiom-performance (

skills/metrickit-ref.md

)

用户: "如何解析MXDiagnosticPayload？" → 调用: 参见axiom-performance (

skills/metrickit-ref.md

)

用户: "MXCallStackTree包含什么内容，如何解码？" → 调用: 参见axiom-performance (

skills/metrickit-ref.md

)

用户: "我的应用有时会挂起" → 调用: 参见axiom-performance (

skills/hang-diagnostics.md

)

用户: "主线程被阻塞，UI无响应" → 调用: 参见axiom-performance (

skills/hang-diagnostics.md

)

用户: "Xcode Organizer显示我的应用存在挂起诊断" → 调用: 参见axiom-performance (

skills/hang-diagnostics.md

)

用户: "我的应用在启动时被看门狗终止" → 调用: 参见axiom-performance (

skills/hang-diagnostics.md

)

用户: "我有崩溃报告，需要在调试器中重现" → 调用:

skills/lldb.md

用户: "如何设置断点来捕获这个崩溃？" → 调用:

skills/lldb.md

用户: "我的构建失败，显示BUILD FAILED但无错误详情" → 调用:

build-fixer

agent或执行

/axiom:fix-build

用户: "构建时而成功时而失败" → 调用:

build-fixer

agent或执行

/axiom:fix-build

用户: "如何加快我的Xcode构建速度？" → 调用:

build-optimizer

agent或执行

/axiom:optimize-build

用户: "构建时提示找不到签名证书" → 调用: 参见axiom-security (skills/code-signing-diag.md)

用户: "我的GitHub Actions CI中出现errSecInternalComponent" → 调用: 参见axiom-security (skills/code-signing-diag.md)

用户: "如何为GitHub Actions设置代码签名？" → 调用: 参见axiom-security (skills/code-signing.md)

用户: "我的应用在控制台打印了什么？" → 调用:

/axiom:console

用户: "我需要查看模拟器的控制台输出" → 调用:

/axiom:console

用户: "应用静默失败，UI无错误提示" → 调用:

/axiom:console