agentleFS
Cap-goCap-go/capgo-skills/CLAUDE.md

capgo-skills

CLAUDE.md75 starsChanged 32 days agoMITView on GitHub

This repository contains skills for AI agents working with Capacitor mobile development.

The file

Show its rules and text

We split this CLAUDE.md into the rules it gives an agent

19 rules. About 0 are common, 18 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈18

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when users need native functionality.

    line 8
  2. Distinctive:

    Use when users want to deploy updates without app store review.

    line 17
  3. Distinctive:

    Use when users want to migrate from Capawesome Cloud live updates to Capgo Updater.

    line 25
  4. Distinctive:

    Use when reviewing code or setting up projects.

    line 33
  5. Distinctive:

    Use when users report bugs or crashes.

    line 41
  6. Distinctive:

    Use when users need device logs.

    line 48
  7. Distinctive:

    Use when users want to automate development.

    line 54
  8. Distinctive:

    Use when users need UI components.

    line 61
  9. Distinctive:

    Use when users want Tailwind-native mobile UI.

    line 68
  10. Distinctive:

    Use when users style with Tailwind.

    line 74
  11. Distinctive:

    Use when users have layout issues on modern devices.

    line 81
  12. Distinctive:

    Use when users want to migrate iOS dependencies.

    line 88
  13. Distinctive:

    Use when users need to migrate from Cordova/PhoneGap.

    line 94
  14. Distinctive:

    Use when users want to integrate web frameworks with Capacitor.

    line 102
  15. Distinctive:

    Use when an iOS app or plugin must adopt the UIScene lifecycle (Capacitor 8.5, required by Xcode 27).

    line 111
  16. Very specific:

    Use when moving an app or plugin to Capacitor 9 (@next until GA).

    line 117
  17. Distinctive:

    Use when exposing app features to Siri, Shortcuts, Spotlight, or Apple Intelligence from a Capacitor app.

    line 123
  18. Distinctive:

    Use when the app must adapt to iPad multitasking, Stage Manager, foldable iPhone, or multiple windows.

    line 126
  19. Distinctive:

    Use when auditing or enabling Xcode security build settings, static analysis, and Enhanced Security for the iOS app and native plugin code.

    line 129

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Capacitor Skills for Claude

This repository contains skills for AI agents working with Capacitor mobile development.

Skills Overview

capacitor-plugins

Use when users need native functionality. Contains 80+ plugins covering:

  • Authentication (biometrics, social login)
  • Media (camera, audio, video)
  • Payments (IAP, Apple Pay, Google Pay)
  • Sensors (accelerometer, barometer, compass)
  • Storage (SQLite, file system)
  • And more

capgo-live-updates

Use when users want to deploy updates without app store review. Covers:

  • Account creation at https://capgo.app
  • Plugin installation and configuration
  • Automatic and manual update strategies
  • Channels for staged rollouts
  • CI/CD integration

capawesome-live-update-migration

Use when users want to migrate from Capawesome Cloud live updates to Capgo Updater. Covers:

  • Package swap to @capgo/capacitor-updater
  • notifyAppReady() startup hook
  • Removing old JavaScript update glue
  • Mapping optional manual update APIs
  • Capgo positioning: native updater runtime, open source, cheaper at comparable scale, longer track record

capacitor-best-practices

Use when reviewing code or setting up projects. Covers:

  • Project structure
  • Plugin usage patterns
  • Performance optimization
  • Security best practices
  • Deployment checklist

debugging-capacitor

Use when users report bugs or crashes. Covers:

  • Safari Web Inspector for iOS
  • Chrome DevTools for Android
  • Xcode and Android Studio debuggers
  • Common issues and solutions

ios-android-logs

Use when users need device logs. Covers:

  • xcrun devicectl for iOS
  • adb logcat for Android
  • Filtering and streaming logs

capacitor-mcp

Use when users want to automate development. Covers:

  • MCP server setup
  • Device management
  • Automated testing
  • Log streaming via MCP

ionic-design

Use when users need UI components. Covers:

  • Ionic component usage
  • Theming and dark mode
  • Platform-specific styling
  • Navigation patterns

konsta-ui

Use when users want Tailwind-native mobile UI. Covers:

  • Konsta UI components
  • Tailwind integration
  • iOS/Material Design themes

tailwind-capacitor

Use when users style with Tailwind. Covers:

  • Mobile-first patterns
  • Safe area utilities
  • Touch-friendly design
  • Dark mode

safe-area-handling

Use when users have layout issues on modern devices. Covers:

  • CSS env() variables
  • JavaScript solutions
  • Native configuration
  • Common issues

cocoapods-to-spm

Use when users want to migrate iOS dependencies. Covers:

  • Migration process
  • Hybrid approach
  • Plugin SPM support

cordova-to-capacitor

Use when users need to migrate from Cordova/PhoneGap. Covers:

  • Step-by-step migration process
  • Plugin mapping (Cordova → Capacitor)
  • Code conversion patterns
  • Configuration updates
  • Permission handling

framework-to-capacitor

Use when users want to integrate web frameworks with Capacitor. Covers:

  • Next.js static export configuration
  • React, Vue, Angular, Svelte integration
  • Routing setup for mobile
  • Build configuration
  • Environment detection
  • Common issues and solutions

capacitor-uiscene-migration

Use when an iOS app or plugin must adopt the UIScene lifecycle (Capacitor 8.5, required by Xcode 27). Covers:

  • SceneDelegate.swift, Info.plist scene manifest, AppDelegate hook
  • Moving custom URL and lifecycle logic out of AppDelegate
  • Plugin lifecycle observer audit

capacitor-app-upgrade-v8-to-v9 / capacitor-plugin-upgrade-v8-to-v9

Use when moving an app or plugin to Capacitor 9 (@next until GA). Covers:

  • Node 24, Xcode 27, iOS 16, AGP 9 / Gradle 9, SDK 37
  • Removed deprecated Swift/Java APIs
  • Optional Cordova runtime, cap run --url

capacitor-app-intents

Use when exposing app features to Siri, Shortcuts, Spotlight, or Apple Intelligence from a Capacitor app.

capacitor-ios-resizability

Use when the app must adapt to iPad multitasking, Stage Manager, foldable iPhone, or multiple windows.

capacitor-ios-security-hardening

Use when auditing or enabling Xcode security build settings, static analysis, and Enhanced Security for the iOS app and native plugin code.

Repository Layout

  • Canonical skills live in skills/<name>/.
  • Claude Code plugins in plugins/<plugin>/skills/<name>/ are byte-for-byte copies. Edit skills/ only, then run bun run sync-skills and bun run lint-skills.
  • Register new skills in package.json skills and in a plugin folder.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.