SuperAPI AI Directory

build-distribution

General & other

View repository

Updated 10-15 21:48

About this skill

Includes a release checklist (version/build number, layered Icon Composer app icon checked in default/dark/clear/tinted appearances, privacy manifest, release configuration, archive validation, TestFlight testing, screenshots, App Store metadata) and guidance on automating releases with fastlane and CI/CD (e.g. GitHub Actions).

Best practices favor automatic signing, TestFlight testing before any public release, incrementing the build number on every upload, and a mandatory privacy manifest for App Store submission.

Build & Distribution

App build, signing, and distribution for all Apple platforms.

Agent Workflow (MANDATORY)

Before ANY distribution, spawn 3 agents in parallel, one Agent call each with a name:

  1. fuse-ai-pilot:explore-codebase - Check existing build configuration
  2. fuse-ai-pilot:research-expert - Verify latest App Store requirements
  3. mcp__XcodeBuildMCP__show_build_settings - Review build settings

After implementation, run fuse-ai-pilot:sniper for validation.


Overview

When to Use

  • Preparing app for release
  • Configuring code signing
  • Uploading to TestFlight
  • Submitting to App Store
  • Creating app icons
  • CI/CD pipeline setup

Why Build Distribution Skill

Feature Benefit
Automatic signing Simplifies certificate management
TestFlight Beta testing with users
App Store Public distribution
CI/CD Automated releases

Reference Guide

Need Reference
Certificates, profiles code-signing.md
Beta testing testflight.md
App Store submission app-store.md
Icons, assets app-icons.md
In-app purchases, subscriptions storekit2.md

Release Checklist

  • Version and build number updated
  • Layered app icon (Icon Composer) checked in default/dark/clear/tinted appearances, incl. alternate icons (HIG app icons)
  • Privacy manifest (PrivacyInfo.xcprivacy)
  • Release configuration
  • Archive validates
  • TestFlight tested
  • Screenshots updated
  • App Store metadata complete

Best Practices

  1. Automatic signing - Let Xcode manage
  2. TestFlight first - Always beta test
  3. Increment build - Every upload needs new build number
  4. Privacy manifest - Required for App Store
  5. fastlane - Automate repetitive tasks
  6. CI/CD - GitHub Actions for automation