Axiom Shipping

Shipping & App Store

You MUST use this skill when preparing to submit ANY app, handling App Store rejections, or working on release workflow.

<!-- AXIOM_AUDITOR_INLINE_BEGIN — auto-maintained by scripts/build-inlined-auditors.ts; do not hand-edit -->

Not on Claude Code? Where this router says "Launch some-auditor agent", read that auditor's file in this suite and follow it inline — the same procedure, needing only file search and read. Homed in another suite: axiom-integration/skills/iap-auditor.md, axiom-security/skills/security-privacy-scanner.md. Agents that need Bash — builds, tests, simulators, crash symbolication — stay Claude Code-only; there is no inline equivalent for those.

<!-- AXIOM_AUDITOR_INLINE_END -->

When to Use

Use this skill 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/WWDC26 App Store Connect changes
• First-time submission workflow

Quick Reference

Routing Logic

1. Pre-Submission Preparation → 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.

Reference: skills/app-store-submission.md

2. Metadata, Guidelines, and API Reference → 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 and WWDC26 changes to App Store Connect

Why app-store-ref: 11-part reference covering every metadata field, guideline, and compliance requirement with exact specifications.

Reference: skills/app-store-ref.md

3. Rejection Troubleshooting → app-store-diag

Triggers:

• "My app was rejected"
• "Guideline 2.1 rejection"
• "Binary was rejected"
• Guideline 4.2 or 4.3 rejection (app too simple, web wrapper, spam, duplicate)
• Guideline 1.x rejection (objectionable content, UGC moderation, Kids category)
• How to respond to a rejection
• Writing an appeal
• Understanding rejection messages
• Third or repeated rejection
• Resolution Center communication

Why app-store-diag: 9 diagnostic patterns mapping rejection types to root causes and fixes, including subjective rejections (4.2/4.3, 1.x). Includes appeal writing guidance and crisis scenario for repeated rejections.

Reference: skills/app-store-diag.md

4. Privacy & Security Compliance → 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

5. IAP Review Issues → 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

6. Screenshot Validation → screenshot-validator (Agent)

Triggers:

• "Check my App Store screenshots"
• "Are my screenshots the right dimensions?"
• "Validate screenshots before submission"
• "Review my marketing screenshots"
• Screenshot content or dimension questions

Why screenshot-validator: Multimodal agent that visually inspects each screenshot for placeholder text, wrong dimensions, debug artifacts, broken UI, and competitor references. Catches issues that manual review misses.

Invoke: Launch screenshot-validator agent or /axiom:audit screenshots

7. Programmatic ASC Access → asc-mcp

Triggers:

• "Automate App Store Connect"
• "Submit build programmatically"
• "Manage TestFlight from Claude"
• "Respond to reviews via API"
• "Set up asc-mcp"
• "Distribute to TestFlight groups via MCP"
• "Create a new version without opening ASC"