/build-distribution
Use when preparing an Apple release — code signing, TestFlight upload, App Store submission, or app icons/CI across all platforms.
$ npx -y skills add fusengine/agents --skill build-distribution --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/build-distribution
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when preparing an Apple release — code signing, TestFlight upload, App Store submission, or app icons/CI across all platforms.
SKILL.md
build-distribution.SKILL.mdname: build-distribution
description: Use when preparing an Apple release — code signing, TestFlight upload, App Store submission, or app icons/CI across all platforms.
versions:
xcode: 26
user-invocable: false
references: references/code-signing.md, references/testflight.md, references/app-store.md, references/app-icons.md, references/storekit2.md
related-skills: swift-core, ios, macos, mcp-tools
<objective> Covers app build, code signing, and distribution across all Apple platforms: certificate/profile management, TestFlight beta distribution, App Store submission, app icon/asset preparation, and StoreKit 2 in-app purchases/subscriptions.
Includes a release checklist (version/build number, app icons for light/dark/tinted, 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. </objective>
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) | | In-app purchases, subscriptions | [storekit2.md](references/storekit2.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
Read more
name: build-distribution description: Use when preparing an Apple release — code signing, TestFlight upload, App Store submission, or app icons/CI across all platforms. versions: xcode: 26 user-invocable: false references: references/code-signing.md, references/testflight.md, references/app-store.md, references/app-icons.md, references/storekit2.md related-skills: swift-core, ios, macos, mcp-tools
<objective> Covers app build, code signing, and distribution across all Apple platforms: certificate/profile management, TestFlight beta distribution, App Store submission, app icon/asset preparation, and StoreKit 2 in-app purchases/subscriptions.
Includes a release checklist (version/build number, app icons for light/dark/tinted, 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. </objective>
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) | | In-app purchases, subscriptions | [storekit2.md](references/storekit2.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
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

