Skip to content

hashgraph-online/awesome-codex-plugins / plugins/ariaxhan/kernel-claude/skills/app-dev

app-dev

Unverified

Mobile/web build pipeline: fastlane-first local builds, store submission, pre-submission checklists. Triggers: app, mobile, store submission, deploy app, fastlane, expo, react native, flutter.

POLICY: fastlane, never EAS

Local fastlane builds (gym/gradle + deliver/supply) are the default for all native build + store submission. EAS/cloud builders are a deliberate, stated exception — never a silent reach (rule: CodingVault/.claude/CLAUDE.md "Mobile builds"). If the project ships its own build CLI (e.g. modelmind's ./mm), extend that — don't bolt on a second pipeline.

FLOW

  1. Load source files — Read fastlane/Fastfile, project build config (build.gradle, *.xcodeproj, app.config.*), any project build CLI, CI config. If no fastlane setup exists, fastlane init and commit the scaffold. (gate: build tooling identified)
  2. Identify environment — dev / staging / production. API endpoints, signing creds, feature flags are environment-specific. Signing material lives in keychain or gitignored _meta/keys/ listed in the secrets-backup manifest — never in the tree. (gate: no hardcoded keys or shared signing certs)
  3. Build locally — iOS: fastlane gym (or project lane). Android: fastlane lane wrapping gradle bundleRelease → signed AAB. (gate: build completes without error)
  4. JS-only vs native change — JS-only updates may use the project's own OTA mechanism if one exists; any native change requires a full store build. (gate: OTA never used for native changes)
  5. Run pre-submission checklist (gate: all items pass before submitting):
    • Privacy manifests (iOS): all required API reasons declared
    • iOS third-party SDKs on Apple's required list: bundled privacy manifests present; binary SDKs signed
    • Permissions: only what you use, with clear usage descriptions
    • Metadata: screenshots current, descriptions accurate (fastlane/metadata/)
    • Version/build numbers: incremented correctly
    • Physical device testing: tested on real device (not simulator)
    • Deep links: universal links / app links verified
    • Push notifications: working in production config
    • Crash-free rate: > 99% on staging before promoting
    • Bundle size: within limits, no large accidental assets
    • iOS toolchain: built with Xcode 26+ / iOS 26 SDK or later (uploads rejected otherwise since 2026-04-28) and deployment target iOS 13+ (since 2026-09-09) (Apple requirements)
    • Android targetSdk 36+ for new apps and updates (since 2026-08-31; Wear OS/Auto 35, TV/XR 34; existing apps keep 35+ to stay available to new users) (Play target API)
    • Android 16 KB page-size support on 64-bit devices: inspect bundled native libraries (including SDKs) and test in a 16 KB environment (Android guidance)
    • Offline behavior: handles no-network gracefully
  6. iOS submission — fastlane deliver/pilot: TestFlight (internal → external) → App Store review. Before external testing, provide TestFlight test information and submit the first build for TestFlight App Review; testing starts after approval. Later builds for the same version may also require review. (gate: metadata complete; privacy manifests present)
  7. Android submission — fastlane supply with a Play service-account JSON: internal → closed/open beta → staged production rollout starting at 5-10%. (gate: data safety form complete; crash rate stable)
  8. Monitor rollout — watch crash rates before expanding staged rollout. Rollback: halt rollout in console; OTA rollback via the project's own mechanism if present. (gate: crash-free rate holds > 99%)

ANTI-PATTERNS (block on detection)

  • Reaching for EAS / cloud builders without a stated, justified exception
  • Hardcoded API keys in builds → keychain or env injection at build time
  • OTA update for native changes → must be a store build
  • Skipping physical device testing → simulators miss real-world issues
  • 0-to-100% rollout on Android → start at 5-10%
  • Shared signing certs across environments → separate keystores

REFERENCE

Deep rationale, environment config patterns, iOS/Android submission detail: skills/app-dev/reference/app-dev-research.md

ON COMPLETE

agentdb write-end '{"skill":"app-dev","platform":"ios|android|both","gate":"submitted|built|blocked","store_ready":true}'

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall