migrate-app-to-flows

This skill orchestrates the migration of a legacy Cognite Dune application to the newer Flows app hosting infrastructure (appsApi). It solves a multi-step, error-prone migration by walking through each area in order and skipping anything already in the correct state. It triggers on requests like 'migrate to Flows', 'move from dune to flows', or 'migrate legacy app', and is scoped to a defined set of tools (Read, Glob, Grep, Edit, Write, Bash).

The workflow starts with an audit that reads app.json, package.json, vite.config.ts, and manifest.json and reports a concise before-state summary. It then updates app.json to use the appsApi infra value and fixes the legacy singular 'deployment' object into the required plural 'deployments' array. It delegates all authentication wiring to a companion setup-flows-auth skill, then creates or updates manifest.json to declare a Content Security Policy: it greps the source for outbound calls (fetch, axios, XMLHttpRequest) and populates network permissions with proper origin sources and CSP directives, flagging dynamic URLs for manual review. Finally it rewrites deploy scripts from the old Dune commands to '@cognite/cli' and runs a final grep to surface any lingering Dune references, ending with a completion report and next steps.

It targets Cognite platform developers maintaining Dune-era apps who need to move to Flows hosting. Use cases include one-shot migrations of proof-of-concept apps, standardizing deployment configuration across a team's apps, and ensuring network permissions are correctly declared for the Flows CSP. The Bash usage is limited to read-only grep scans and standard CLI deploy commands, not destructive operations.