ionic-app-upgrades
Guides the agent through upgrading an Ionic Framework app to a newer major version. Supports upgrades from Ionic 4 through 8, including multi-version jumps. Covers framework-specific migration steps for Angular, React, and Vue, component breaking changes, CSS variable updates, and browser support changes. Do not use for Capacitor version upgrades (use capacitor-app-upgrades instead), for plugin library upgrades, or for non-Ionic UI frameworks.
What this skill does
# Ionic App Upgrade Upgrade an Ionic Framework app to a newer major version (4 to 5, 5 to 6, 6 to 7, or 7 to 8). ## Prerequisites | Target Version | Angular | React | Vue | | -------------- | -------- | ----- | ------- | | 5 | 8.2+ | 16+ | N/A | | 6 | 12+ | 17+ | 3.0.6+ | | 7 | 14+ | 17+ | 3.0.6+ | | 8 | 16+ | 17+ | 3.0.6+ | ## Procedures ### Step 1: Detect Current Version Read `@ionic/angular`, `@ionic/react`, or `@ionic/vue` version from `package.json` (`dependencies` or `devDependencies`). Determine the current major version and which framework is in use (Angular, React, Vue, or Core/Standalone). Ask the user for the target version. Default to the latest (8) if not specified. ### Step 2: Execute Upgrade For each major version jump between the current and target version, apply the corresponding upgrade guide **sequentially**: | Current to Target | Reference | | ----------------- | ------------------------------------ | | 4 to 5 | `references/upgrade-v4-to-v5.md` | | 5 to 6 | `references/upgrade-v5-to-v6.md` | | 6 to 7 | `references/upgrade-v6-to-v7.md` | | 7 to 8 | `references/upgrade-v7-to-v8.md` | For multi-version jumps (e.g., 5 to 8), apply each upgrade in order: 1. Read and apply `references/upgrade-v5-to-v6.md` 2. Build the project (`npm run build`), fix any errors, and verify the app runs 3. Read and apply `references/upgrade-v6-to-v7.md` 4. Build the project (`npm run build`), fix any errors, and verify the app runs 5. Read and apply `references/upgrade-v7-to-v8.md` 6. Build the project (`npm run build`), fix any errors, and verify the app runs Do **not** skip intermediate versions. ### Step 3: Final Verification After completing all upgrade steps: ```bash npm run build ``` If the project uses Capacitor, also run: ```bash npx cap sync ``` ## Error Handling * If `npm run build` fails after an upgrade step, check the compiler errors. Most errors are caused by removed component properties, renamed CSS variables, or changed event handler signatures documented in the reference files. * If Jest or unit tests fail, check the `transformIgnorePatterns` configuration — Ionic 6+ ships as ES Modules and requires Babel/Jest configuration updates. * If CSS styles break after upgrade, check for removed CSS Shadow Parts and renamed CSS variables in the reference file for that version. * If a multi-version upgrade fails mid-way, fix the current version step before proceeding to the next. * If the project also uses Capacitor and platform builds fail, the Capacitor version may also need upgrading — use the `capacitor-app-upgrades` skill. ## Related Skills - **`capacitor-app-upgrades`** — If Capacitor also needs upgrading alongside Ionic, use this skill for the Capacitor-specific upgrade steps. - **`ionic-app-development`** — General Ionic development guidance. - **`capacitor-plugins`** — For installing or reconfiguring plugins after the app upgrade.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.