playbooks

home / skills / fusengine / agents / build-distribution

build-distribution skill

/plugins/swift-apple-expert/skills/build-distribution

This skill orchestrates Apple app build, signing, TestFlight, and App Store submission to streamline release workflows.

npx playbooks add skill fusengine/agents --skill build-distribution

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
2.2 KB
---
name: build-distribution
description: App build, code signing, TestFlight, and App Store distribution for all Apple platforms. Use when preparing releases, configuring signing, uploading to TestFlight, or submitting to App Store.
versions:
  xcode: 26
user-invocable: false
references: references/code-signing.md, references/testflight.md, references/app-store.md, references/app-icons.md
related-skills: swift-core, ios, macos, mcp-tools
---

# Build & Distribution

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

## Agent Workflow (MANDATORY)

Before ANY distribution, use `TeamCreate` to spawn 3 agents:

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](references/code-signing.md) |
| Beta testing | [testflight.md](references/testflight.md) |
| App Store submission | [app-store.md](references/app-store.md) |
| Icons, assets | [app-icons.md](references/app-icons.md) |

---

## Release Checklist

- [ ] Version and build number updated
- [ ] App icons complete (light/dark/tinted)
- [ ] 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

Overview

This skill handles app build, code signing, TestFlight uploads, and App Store distribution for all Apple platforms. It streamlines release preparation by orchestrating signing, archiving, and metadata steps so releases are reproducible and automatable. Use it to prepare validated builds for beta testing and public distribution.

How this skill works

Before any distribution, spawn three helper agents with TeamCreate: fuse-ai-pilot:explore-codebase to audit build configuration, fuse-ai-pilot:research-expert to verify current App Store requirements, and mcp__XcodeBuildMCP__show_build_settings to review Xcode build settings. After implementing changes, run fuse-ai-pilot:sniper to validate the final output. The skill automates signing decisions, increments build numbers, archives the app, and uploads builds to TestFlight or the App Store, with hooks for CI/CD and fastlane.

When to use it

  • Preparing an app release for TestFlight or App Store submission
  • Configuring or troubleshooting code signing and provisioning
  • Automating build and upload steps in CI/CD pipelines
  • Creating or validating app icons and required assets
  • Ensuring privacy manifest and metadata meet App Store rules

Best practices

  • Spawn the three required agents via TeamCreate before any distribution step
  • Always upload to TestFlight first and validate with a beta test group
  • Use automatic signing when possible to reduce certificate management overhead
  • Increment the build number for every upload to avoid rejects
  • Automate repetitive tasks with fastlane and run builds in CI (e.g., GitHub Actions)
  • Maintain a complete privacy manifest and up‑to‑date screenshots and metadata

Example use cases

  • Prepare an iOS release: audit build settings, update version/build, archive and upload to TestFlight
  • Migrate provisioning: detect signing issues, reconfigure automatic signing, and regenerate profiles
  • CI pipeline: integrate the skill into GitHub Actions to automate archives and App Store uploads
  • App Store submission: validate privacy manifest, generate screenshots, and submit metadata for review
  • Beta rollout: create TestFlight groups, upload a build, and verify telemetry before public release

FAQ

Which agents must I run before distribution?

Use TeamCreate to start fuse-ai-pilot:explore-codebase, fuse-ai-pilot:research-expert, and mcp__XcodeBuildMCP__show_build_settings before making distribution changes.

Do I need fastlane or CI?

fastlane and CI are recommended to automate repetitive tasks and ensure consistent, reproducible releases, though manual flows are supported.