Back to Details

axiom-shipping

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Shipping & App Store Router

应用发布与App Store路由指南

You MUST use this skill when preparing to submit ANY app, handling App Store rejections, or working on release workflow.
在准备提交任何应用、处理App Store拒稿或优化发布工作流时，必须使用此技能。

When to Use

适用场景

Use this router when you encounter:
  • Preparing an app for App Store submission
  • App Store rejection (any guideline)
  • Metadata requirements (screenshots, descriptions, keywords)
  • Privacy manifest and nutrition label questions
  • Age rating and content classification
  • Export compliance and encryption declarations
  • EU DSA trader status
  • Account deletion or Sign in with Apple requirements
  • Build upload and processing issues
  • App Review appeals
  • WWDC25 App Store Connect changes
  • First-time submission workflow
当你遇到以下情况时，请使用此路由：
  • 为App Store提交准备应用
  • App Store拒稿（违反任何审核指南）
  • 元数据要求（截图、描述、关键词）
  • 隐私清单和无障碍营养标签相关问题
  • 年龄分级与内容分类
  • 出口合规与加密声明
  • 欧盟DSA商家身份认证
  • 账号删除或"通过Apple登录"要求
  • 构建版本上传与处理问题
  • App审核申诉
  • WWDC25中App Store Connect的更新
  • 首次提交工作流

Routing Logic

路由逻辑

1. Pre-Submission Preparation → app-store-submission

1. 提交前准备 → app-store-submission

Triggers:
  • "How do I submit my app?"
  • "What do I need before submitting?"
  • Preparing for first submission
  • Pre-flight checklist needed
  • Screenshot requirements
  • Metadata completeness check
  • Encryption compliance questions
  • Accessibility Nutrition Labels
  • Privacy manifest requirements for submission
Why app-store-submission: Discipline skill with 8 anti-patterns, decision trees, and pressure scenarios. Prevents the mistakes that cause 90% of rejections.
Invoke: 
/skill axiom-app-store-submission
触发场景：
  • "我该如何提交我的应用？"
  • "提交前我需要准备什么？"
  • 首次提交准备
  • 需要提交前检查清单
  • 截图要求
  • 元数据完整性检查
  • 加密合规问题
  • 无障碍营养标签
  • 提交所需的隐私清单要求
选择app-store-submission的原因：该技能包含8种反模式、决策树和压力场景模拟，可避免导致90%拒稿的常见错误。
调用方式：
/skill axiom-app-store-submission

2. Metadata, Guidelines, and API Reference → app-store-ref

2. 元数据、审核指南与API参考 → app-store-ref

Triggers:
  • "What fields are required in App Store Connect?"
  • "What's the max length for app description?"
  • Specific guideline number lookup
  • Privacy manifest schema details
  • Age rating tiers and questionnaire
  • IAP submission metadata
  • EU DSA compliance details
  • Build upload methods
  • WWDC25 changes to App Store Connect
Why app-store-ref: 10-part reference covering every metadata field, guideline, and compliance requirement with exact specifications.
Invoke: 
/skill axiom-app-store-ref
触发场景：
  • "App Store Connect中需要填写哪些必填字段？"
  • "应用描述的最大长度是多少？"
  • 特定审核指南编号查询
  • 隐私清单Schema详情
  • 年龄分级层级与问卷
  • IAP提交元数据
  • 欧盟DSA合规细节
  • 构建版本上传方式
  • WWDC25对App Store Connect的更新
选择app-store-ref的原因：包含10部分参考内容，覆盖所有元数字段、审核指南和合规要求的具体规范。
调用方式：
/skill axiom-app-store-ref

3. Rejection Troubleshooting → app-store-diag

3. 拒稿排查 → app-store-diag

Triggers:
  • "My app was rejected"
  • "Guideline 2.1 rejection"
  • "Binary was rejected"
  • How to respond to a rejection
  • Writing an appeal
  • Understanding rejection messages
  • Third or repeated rejection
  • Resolution Center communication
Why app-store-diag: 7 diagnostic patterns mapping rejection types to root causes and fixes. Includes appeal writing guidance and crisis scenario for repeated rejections.
Invoke: 
/skill axiom-app-store-diag
触发场景：
  • "我的应用被拒了"
  • "违反指南2.1被拒"
  • "二进制包被拒"
  • 如何回复拒稿通知
  • 撰写申诉信
  • 理解拒稿通知内容
  • 第三次或多次拒稿
  • 解决中心沟通技巧
选择app-store-diag的原因：包含7种诊断模式，可将拒稿类型映射到根本原因和修复方案，还包括申诉信撰写指导和多次拒稿的危机处理方案。
调用方式：
/skill axiom-app-store-diag

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

4. 隐私与安全合规 → security-privacy-scanner (Agent)

Triggers:
  • "Scan my code for privacy issues before submission"
  • Hardcoded API keys or secrets
  • Missing privacy manifest
  • Required Reason API declarations
  • ATS violations
Why security-privacy-scanner: Autonomous agent that scans for security vulnerabilities and privacy compliance issues that cause rejections.
Invoke: Launch 
security-privacy-scanner
agent or 
/axiom:audit security
触发场景：
  • "提交前帮我扫描代码中的隐私问题"
  • 硬编码的API密钥或机密信息
  • 缺失隐私清单
  • 必需的Reason API声明
  • ATS违规
选择security-privacy-scanner的原因：自主Agent，可扫描导致拒稿的安全漏洞和隐私合规问题。
调用方式：启动
security-privacy-scanner
Agent或
/axiom:audit security

5. IAP Review Issues → iap-auditor (Agent)

5. IAP审核问题 → iap-auditor (Agent)

Triggers:
  • IAP rejected or not working
  • Missing transaction.finish()
  • Missing restore purchases
  • Subscription tracking issues
Why iap-auditor: Scans IAP code for the patterns that cause StoreKit rejections.
Invoke: Launch 
iap-auditor
agent
触发场景：
  • IAP被拒或无法正常工作
  • 缺失transaction.finish()
  • 缺失恢复购买功能
  • 订阅追踪问题
选择iap-auditor的原因：扫描IAP代码中可能导致StoreKit拒稿的常见问题。
调用方式：启动
iap-auditor
Agent

Decision Tree

决策树

dot
digraph shipping {
    "Shipping question?" [shape=diamond];
    "Rejected?" [shape=diamond];
    "Need specific specs?" [shape=diamond];
    "IAP issue?" [shape=diamond];
    "Want code scan?" [shape=diamond];

    "app-store-submission" [shape=box, label="app-store-submission\n(pre-flight checklist)"];
    "app-store-ref" [shape=box, label="app-store-ref\n(metadata/guideline specs)"];
    "app-store-diag" [shape=box, label="app-store-diag\n(rejection troubleshooting)"];
    "security-privacy-scanner" [shape=box, label="security-privacy-scanner\n(Agent)"];
    "iap-auditor" [shape=box, label="iap-auditor\n(Agent)"];

    "Shipping question?" -> "Rejected?" [label="yes, about to submit or general"];
    "Rejected?" -> "app-store-diag" [label="yes, app was rejected"];
    "Rejected?" -> "Need specific specs?" [label="no"];
    "Need specific specs?" -> "app-store-ref" [label="yes, looking up field/guideline"];
    "Need specific specs?" -> "IAP issue?" [label="no"];
    "IAP issue?" -> "iap-auditor" [label="yes"];
    "IAP issue?" -> "Want code scan?" [label="no"];
    "Want code scan?" -> "security-privacy-scanner" [label="yes, scan for privacy/security"];
    "Want code scan?" -> "app-store-submission" [label="no, general prep"];
}
Simplified:
  1. App was rejected? → app-store-diag
  2. Need specific metadata/guideline specs? → app-store-ref
  3. IAP submission issue? → iap-auditor (Agent)
  4. Want pre-submission code scan? → security-privacy-scanner (Agent)
  5. General submission preparation? → app-store-submission
dot
digraph shipping {
    "Shipping question?" [shape=diamond];
    "Rejected?" [shape=diamond];
    "Need specific specs?" [shape=diamond];
    "IAP issue?" [shape=diamond];
    "Want code scan?" [shape=diamond];

    "app-store-submission" [shape=box, label="app-store-submission\n(pre-flight checklist)"];
    "app-store-ref" [shape=box, label="app-store-ref\n(metadata/guideline specs)"];
    "app-store-diag" [shape=box, label="app-store-diag\n(rejection troubleshooting)"];
    "security-privacy-scanner" [shape=box, label="security-privacy-scanner\n(Agent)"];
    "iap-auditor" [shape=box, label="iap-auditor\n(Agent)"];

    "Shipping question?" -> "Rejected?" [label="yes, about to submit or general"];
    "Rejected?" -> "app-store-diag" [label="yes, app was rejected"];
    "Rejected?" -> "Need specific specs?" [label="no"];
    "Need specific specs?" -> "app-store-ref" [label="yes, looking up field/guideline"];
    "Need specific specs?" -> "IAP issue?" [label="no"];
    "IAP issue?" -> "iap-auditor" [label="yes"];
    "IAP issue?" -> "Want code scan?" [label="no"];
    "Want code scan?" -> "security-privacy-scanner" [label="yes, scan for privacy/security"];
    "Want code scan?" -> "app-store-submission" [label="no, general prep"];
}
简化版：
  1. 应用是否被拒？→ app-store-diag
  2. 是否需要特定的元数据/审核指南规范？→ app-store-ref
  3. 是否存在IAP提交问题？→ iap-auditor (Agent)
  4. 是否需要提交前代码扫描？→ security-privacy-scanner (Agent)
  5. 通用提交准备？→ app-store-submission

Anti-Rationalization

反合理化误区

ThoughtReality
"I'll just submit and see what happens"40% of rejections are Guideline 2.1 (completeness). app-store-submission catches them in 10 min.
"I've submitted apps before, I know the process"Requirements change yearly. Privacy manifests, age rating tiers, EU DSA, Accessibility Nutrition Labels are all new since 2024.
"The rejection is wrong, I'll just resubmit"Resubmitting without changes wastes 24-48 hours per cycle. app-store-diag finds the root cause.
"Privacy manifests are only for big apps"Every app using Required Reason APIs needs a manifest since May 2024. Missing = automatic rejection.
"I'll add the metadata later"Missing metadata blocks submission entirely. app-store-ref has the complete field list.
"It's just a bug fix, I don't need a full checklist"Bug fix updates still need What's New text, correct screenshots, and valid build. app-store-submission covers it.
错误想法实际情况
"我先提交看看结果再说"40%的拒稿是因为违反指南2.1（材料不完整），app-store-submission可在10分钟内排查这些问题。
"我之前提交过应用，流程我都懂"审核要求每年都会更新。隐私清单、年龄分级层级、欧盟DSA、无障碍营养标签都是2024年新增的要求。
"拒稿是错判，我直接重新提交就行"不做修改重新提交会浪费24-48小时的审核周期，app-store-diag可找到问题根源。
"隐私清单只针对大型应用"自2024年5月起，所有使用Required Reason API的应用都需要隐私清单，缺失会直接导致拒稿。
"元数据我之后再补"缺失元数据会直接阻止提交，app-store-ref包含完整的字段列表。
"只是修复bug，不需要完整检查清单"bug修复更新仍需填写"新功能说明"文本、正确的截图和有效的构建版本，app-store-submission会覆盖这些要求。

When NOT to Use (Conflict Resolution)

禁用场景（冲突解决）

Do NOT use axiom-shipping for these — use the correct router instead:
IssueCorrect RouterWhy NOT axiom-shipping
Build fails before archivingios-buildEnvironment/build issue, not submission
SwiftData migration crashios-dataSchema issue, not App Store
Privacy manifest coding (writing the file)ios-buildsecurity-privacy-scanner handles code scanning
StoreKit 2 implementation (writing IAP code)ios-integrationin-app-purchases / storekit-ref covers implementation
Performance issues found during testingios-performanceProfiling issue, not submission
Accessibility implementationios-accessibilityCode-level accessibility, not App Store labels
axiom-shipping is for the submission workflow, not code implementation:
  • Preparing metadata and compliance → axiom-shipping
  • Writing the actual code → domain-specific router (ios-build, ios-data, etc.)
  • App was rejected → axiom-shipping
  • Code changes to fix rejection → domain-specific router, then back to axiom-shipping to verify
以下场景请勿使用axiom-shipping，请使用对应路由：
问题正确路由不使用axiom-shipping的原因
归档前构建失败ios-build属于环境/构建问题，与提交流程无关
SwiftData迁移崩溃ios-data属于数据架构问题，与App Store无关
隐私清单编码（编写文件）ios-buildsecurity-privacy-scanner负责代码扫描
StoreKit 2实现（编写IAP代码）ios-integration应用内购买/storekit-ref覆盖实现细节
测试中发现性能问题ios-performance属于性能分析问题，与提交流程无关
无障碍功能实现ios-accessibility属于代码层面的无障碍开发，与App Store标签无关
axiom-shipping专注于提交工作流，而非代码实现：
  • 元数据准备与合规检查 → 使用axiom-shipping
  • 代码编写 → 使用对应领域的路由（ios-build、ios-data等）
  • 应用被拒 → 使用axiom-shipping
  • 修复拒稿的代码修改 → 使用对应领域的路由，之后回到axiom-shipping验证

Example Invocations

调用示例

User: "How do I submit my app to the App Store?" → Invoke: 
/skill axiom-app-store-submission
User: "My app was rejected for Guideline 2.1" → Invoke: 
/skill axiom-app-store-diag
User: "What screenshots do I need?" → Invoke: 
/skill axiom-app-store-ref
User: "What fields are required in App Store Connect?" → Invoke: 
/skill axiom-app-store-ref
User: "How do I fill out the age rating questionnaire?" → Invoke: 
/skill axiom-app-store-ref
User: "Do I need an encryption compliance declaration?" → Invoke: 
/skill axiom-app-store-submission
User: "My app keeps getting rejected, what do I do?" → Invoke: 
/skill axiom-app-store-diag
User: "How do I appeal an App Store rejection?" → Invoke: 
/skill axiom-app-store-diag
User: "Scan my code for App Store compliance issues" → Invoke: 
security-privacy-scanner
agent
User: "Check my IAP implementation before submission" → Invoke: 
iap-auditor
agent
User: "What's new in App Store Connect for 2025?" → Invoke: 
/skill axiom-app-store-ref
User: "I need to set up DSA trader status for the EU" → Invoke: 
/skill axiom-app-store-ref
User: "What are Accessibility Nutrition Labels?" → Invoke: 
/skill axiom-app-store-submission
User: "This is my first app submission ever" → Invoke: 
/skill axiom-app-store-submission
用户："我该如何将应用提交到App Store？" → 调用：
/skill axiom-app-store-submission
用户："我的应用因违反指南2.1被拒" → 调用：
/skill axiom-app-store-diag
用户："我需要准备哪些截图？" → 调用：
/skill axiom-app-store-ref
用户："App Store Connect中有哪些必填字段？" → 调用：
/skill axiom-app-store-ref
用户："我该如何填写年龄分级问卷？" → 调用：
/skill axiom-app-store-ref
用户："我需要提交加密合规声明吗？" → 调用：
/skill axiom-app-store-submission
用户："我的应用多次被拒，该怎么办？" → 调用：
/skill axiom-app-store-diag
用户："我该如何申诉App Store拒稿？" → 调用：
/skill axiom-app-store-diag
用户："帮我扫描代码中的App Store合规问题" → 调用：
security-privacy-scanner
agent
用户："提交前检查我的IAP实现" → 调用：
iap-auditor
agent
用户："2025年App Store Connect有哪些新变化？" → 调用：
/skill axiom-app-store-ref
用户："我需要为欧盟设置DSA商家身份吗？" → 调用：
/skill axiom-app-store-ref
用户："什么是无障碍营养标签？" → 调用：
/skill axiom-app-store-submission
用户："这是我第一次提交应用" → 调用：
/skill axiom-app-store-submission