Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Harness Mobile
Fastlane lane conventions for iOS + Android store delivery — beta/release/internal/production lanes, screenshot lanes, match signing with an App Store Connect API key kept out of env, scoped Play service accounts, and two-key gating on release lanes. Use when authoring a Fastfile or running fastlane to build, sign, or upload mobile binaries.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harness-mobile:addon-fastlaneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `ios beta` → build + upload to TestFlight (internal group).
Fastfile)ios beta → build + upload to TestFlight (internal group).ios release → build + upload to App Store, await review.android internal → build AAB + upload to Play Internal Testing.android production → build AAB + upload to Play Production track.ios screenshots → snapshot with Snapfile.android screenshots → screengrab with Screengrabfile.match with App Store Connect API key (.p8) stored in ~/.appstoreconnect/, NOT in env.--json_key; service account scoped to the one app.ios release and android production lanes refuse to run without safety.two_key=true (or a typed token). Encoded in the Fastfile template.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-mobileBlocks Edit/Write/Bash actions until Claude investigates importers, data schemas, and user instructions. Improves output quality by forcing concrete facts before edits.