使用公理
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
<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 -->
章节与文件索引
按说明文件中的顺序排列。
规则
危险信号——iOS 特定的合理化
iOS开发技能优先
iOS项目检测
使用 Axiom 路由器技巧
文件/命令 -> .xcodeproj · .xcworkspace · /skill axiom-swift-concurrency · /axiom:fix-build · /axiom:audit-accessibility
内容校验值 -> 7a184fc09628
当前原文的自动摘译,尚未人工审校。
规则
在处理 iOS/Swift 项目时,在做出任何回应之前先检查 Axiom 技能。这包括澄清问题。即使只有 1% 的机会也意味着要先检查。
危险信号——iOS 特定的合理化
这些想法意味着停止——你正在合理化: 想法·现实“这只是一个简单的构建问题”·构建失败有模式。首先检查 ios-build。 “我可以快速修复这个 SwiftUI 错误” · SwiftUI 问题隐藏着陷阱。首先检查 ios-ui。 “让我添加这个数据库列” · 架构更改存在数据丢失的风险。首先检查 ios 数据。
iOS开发技能优先
当可以应用多种 Axiom 技能时,请使用此优先级: 环境/构建优先 (ios-build) — 在调试代码之前修复环境 架构模式(ios-ui、axiom-ios-data、axiom-ios-concurrency) — 这些模式决定如何构建解决方案 实现细节(ios-integration、axiom-ios-ai、axiom-ios-vision) — 这些指导特定功能工作 示例:
iOS项目检测
Axiom 技能适用于以下情况: 工作目录包含
.xcodeproj或.xcworkspace用户提及 iOS、Swift、Xcode、SwiftUI、UIKit 用户询问 Apple 框架(SwiftData、CloudKit 等) 用户报告 iOS 特定错误(并发、内存、构建失败)使用 Axiom 路由器技巧
Axiom 使用路由器技能进行逐步披露:首先检查适当的路由器技能(ios-build、axiom-ios-ui、axiom-ios-data 等)。路由器将调用您实际需要的专业技能。完全遵循专业技能不要跳过路由器。路由器具有决策逻辑来选择正确的专业技能。