cc-mobile-ios

Claude Code — Mobile setups

This folder holds per-stack Claude Code configurations. Each subfolder is a self-contained setup you can drop into (or start from, inside) a project of that stack.

Stacks

• android/ — Kotlin + Jetpack Compose, MVVM + Clean Architecture, Hilt, Retrofit.
• ios/ — Swift + SwiftUI, MVVM + Clean Architecture, @Observable, URLSession.
• kmm/ — Kotlin Multiplatform shared module (Ktor + Koin + shared ViewModels) consumed by native Compose/SwiftUI apps.
• flutter/ — Dart + Flutter, Clean Architecture, flutter_bloc + bloc_concurrency, freezed + fpdart (Either<Failure, T>), typed go_router, get_it, dio + OpenAPI client, drift + sqlcipher. Includes /init-flutter-app for scaffolding a new app end-to-end.

Structure of each stack folder

<stack>/
├── CLAUDE.md               # Project context & conventions (stack-specific)
├── README.md               # Overview of the stack's setup
└── .claude/
    ├── settings.json       # Permissions, env
    ├── agents/             # Specialist subagents
    ├── skills/             # Domain knowledge packs (one per topic)
    └── commands/           # Slash commands

Claude Code picks up CLAUDE.md and everything under .claude/ automatically when you open the folder.

Alongside the stack folders, the repo also ships a Claude Code plugin for each stack under plugins/ and a marketplace manifest at .claude-plugin/marketplace.json. See Distribution via marketplace.

Using a stack

Option A — install the plugin (recommended for teams). Each stack ships as a Claude Code plugin via the cc-mobile marketplace. See Distribution via marketplace below. This gives you the skills, agents, and slash commands (including /init-<stack>-app) without copying files around.

Option B — start a project here. Initialize the project inside the corresponding subfolder, then open that subfolder in Claude Code. /init-<stack>-app will scaffold the whole app (folders, manifests, core/ base classes, routing, tests) with a few clarifying questions.

Option C — bring your own project. Copy the subfolder's CLAUDE.md and .claude/ into the root of your existing project.

Distribution via marketplace

This repo is itself a Claude Code plugin marketplace. .claude-plugin/marketplace.json at the repo root advertises the four stack plugins in plugins/.

Coworkers install once:

/plugin marketplace add <git-url-of-this-repo>
/plugin install cc-mobile-android@cc-mobile
/plugin install cc-mobile-ios@cc-mobile
/plugin install cc-mobile-kmm@cc-mobile
/plugin install cc-mobile-flutter@cc-mobile

Installing just the stacks they work with is fine — they're independent.

Working on a KMM project

KMM is the one stack that needs three plugins together: cc-mobile-kmm covers the shared module only, while the native UI lives in androidApp/ (Compose) and iosApp/ (SwiftUI). Install all three:

/plugin install cc-mobile-kmm@cc-mobile
/plugin install cc-mobile-android@cc-mobile
/plugin install cc-mobile-ios@cc-mobile

A few things to know:

• Use the KMM CLAUDE.md as your project root. Copy plugins/cc-mobile-kmm/CLAUDE.md to your project root — it already references the androidApp/ + iosApp/ layout. The android and ios plugin CLAUDE.md files assume a standalone single-stack repo and will mislead the agent.
• Slash commands are shared by name (/new-feature, /add-usecase, /add-migration, /fix-tests, /upgrade-deps). When invoked unprefixed, Claude Code may pick any of the three. To target a specific stack, use the prefixed form: /cc-mobile-kmm:new-feature, /cc-mobile-android:add-screen, /cc-mobile-ios:add-view.
• Pre-commit hooks are layout-aware. The android plugin's hook skips itself when :app isn't a gradle module (it expects KMM's :androidApp). The ios plugin's hook skips itself when there's no Package.swift / .xcodeproj / .xcworkspace at the repo root. The kmm plugin's hook is the only one that runs in a KMM repo, gating commits on :shared:allTests and :androidApp:lintDebug.
• Agent names never collide — every agent is stack-prefixed (kmm-reviewer, android-ui-engineer, ios-tester). Pick the one that matches the file you're working on.

Getting updates:

/plugin marketplace update cc-mobile

Re-running install on an updated plugin refreshes its skills, agents, and commands. The stack's CLAUDE.md is shipped inside the plugin; if a coworker has dropped a copy into their project root, they should re-copy it when the template evolves (see each plugin's README for the copy step).

Publishing a new version: