flocon-setup
/flocon-setup
Use when installing Flocon in an Android, Kotlin Multiplatform, Swift (iOS) or Flutter project, or when migrating an existing Flocon integration to a newer SDK version (for example 1.x to 2.0) - adding dependencies, debug-only builds, initialization, plugin installation, and checking that each feature is really captured.
- Author
- openflocon ↗
- Repository
- flocon ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when installing Flocon in an Android, Kotlin Multiplatform, Swift (iOS) or Flutter project, or when migrating an existing Flocon integration to a newer SDK version (for example 1.x to 2.0) - adding dependencies, debug-only builds, initialization, plugin installation, and checking that each feature is really captured.
Original author description
Use when installing Flocon in an Android, Kotlin Multiplatform, Swift (iOS) or Flutter project, or when migrating an existing Flocon integration to a newer SDK version (for example 1.x to 2.0) - adding dependencies, debug-only builds, initialization, plugin installation, and checking that each feature is really captured.
How it works
- 1. Detect the platform first
- 2. Then detect the version, with that platform's rules
- 3. Rules for every platform
- 4. Platform rules
SKILL.md preview
---
name: flocon-setup
description: Use when installing Flocon in an Android, Kotlin Multiplatform, Swift (iOS) or Flutter project, or when migrating an existing Flocon integration to a newer SDK version (for example 1.x to 2.0) - adding dependencies, debug-only builds, initialization, plugin installation, and checking that each feature is really captured.
---
# Setting up or migrating Flocon in a project
Flocon is a debugging SDK: the app talks to Flocon Desktop. This skill puts the SDK in a project, or moves an existing integration to a newer version. It does not debug a running app (that is `flocon-mcp`).
Always follow the docs of the SDK used when they are available: for Kotlin, the repository docs `docs/install-kotlin.md` (install), `docs/connect.md` (connection), `docs/migration.md` (1.x to 2.0) and the feature pages; for Swift, the README of `openflocon/FloconSwift` and its DocC comments; for Flutter, the README of `openflocon/FloconFlutter` and the Dart doc comments of the packages. If this skill and those docs disagree, the docs win; tell the user.
## 1. Detect the platform first
Answer from the project files; ask the user only what the files cannot tell.
| Look for | Platform |
| :--- | :--- |
| `com.android.application` / `com.android.library`, no `kotlin("multiplatform")` | Android |
| `kotlin("multiplatform")` with `commonMain` / `iosMain` | Kotlin Multiplatform (an iOS app consuming the KMP framework is still KMP for Flocon) |
| `*.xcodeproj` / `*.xcworkspace` / `Package.swift`, no Kotlin framework providing Flocon | Swift (iOS / macOS) |
| `pubspec.yaml` with `sdk: flutter` | Flutter (its `android/` and `ios/` folders are generated host apps: use the Flutter rules, not the Android or Swift ones) |
A repository can hold several apps: handle each app with its platform rules.
## 2. Then detect the version, with that platform's rules
**Android / KMP** (Kotlin SDK, `io.github.openflocon` artifacts):
| Look for | Tells you |
| :--- | :--- |
| `io.github.openflocon` in `libs.versions.toml` / `*.gradle.kts` | Flocon already used: read its version |
| `Flocon.initialize(` or `import io.github.openflocon.flocon.plugins.` | Kotlin SDK 1.x |
| `startFlocon(` | Kotlin SDK 2.x |
**Swift** (`openflocon/FloconSwift`): read the version from `Package.resolved` / `project.pbxproj` (revision or version of `FloconSwift`, and `FloconSwiftGrpc`). Do not use the start function as a version marker: the Swift SDK has both `startFlocon { }` and `Flocon.initialize()`. Details in [references/swift.md](references/swift.md).
**Flutter** (`flocon*` packages on pub.dev): read the version of `flocon` in `pubspec.lock`. Do not infer it from the start function. `0.0.x` is the current API, not a legacy one: the future `2.0.0` will have its own migration page in `references/migrations/`. Details in [references/flutter.md](references/flutter.md).
Then pick one path, and read only the file you need:
- No Flocon → install: [references/android.md](references/android.md), [references/kmp.md](references/kmp.md), [references/swift.md](references/swift.md) or [references/flutter.md](references/flutter.md).
- Kotlin Flocon 1.x → migrate: [references/migrations/v1-to-v2.md](references/migrations/v1-to-v2.md).
- Already on the target version → only add the missing plugins from the install page.
A future migration is a new file in `references/migrations/`.
## 3. Rules for every platform
- Work on a branch; do not touch unrelated uncommitted changes (use a separate worktree if the tree is dirty).
- Flocon must never be active in release builds. Say precisely what was delivered: **SDK inactive** in a configuration (nothing starts or intercepts) is not the same as **SDK absent from the binary**. Inspect the real build configurations / variants of the project (they are rarely only Debug and Release).
- Install only the plugins the project really uses; find them by searching the code, do not guess.
- A plugin that is not installed does nothing at runtime, it does not fail the build. After the change, list every plugin call and check each one is installed.
- After finding a configuration point (network client factory, image downloader, analytics provider…), search its callers and check it runs in the app target being tested. A hook in a function only the demo calls covers nothing.
- Do not wrap SDK calls in background tasks "for performance": the logging calls only queue values and send in the background. Measure the app's own mapping cost instead.
- Ending with a green compile is not proof it works: say what was not run (app on a device, connection to Flocon Desktop, Release build, camera…).
- Keep the user's device / simulator data, and do not start or restart Flocon Desktop if the user manages it.
- Never put project, company or app names in docs or skill files you write for Flocon itself.
## 4. Platform rules
**Android / KMP**
- Every real module has a `-no-op` twin with the same API, used in release and in any non-debug variant (dependency substitution for KMP).
- Compile every variant you touched (debug, release, and others such as an internal build). List the Gradle tasks first, their names depend on flavors.
**Swift**
- There is no no-op product. "Inactive in Release" is done with the project's debug compilation condition around imports, calls, types, hooks and menu entries; SPM still links the framework in every configuration. Removing it from the Release binary is a separate, architectural choice: ask once if the user's wording does not settle it.
- `.network` only covers `URLSession.shared`; every other session needs `withFlocon()` on its configuration before the session is created. Background sessions are not instrumented.
- Analytics, feature flags, gRPC, App Group storage and dashboards need explicit wiring: see the topic pages listed in [references/swift.md](references/swift.md).
- Build the touched schemes and configurations with `xcodebuild` (list them with `xcodebuild -list`).
**Flutter**
- There is no no-op package. "Inactive in release" is `if (kDebugMode)` around the start; the packages and their native code stay in the release binary. Removing the Flocon Dart code from it needs a debug-only entry point: ask once if the user's wording does not settle it. See [references/flutter.md](references/flutter.md).
- Network is only captured for clients wrapped with `withFlocon()`; top-level `http.get(...)` and clients created elsewhere are not. Inventory them.
- Use the API of the installed version (`pubspec.lock`): the facade (`Flocon.analytics`, `Flocon.featureFlags`...) and the top-level functions (`floconAnalytics(...)`) are two generations, see [references/flutter-data.md](references/flutter-data.md).
- The host differs per target (`10.0.2.2` Android emulator, `localhost` iOS Simulator / macOS, the computer's IP on a device), and each target needs its permission (`INTERNET`, `NSLocalNetworkUsageDescription`, macOS network entitlement).
- Run `flutter analyze` and build the targets the project ships, debug and release.
Files in this package (12)
- SKILL.md 7 KB
- references/android.md 3 KB
- references/flutter-data.md 5 KB
- references/flutter-network.md 3 KB
- references/flutter.md 7 KB
- references/kmp.md 2 KB
- references/swift-analytics-flags.md 6 KB
- references/swift-connection.md 6 KB
- references/swift-network.md 8 KB
- references/swift-storage.md 3 KB
- references/swift.md 13 KB
- references/migrations/v1-to-v2.md 2 KB
Versions
The database has no other skills named flocon-setup.
Database snapshot: 13.11.2026 · package version 5a2c59ec94d1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90flocon-debug
Use when debugging a mobile app (Android, iOS, KMP) connected to Flocon Desktop - inspecting network calls, mocking a response or error, reading app files, analytics events, feature flags, crashes or SQLite databases. - 100flocon-mcp
Use when debugging a mobile app (Android, iOS, KMP, Flutter) connected to Flocon Desktop - reading the timeline of what the app did, investigating crashes, inspecting network calls, mocking a response or error, simulating a slow or flaky network, reading app files, analytics… - 100agp-9-upgrade
Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects. - 100kmp-build-setup
Configuring the Kotlin Multiplatform Gradle build - the kotlin {} DSL, declaring targets (androidTarget, iosArm64, iosSimulatorArm64, jvm, js, wasmJs), the default source-set hierarchy template (commonMain/androidMain/iosMain, applyDefaultHierarchyTemplate), adding dependencies… - 90mobile-kotlin-multiplatform
Use this skill when the user says 'Kotlin Multiplatform', 'KMP', 'Compose Multiplatform', 'shared Kotlin', 'KMP module', 'expect/actual', 'commonMain', 'KMP project', 'multiplatform library'. Build cross-platform mobile apps with Kotlin Multiplatform sharing business logic,… - 90catalyst-sdk
Catalyst SDKs — initialization patterns, service access, and method reference for Node.js, Web (browser), Python, Java, Android, iOS, and Flutter. Trigger on 'SDK', 'zcatalyst-sdk-node', 'Node.js SDK', 'Web SDK', 'Python SDK', 'Java SDK', 'Android SDK', 'iOS SDK', 'Flutter SDK', or 'initialize SDK'.