capacitor-app-upgrades
Guides the agent through upgrading a Capacitor app project to a newer major version. Supports upgrades from Capacitor 4 through 8, including multi-version jumps. Performs all upgrade steps manually — does not use the interactive `npx cap migrate` command. Do not use for plugin library upgrade or non-Capacitor mobile frameworks.
What this skill does
# Capacitor App Upgrade Upgrade a Capacitor app project to a newer major version (4→5, 5→6, 6→7, or 7→8). ## Prerequisites | Target Version | Node.js | Xcode | Android Studio | | -------------- | ------- | ------- | ------------------------------- | | 5 | 16+ | 14.1+ | Flamingo 2022.2.1+ (Java 17) | | 6 | 18+ | 15.0+ | Hedgehog 2023.1.1+ | | 7 | 20+ | 16.0+ | Ladybug 2024.2.1+ (Java 21) | | 8 | 22+ | 26.0+ | Otter 2025.2.1+ | ## Procedures ### Step 1: Detect Current Version Read `@capacitor/core` version from `package.json` (`dependencies` or `devDependencies`). Determine the current major version. Ask the user for the target version. Default to the latest (8) if not specified. ### Step 2: Execute Upgrade **Do not run `npx cap migrate`.** It is an interactive command that cannot be invoked by an agent. Always apply each upgrade manually using the steps in the corresponding reference file. For each major version jump between the current and target version, apply the corresponding upgrade guide **sequentially**: | Current → Target | Reference | | ---------------- | ------------------------------------ | | 4 → 5 | `references/upgrade-v4-to-v5.md` | | 5 → 6 | `references/upgrade-v5-to-v6.md` | | 6 → 7 | `references/upgrade-v6-to-v7.md` | | 7 → 8 | `references/upgrade-v7-to-v8.md` | For multi-version jumps (e.g., 5 → 8), apply each upgrade in order: 1. Read and apply `references/upgrade-v5-to-v6.md` 2. Run `npx cap sync`, build, and verify on both platforms 3. Read and apply `references/upgrade-v6-to-v7.md` 4. Run `npx cap sync`, build, and verify on both platforms 5. Read and apply `references/upgrade-v7-to-v8.md` 6. Run `npx cap sync`, build, and verify on both platforms Do **not** skip intermediate versions. ### Step 3: Final Verification After completing all upgrade steps: ```bash npx cap sync npx cap run android npx cap run ios ``` ## Error Handling * If Android build fails after upgrade, run **Tools > AGP Upgrade Assistant** in Android Studio. * If iOS build fails, verify the deployment target matches the target version requirements in the reference file. * If Gradle property syntax warnings appear (v8+), search all `.gradle` files for property assignments without `=` and update them. * If a multi-version upgrade fails mid-way, fix the current version step before proceeding to the next. ## Related Skills - **`capacitor-app-development`** — For general Capacitor development topics, troubleshooting, and best practices after completing the upgrade. - **`capacitor-plugin-upgrades`** — If the project contains Capacitor plugins that also need upgrading, use this skill after the app upgrade. - **`capacitor-plugins`** — For installing or reconfiguring plugins after the app upgrade. - **`ionic-app-upgrades`** — If the project uses the Ionic Framework UI library, the Ionic version may also need upgrading alongside Capacitor.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.