Ionic Appflow Migration logo

Ionic Appflow Migration

Organization
Cap-go
ionic-appflow-migration

Guides the agent through migrating an existing Ionic or Capacitor project away from Ionic Appflow. Use when detecting Appflow live updates, cloud builds, or store deployment flows and replacing them with Capgo live updates plus the repository's CI/CD and store publishing setup. Do not use for Ionic Enterprise SDK plugin migration or for setting up a fresh Capacitor project from scratch.

Overview

PublisherCap-go
Repositorycapgo-skills
Skill nameionic-appflow-migration
Stars
71
Forks
4
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Cap-go on GitHub. Read the source before you install it.

Installation

Install the Ionic Appflow Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Cap-go/capgo-skills.git /tmp/capgo-skills
mkdir -p .claude/skills
cp -r /tmp/capgo-skills/plugins/capacitor-app-migrations/skills/ionic-appflow-migration .claude/skills/ionic-appflow-migration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ionic Appflow Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ionic Appflow Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ionic Appflow Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ionic Appflow Migration

Migrate an existing Ionic or Capacitor project away from Ionic Appflow.

When to Use This Skill

  • User is moving off Ionic Appflow
  • The project uses Appflow Live Updates, cloud builds, or store deployment
  • The repository still references ionic appflow, @capacitor/live-updates, or cordova-plugin-ionic

Live Project Snapshot

Detected Appflow-related packages and scripts: !node -e "const fs=require('fs');if(!fs.existsSync('package.json'))process.exit(0);const pkg=JSON.parse(fs.readFileSync('package.json','utf8'));const out=[];for(const section of ['dependencies','devDependencies']){for(const [name,version] of Object.entries(pkg[section]||{})){if(name==='@capacitor/live-updates'||name==='cordova-plugin-ionic'||name.includes('appflow'))out.push(section+'.'+name+'='+version)}}for(const [name,cmd] of Object.entries(pkg.scripts||{})){if(/appflow|ionic cloud|ionic package|live-updates/i.test(cmd))out.push('scripts.'+name+'='+cmd)}console.log(out.join('\n'))"

Possible Appflow config and workflow paths: !find . -maxdepth 4 \( -name '.io-config.json' -o -name 'ionic.config.json' -o -name 'capacitor.config.json' -o -name 'capacitor.config.ts' -o -name 'capacitor.config.js' -o -path './.github/workflows' \)

Migration Strategy

Split the Appflow migration by feature instead of treating it as a single package swap.

  • Live Updates -> capgo-live-updates
  • Native cloud builds -> capacitor-ci-cd
  • Store publishing -> capacitor-app-store

Use this skill to detect what Appflow is doing today, then hand off each feature area to the right skill.

Procedures

Step 1: Detect Appflow Usage

Start from the injected snapshot above, then search more broadly if the migration surface is still unclear.

Search the repository for:

  • ionic appflow
  • @capacitor/live-updates
  • cordova-plugin-ionic
  • dashboard.ionicframework.com
  • appflow.ionic.io

Record whether the project currently uses:

  • live updates
  • cloud/native builds
  • app store deployment automation

Step 2: Migrate Live Updates

If Appflow live updates are in use:

  1. Remove @capacitor/live-updates or cordova-plugin-ionic.
  2. Install and configure Capgo using the capgo-live-updates skill.
  3. Map Appflow channels and rollout behavior onto Capgo channels.
  4. Verify that notifyAppReady() or the equivalent Capgo startup flow is wired correctly.

Do not delete Appflow configuration until the Capgo update path is validated.

Step 3: Replace Cloud Build Automation

If Appflow was building the app in the cloud:

  1. Inspect the existing CI/CD workflow for ionic appflow build.
  2. Replace it with repository-owned automation using the capacitor-ci-cd skill.
  3. Preserve signing inputs, environment variables, and platform-specific build arguments.

Treat Appflow build settings as migration input, not as a runtime dependency.

Step 4: Replace Store Publishing

If Appflow handled TestFlight or Google Play publishing:

  1. Inspect the current deployment flow.
  2. Move that workflow to the repository's publishing pipeline using the capacitor-app-store skill.
  3. Keep bundle identifiers, track selection, and credential handling unchanged unless the user wants a new release process.

Step 5: Clean Up

After each migrated feature is verified:

  • remove Appflow packages and scripts
  • remove obsolete Appflow configuration
  • remove stale CI secrets that are no longer needed

Error Handling

  • For live update migrations, validate rollback behavior before deleting the old Appflow setup.
  • For build migrations, preserve the existing signing path first and only simplify later.
  • For publishing migrations, move one destination at a time so App Store and Play failures stay isolated.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ionic Appflow Migration AI skill do?

Guides the agent through migrating an existing Ionic or Capacitor project away from Ionic Appflow. Use when detecting Appflow live updates, cloud builds, or store deployment flows and replacing them with Capgo live updates plus the repository's CI/CD and store publishing setup. Do not use for Ionic Enterprise SDK plugin migration or for setting up a fresh Capacitor project from scratch.

Why use Ionic Appflow Migration on TypingMind?

Because you install it once and use it with any model. Ionic Appflow Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ionic Appflow Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Cap-go/capgo-skills/tree/main/plugins/capacitor-app-migrations/skills/ionic-appflow-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ionic Appflow Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ionic Appflow Migration?

As many as you like. As long as a model supports skills, you can use Ionic Appflow Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ionic Appflow Migration AI skill free?

It is published on GitHub by Cap-go. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇