capacitor-plugin-spm-support
Guides the agent through adding Swift Package Manager support to an existing Capacitor plugin. Covers Package.swift, CAPBridgedPlugin conversion, bridge cleanup, and package manifest updates. Do not use for app projects or non-Capacitor plugin frameworks.
What this skill does
# Add Swift Package Manager Support to a Capacitor Plugin Add SPM support to an existing Capacitor plugin so it can be consumed without CocoaPods. ## When to Use This Skill - User wants a plugin to work through Xcode's package manager - User is converting an existing iOS plugin from Obj-C bridge files to bridged Swift registration - User needs the plugin package manifest and file exports updated for SPM ## Procedures ### Step 1: Gather Plugin Information Read these files in the plugin root: - `package.json` - the `.podspec` - the main Swift plugin class under `ios/` Record: - the package name - the pod name - the iOS deployment target - the plugin class name - the JavaScript plugin name - all exposed plugin methods - any third-party CocoaPods dependencies that also need SPM equivalents ### Step 2: Create `Package.swift` Add a `Package.swift` manifest that: - declares the plugin package name - sets the iOS minimum version - points the target at the plugin's iOS source directory - depends on the Capacitor Swift package support package used by the project - adds any resolved third-party SPM packages Keep the target structure aligned with the actual plugin source tree. ### Step 3: Convert the Swift Plugin Class Update the plugin class to conform to `CAPBridgedPlugin`. Add the bridge properties at the top of the class: - `identifier` - `jsName` - `pluginMethods` Preserve each method name and return type exactly as the plugin already exposes them. ### Step 4: Remove Objective-C Bridge Files Delete the old bridge header and implementation files once the Swift bridge is in place. Then clean the Xcode project file so it no longer references them. ### Step 5: Update Package Metadata Update the plugin package manifest so it exports: - the iOS sources - the podspec - `Package.swift` Add an iOS SPM install command if the project maintains script helpers. ### Step 6: Verify Install dependencies with the repository's existing package manager. Then `cd` into the example or test app directory that contains `capacitor.config.*`, run `npx cap sync` (or the repository's equivalent runner) there, and build that same app. ## Error Handling - Start with the Swift package resolver: check the target path and package dependency names first. - Verify bridge registration by matching the class name, `identifier`, and `jsName` against the exported API. - For unsupported CocoaPods dependencies, replace them with SPM-compatible packages or keep CocoaPods for that dependency.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".