mobile-testflight
Skill7 starsChanged 8 days agoMITView on GitHub
Build and submit the native SwiftUI FalconDeck iOS app to the existing TestFlight listing. Use when asked to push, ship, or release a TestFlight build.
In this repository19 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/autoreview/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- autoreviewSkill
- axe-ios-simulatorSkill
- desktop-mac-releaseSkill
- dopplerSkill
- github-reference-finderSkill
- goal-writerSkill
- humanizerSkill
- ntfySkill
- publish-reportSkill
- qa-spiderSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- verified-bug-campaignSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Verify Apple processing and access for the existing TestFlight tester group.
- Distinctive: line 33
If submission hangs, check https://status.expo.dev/ for EAS Submit outages.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Mobile TestFlight push
The SwiftUI app in ios-native-pilot replaces the existing iOS app:
com.falcondeck.mobile, App Store Connect 6760899257. Use its Release
configuration. Debug retains the separate pilot identifier. Read
ios-native-pilot/README.md for the archive/export path.
Query App Store Connect for the latest uploaded build and marketing version before choosing the next version/build. Run the relevant simulator checks and repo-required review, regenerate with XcodeGen, then archive and export the native app with Xcode App Store Connect signing. Use existing authorized credentials; keep private keys in a private temporary directory and remove them when finished. Do not print credentials.
Submit the exported native IPA from apps/mobile:
eas submit --platform ios --profile preview-testflight \
--path ../../ios-native-pilot/artifacts/<export>/FalconDeckNative.ipa \
--non-interactive --waitNotes:
--platform iosis required in non-interactive mode.- The version/build is set by the native Xcode project; submission does not increment it.
- Verify Apple processing and access for the existing TestFlight tester group.
- Return the version/build and TestFlight/submission link.
- If submission hangs, check https://status.expo.dev/ for EAS Submit outages.
- Expo build and OTA commands target the legacy React Native app. Use those only when the user explicitly requests a legacy Expo build; they do not ship native changes.
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
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.

