メニュー
Upgrade a project that is based on the agentic-mobile-blueprint template. Use when the user asks to check for template updates, upgrade to a newer version, or apply template changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | template-upgrade |
| description | Upgrade a project that is based on the agentic-mobile-blueprint template. Use when the user asks to check for template updates, upgrade to a newer version, or apply template changes. |
This project is based on agentic-mobile-blueprint.
Template releases publish upgrade notes to .agents/skills/template-upgrade/vX.Y.Z.md.
Each file documents only shared infrastructure changes — skills, _shared/ utilities, build config, env vars, deps.
App scaffold files (mobile/app/, example screens) are intentionally excluded.
Read the local version:
cat TEMPLATE_VERSION
Fetch the template's latest version:
https://raw.githubusercontent.com/Ampli-Group/agentic-mobile-blueprint/main/TEMPLATE_VERSION
If local == latest: nothing to do. Stop here and tell the user they are up to date.
Fetch the list of upgrade files from the template:
https://api.github.com/repos/Ampli-Group/agentic-mobile-blueprint/contents/.agents/skills/template-upgrade
This returns a JSON array. Filter for files whose name matches vX.Y.Z.md and whose version is strictly greater than the local version and less than or equal to the latest version. Sort them in ascending semver order (oldest first).
Semver comparison: parse each version as [MAJOR, MINOR, PATCH] integers and compare numerically — do not do lexicographic string comparison.
Example: local = 0.1.0, latest = 0.3.1 → apply v0.1.1.md, v0.2.0.md, v0.3.0.md, v0.3.1.md in that order (only files that actually exist).
For each file to apply, fetch its content:
https://raw.githubusercontent.com/Ampli-Group/agentic-mobile-blueprint/main/.agents/skills/template-upgrade/vX.Y.Z.md
Read the full file before applying anything. Build a complete picture of all changes across all versions first.
Work through the upgrade notes in version order. For each version:
package.json, deno.json, or relevant config files.Key rules while applying:
supabase/functions/_shared/), copy the change directly — these files are not expected to be customised by consuming projects..agents/skills/), merge carefully — the project may have added its own skills.AGENTS.md, apply the described changes as a patch rather than overwriting — the project will have customised it..env.local files and remind the user to fill them in. Run mise run configure if the upgrade notes say to.mobile/app/, example screens, or maestro/ flows — these are owned by the consuming project..agents/skills/template-upgrade/vX.Y.Z.md files into the project. These release notes live only in the blueprint repo. Fetch and read them from GitHub; do not write them to disk..agents/skills/template-release/ into the project. The release skill is for cutting blueprint releases — it has no use in a consuming project.After applying all changes:
echo "X.Y.Z" > TEMPLATE_VERSION
Summarise:
If the user just wants to see what would change without applying it:
Cut a new template version — bump TEMPLATE_VERSION, write upgrade notes, tag and publish a GitHub release. Use when releasing a new version of the agentic-mobile-blueprint template.
Set up Apple Developer account, App Store Connect app listing, and EAS credentials for iOS builds and TestFlight distribution. Use when creating a new iOS app, configuring Apple certificates/provisioning, or troubleshooting App Store Connect submission issues.
Explains how EAS Build and Submit work together for App Store and Google Play deployment. Use when configuring eas.json, troubleshooting mobile builds/submissions, or understanding version management, submit profiles, and the build-then-submit pipeline.
Supabase Edge Function development patterns with Deno runtime. Use when creating, modifying, or debugging edge functions. For Langfuse tracing see the langfuse-tracing skill. For Sentry error handling see the sentry-integration skill.
Next.js frontend app development patterns with App Router, Tailwind CSS v4, Zustand, and TanStack Query. Use when creating pages, components, or API routes in the frontend app.
Set up Google Play Console, create an Android app listing, configure EAS credentials for Android builds, and set up the service account for CI/CD submissions. Use when publishing a new Android app, setting up Play Store automation, or troubleshooting AAB uploads.