Opinionated Claude Code setup for iOS apps — Swift + SwiftUI, MVVM + Clean Architecture, @Observable state holders, URLSession + Codable, SwiftData + Keychain, NavigationStack typed routes. Ships skills, agents, and slash commands including /init-ios-app to scaffold a new app end-to-end.
Add a SwiftData schema migration with a VersionedSchema + MigrationPlan stage and tests.
Add a domain use case with a Swift Testing suite.
Add a single SwiftUI view with its @Observable view model, ViewState, and
1. Run the targeted test set.
Scaffold a fresh iOS app with this project's conventions — Swift 6, SwiftUI, Clean Architecture, Swift Concurrency, SPM-based modules, composition-root DI, URLSession, Keychain, NavigationStack with typed destinations, Swift Testing.
Use PROACTIVELY after any change to a SwiftUI view — new screen, refactored component, typography / interaction tweaks. Reviews against iOS accessibility guidelines: accessibility labels/hints/traits, Dynamic Type, VoiceOver navigation, Reduce Motion, contrast, RTL mirroring. Read-only; does not write code.
Use PROACTIVELY for architectural decisions in a Swift/SwiftUI iOS project — module boundaries, layer responsibilities, whether a new feature belongs in Data/Domain/Presentation, when to introduce a use case vs. call a repository directly, how to structure multi-target / multi-package builds, and trade-offs between MVVM, MV, TCA, and Coordinator patterns. Not for writing views or running tests.
Use PROACTIVELY for any Swift Package Manager, Xcode project, or build-system issue. Covers `Package.swift`, Xcode project/scheme quirks, adding/updating dependencies, module resolution errors, linking issues, bitcode/module stability, and build-performance tuning. Trigger on build failures, "add this library", version bumps, or questions about target/module setup.
Use PROACTIVELY when the user reports jank, slow cold start, memory pressure, or before shipping a release build. Proposes a measurement plan (Instruments, MetricKit, Signposts, SwiftUI `Self._printChanges()`) and reads code to identify likely hotspots. Read-only; does not write code.
Use PROACTIVELY for iOS release tasks — `CFBundleShortVersionString` / `CFBundleVersion` bumps, signing & provisioning, App Store metadata, `fastlane match` / `deliver` / `pilot`, `xcodebuild archive` automation, TestFlight, crash mapping uploads. Write-capable; scoped to release-time files.
How MVVM + Clean Architecture is applied in this Swift + SwiftUI codebase. Load when designing a new feature, deciding where code belongs, adding a repository or use case, or reviewing layer boundaries.
iOS accessibility patterns — accessibility labels/hints/values/traits, Dynamic Type, VoiceOver, Reduce Motion, high contrast, RTL mirroring. Load whenever adding or reviewing a SwiftUI screen.
Authoritative blueprint for scaffolding a brand-new iOS app with this project's conventions. Used by /init-ios-app. Contains every file template, placeholder list, feature-flag block, and the procedure to emit a runnable splash.
Dependency injection patterns used in this project — composition root + constructor injection, protocol-oriented design, testable factories, and how DI fits with SwiftUI / @Observable. Load when adding a new type that needs dependencies, wiring a repository, setting up previews, writing tests, or debugging a DI-related crash.
iOS performance patterns — Instruments tracing, SwiftUI `Self._printChanges()`, MetricKit, launch optimization, scroll smoothness, memory pressure, Signposts. Load when investigating jank, cold-start regressions, or shipping a release build.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
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.<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.
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.
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.
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:
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./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.: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.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:
npx claudepluginhub dimitriremoiville/cc-mobile --plugin cc-mobile-iosOpinionated Claude Code setup for Android apps — Kotlin + Jetpack Compose, MVVM + Clean Architecture, Hilt DI, Retrofit + OkHttp + kotlinx.serialization, Room + DataStore. Ships skills, agents, and slash commands including /init-android-app to scaffold a new app end-to-end.
Opinionated Claude Code setup for Kotlin Multiplatform Mobile — shared module with MVVM + Clean Architecture in commonMain, Ktor Client + kotlinx.serialization, Koin DI, shared ViewModels over StateFlow, SQLDelight, multiplatform-settings. Ships skills, agents, and slash commands including /init-kmm-app to scaffold a new shared module end-to-end.
Opinionated Claude Code setup for Flutter apps — Clean Architecture, flutter_bloc + bloc_concurrency, freezed + fpdart (Either<Failure, T>), typed go_router, get_it, dio + OpenAPI client, drift + sqlcipher. Ships skills, agents, and slash commands including /init-flutter-app to scaffold a new app end-to-end.
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
TypeScript/JavaScript full-stack development with NestJS, React, and React Native
Complete AI coding workflow system. Self-correcting memory + persistent FTS5-indexed research wikis + auto-research loop + multi-LLM council on a single SQLite store. 33 skills, 8 agents, 22 commands, 37 hook scripts across 24 events. Cross-agent via SkillKit.
Open-source, local-first Claude Code plugin for token reduction, context compression, and cost optimization using hybrid RAG retrieval (BM25 + vector search), reranking, AST-aware chunking, and compact context packets.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.