agentleFS
Sign inStart free
MKS-01MKS-01/appscreenmap/.claude/skills/store-requirements/SKILL.md

store-requirements

Skill2 starsChanged 19 days agoMITView on GitHub

Keep AppScreenMap's store rules current — the dated Google Play target-API and App Store SDK / deployment-target requirements in packages/store/.../requirements.json that `appscreenmap store` measures builds against. Use when asked to update, refresh or review the store rules, after a Play Console or Apple announcement, each spring and autumn, when the audit's "rules checked" date is more than ~3 months old, or when `appscreenmap store` says nothing about a deadline you know exists.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep old tiers: the audit hides those beyond the window and still uses them to decide what is met.

    line 33
  2. Very specific:

    Only audit and scan skills are vendored, never development ones.

    line 43
  3. Distinctive:

    Never hand-edit the copies.

    line 47

≈ “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

Store requirements upkeep

appscreenmap store (package packages/store) compares a build's target SDK, compile SDK and minimum SDK (Android) or build SDK, Xcode and deployment target (iOS) with the rules in packages/store/src/appscreenmap/store/requirements.json. It always lists every rule that starts within the next 365 days as upcoming, so the data must stay ahead of the stores. The viewer's source catalogue is apps/viewer/src/insights/sources.ts (owned by the viewer session: tell it what to change).

When

TriggerWhy
April–MayApple raises the minimum SDK / Xcode every April (Xcode and SDK 26 on 2026-04-28); Google publishes the August target-API deadline in spring
31 AugustPlay's target-API deadline; the extension runs to 1 November
After WWDC (June) and the Android release (June)New SDK levels; check what the stores announce next
checked older than ~3 monthsStale data makes a "Compatible" answer untrustworthy

Steps

  1. Read the official pages only, with today's date in mind (these are the sources the refs point at):
  2. Edit requirements.json:
    • New Play level → append {"api": N, "from": "YYYY-MM-DD", "extension_until": "…"} to each affected form factor in android.tiers; update existing_app_min_api if the availability floor moved.
    • Apple → update ios.sdk / ios.deployment (min_major, from, text quoted from the page).
    • A rule neither store has published goes in expected (text only), never in tiers. When the store publishes it, move it to tiers and rewrite expected for the next year.
    • Set checked to today.
    • Keep old tiers: the audit hides those beyond the window and still uses them to decide what is met.
  3. Add a test in packages/store/tests/test_store.py for the new boundary (use the today parameter: a day before the date → upcoming, on it → due/blocked, after the extension → blocked).
  4. Check the fix text in audit.py: the behaviour changes named in the Android target fix (edge-to-edge at 35; large-screen orientation limits ignored, predictive back at 36) should name the level you just added. Read the matching behaviour-change page on developer.android.com first.
  5. Run: uv run pytest -q packages/store && uv run ruff check && uv run ruff format, then uv run appscreenmap-engine store --apk samples/playground-app/apk/playground-v1.apk and read the output. The Playground sets targetSdk/compileSdk in samples/playground-app/app/build.gradle.kts: raise both when a new level is due, rebuild with samples/playground-app/build.sh.
  6. Say what changed: old rule → new rule, the date, and the page you read. If you couldn't reach an official page, leave the data alone and say so.

Related audit skills

Only audit and scan skills are vendored, never development ones. From github.com/android/skills (Apache-2.0, unchanged, pinned in scripts/android-skills.lock): play-policy-insights (Play policy), android-permissions-security, android-intent-security, edge-to-edge (what target 35+ enforces), adaptive (large screens, foldables, resizable windows: what target 36 stops letting apps opt out of). make skills-check reports drift from upstream and make skills-sync copies and re-pins; run it with the spring review. From Apple (Xcode 27, no license, git-ignored): audit-xcode-security-settings, uikit-app-modernization (multi-window and orientation on the 26+ SDKs), via make skills-xcode. Never hand-edit the copies.

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.

Check your setup, free