Skip to content
Back to skills

Mobile

ASecurity

Capacitor native app guide — Android/iOS toolchain setup (macOS + Linux), build/sign/run commands, on-device testing, Chrome remote profiling, and the store release & kids-compliance checklists. Use before touching anything Android, iOS, or Capacitor related.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 29, 2026
developmentgoshelltesting

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add KyleMit/Splotch --skill mobile --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mobile?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mobile
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kylemit-mobile/badge)](https://www.skillsdirectory.com/skills/kylemit-mobile)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mobile
description: Capacitor native app guide — Android/iOS toolchain setup (macOS + Linux), build/sign/run commands, on-device testing, Chrome remote profiling, and the store release & kids-compliance checklists. Use before touching anything Android, iOS, or Capacitor related.
---

# Splotch — Native App (Capacitor) Guide

Splotch ships as native **Android** and **iOS** apps via [Capacitor](https://capacitorjs.com/),
bundling the same SvelteKit code as a static, offline-first shell. The web app (splotch.art) is
unchanged and still deploys to Netlify.

The guide is `docs/MOBILE/`, split into three files — **read the one that matches your task**:

* **[`docs/MOBILE/native.md`](../../../docs/MOBILE/native.md)** — start here. How the static native
  build works, offline vs. online behavior, dual-layer storage, the data/privacy posture the stores
  ask about, shared store-listing assets, the kids-compliance baseline, and cross-platform
  follow-ups.
* **[`docs/MOBILE/android.md`](../../../docs/MOBILE/android.md)** — Android toolchain setup (macOS +
  Linux), build/sign/run commands, on-device web testing, Chrome remote profiling, and the Google
  Play release + Families-policy checklist.
* **[`docs/MOBILE/ios.md`](../../../docs/MOBILE/ios.md)** — iOS toolchain setup (macOS + Xcode, SPM
  not CocoaPods), build/run commands, Safari Web Inspector, and the App Store release +
  Kids-Category checklist.
* **[`docs/MOBILE/compliance.md`](../../../docs/MOBILE/compliance.md)** — the app-store compliance
  ledger: every implemented guideline with the store's text quoted verbatim, whether each of iOS and
  Android requires it, the decision that answers it, and provenance (ADRs, issues, commits). Read it
  before arguing a store-policy question from memory, and update it when a policy or mitigation
  moves.

Both platforms are active and committed (`android/`, `ios/`). Android builds on macOS or Linux; iOS
requires macOS + Xcode. The `CAPACITOR=true` build env var is the single signal for all
web-vs-native branching (see the root `CLAUDE.md`).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…