agentleFS
chatgptprojectschatgptprojects/clear-code/skills/ios-bootstrap-testflight/SKILL.md

ios-bootstrap-testflight

Skill2.1k starsChanged 7 months agoMITView on GitHub

Scaffold a native iOS app (SwiftUI, no dependencies) from nothing, run it in the Simulator, and archive + upload it to TestFlight entirely from the command line. Bundles working scripts for icon generation, simulator run, and signed upload via the App Store Connect API. Use this whenever the user wants to build, run, ship, or debug an iOS/iPhone/iPad app, mentions Xcode, SwiftUI, .xcodeproj, xcodebuild, simctl, provisioning, code signing, App Store Connect, TestFlight, archiving, or "get this on my phone" — and also when an existing iOS build is failing on icons, signing, teams, destinations, or duplicate build numbers.

3 other projects use a version of this.

Trending

Quiet since April.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the chatgptprojects/clear-code repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check *which* build command failed before assuming the code is broken.

    line 55
  2. Very specific:

    If any of that is missing, references/bootstrap.md has the setup commands in order.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

iOS bootstrap → TestFlight

Two jobs: create an iOS app that builds, and get it onto a real phone. Both are almost entirely CLI. Xcode's UI is only needed for first-time account setup.

Read next

FileWhen
references/bootstrap.mdCreating a new project, or the project won't open/build
references/testflight.mdSigning, archiving, uploading. Holds the user's Team ID and API key details.
references/appstore.mdPublic release — screenshots, metadata, privacy policy, review. Read the 4.3 risk section before the user invests in assets.
references/caveats.mdAnything looks wrong on device — button styling, layout, gestures, animation

Scripts

Copy into the project's workspace/ and run from the project root. They auto-detect the .xcodeproj and scheme, so they work unmodified in any project.

mkdir -p workspace
cp ~/.claude/skills/ios-bootstrap-testflight/scripts/* workspace/
chmod +x workspace/*.sh
ScriptDoes
make_icon.swiftRenders a 1024×1024 App Store icon into the asset catalog
run.shBuild → boot simulator → install → launch
upload_testflight.shBump build number → icon → archive → upload to TestFlight
screenshots.shCaptures App Store screenshots at Apple's exact required sizes
time ./workspace/run.sh                          # test locally
time ./workspace/upload_testflight.sh --validate # archive only, no API key needed
time ./workspace/upload_testflight.sh            # bump + archive + upload

The rule that saves the most time

Never run xcodebuild raw and read the output. It emits thousands of lines and buries the one that matters. Always filter:

xcodebuild ... 2>&1 | grep -E "error:|warning:|BUILD"

A build can print ** BUILD FAILED ** while every Swift file compiled fine — asset catalog and signing failures look identical to code failures in raw logs. Check which build command failed before assuming the code is broken.

Environment expectations

  • Xcode (full app, not Command Line Tools) — xcode-select -p must contain Xcode.app
  • ~40 GB free disk for Xcode + one iOS platform
  • Apple Developer Program membership for TestFlight (free tier cannot upload)

If any of that is missing, references/bootstrap.md has the setup commands in order.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.