coin-collection-android-US

Add a new year's coins to all active (ongoing) collection types and bump the database version — the annual maintenance workflow performed when the U.S. Mint issues new coins. Use when asked to add this year's coins, do the annual coin update, or extend ongoing series to a new year. NOT for adding entirely new collection types — use the add-coin-collection skill for that.

Capture a screenshot from a running Android emulator for UI debugging or review using the mobile-mcp MCP server. Use when asked to take a screenshot, capture the current screen, check the UI, show me the app, what does the screen look like, verify a UI change, screenshot for debugging, or screenshot of the emulator. Supports interactive navigation (tap, scroll, type) before capturing. NOT for regenerating the full set of store listing screenshots — use the capture-store-screenshots skill for that.

Perform a database migration to add new coins, fix data, or modify the schema. Use when asked to add coins to an existing collection, bump the database version, do a database upgrade, add yearly coins, fix coin data, or modify the database schema. Covers incrementing DATABASE_VERSION, updating collection upgrade methods, and schema-level changes. NOT for creating an entirely new collection type — use the add-coin-collection skill for that.

Deploy the Android app to Google Play and the Amazon Appstore with this repo's Fastlane lanes. Use when asked to deploy a build, upload an APK to the Play Store or Amazon Appstore, push to the alpha/beta/internal tester track, release to production, wire up supply authentication, configure release signing, or understand and modify the Fastfile deploy lanes and the CI release flow. NOT for generating store screenshots — use the capture-store-screenshots skill — and NOT the annual coin update itself — use the add-yearly-coins prompt.

Run the pre-release verification checklist before triggering the GitHub Actions release workflow. Verifies unit tests, lint, version bump in AndroidManifest.xml, DATABASE_VERSION, store metadata, screenshots, and git state, then reports a summary table. Use when asked to run the release checklist, verify release readiness, or check that everything is ready before a release.

Domain-specific review of uncommitted changes to collection classes, database migrations, or flags — checks migration guards (!fromImport, oldVersion <=), collection-upgrade completeness, checkbox flag round-trip and masks, COIN_IMG_IDS/COLLECTION_TYPES array immutability, and test coverage. Use before committing any change that touches DatabaseHelper migrations, collection classes, or CollectionListInfo flags. NOT a general code review — use /code-review for that.

Run the project's test suites and interpret results. Use when asked to run tests, verify changes, check if tests pass, run unit tests, run lint, run instrumented tests, or validate a change. Covers unit tests (Robolectric), instrumented tests (Espresso), and lint checks with the correct Gradle commands and output locations.

Run a UI sanity check and export/import test against a connected Android emulator using the mobile-mcp MCP server and adb. Covers the two flows Espresso cannot automate (system file picker export/import). Requires a running emulator or connected device and the mobile-mcp server. NOT for general regression testing — the instrumented test suite covers everything else.

Add a new coin collection type to the app. Use when asked to add a new collection, create a new coin type, add a coin series, new coin set, or implement a new collection class. Guides through creating the CollectionInfo subclass, registering it in MainApplication, adding resources, and writing tests. NOT for adding coins to an existing collection — use the database-migration skill for that.

Regenerate the full set of 18 app store screenshots (6 screens x 3 device sizes) for the Coin Collection Android app using the automated Fastlane/Screengrab pipeline. Use when asked to regenerate store screenshots, update app store images, refresh store listings, rebuild all screenshots, run screengrab, or recapture store listing images. NOT for ad-hoc UI debugging screenshots — use the capture-debug-screenshot skill for that.