---
name: ansight-install
description: Use this skill when installing or configuring Ansight but the app platform has not been selected yet. Inspect the target app, identify whether it is .NET MAUI/.NET mobile, native iOS, native Android, or React Native, then fork into or load the matching platform-specific install skill. Route .NET apps to ansight-install-dotnet, native iOS apps to ansight-install-ios, native Android apps to ansight-install-android, and React Native apps to ansight-install-react-native. Keep `reflect.*` reflection tools as development-time dependencies by default. Do not duplicate platform setup; delegate to the specific skill and continue with that workflow.
---

# Ansight Install Router Skill

Use this skill when the user asks an agent to install or configure Ansight and the prompt does not already name the target SDK.

This is a routing skill. Do not perform a full SDK integration from this file. Identify the app platform, then fork into or load the matching platform-specific install skill and follow that skill as the source of truth.

## Routing Rules

Inspect the repo before choosing:

- Use the .NET install skill for .NET MAUI, .NET for Android, .NET for iOS, and .NET Mac Catalyst apps.
- Use the iOS install skill for native SwiftUI or UIKit apps.
- Use the Android install skill for native Android Kotlin apps.
- Use the React Native install skill for React Native apps with iOS and Android native projects.

If more than one app is present, ask which app should be configured unless the user's prompt clearly identifies one.

## Remote Tool Default

When the selected install enables reflection, mention the concrete `reflect.*` tool family and default the reflection package or suite to a development-time dependency: Debug or explicit local-development variants only, with runtime guards. Do not enable `reflect.*` for distributable builds unless the user explicitly requests it and accepts the policy.

## Platform Skills

| Platform | Use This Skill |
| --- | --- |
| .NET MAUI, .NET Android, .NET iOS, .NET Mac Catalyst | `https://www.ansight.ai/skills/dotnet/ansight-install-dotnet.md` |
| Native iOS SwiftUI or UIKit | `https://www.ansight.ai/skills/ios/ansight-install-ios.md` |
| Native Android Kotlin | `https://www.ansight.ai/skills/android/ansight-install-android.md` |
| React Native | `https://www.ansight.ai/skills/react-native/ansight-install-react-native.md` |

## Detection Hints

- `.csproj`, `MauiProgram.cs`, `TargetFramework` values such as `net*-android`, `net*-ios`, or `net*-maccatalyst`: .NET.
- `.xcodeproj`, `.xcworkspace`, `Package.swift`, `Podfile`, `Info.plist`, SwiftUI `App`, or UIKit `AppDelegate` without React Native app files: native iOS.
- `settings.gradle`, `build.gradle`, `build.gradle.kts`, `AndroidManifest.xml`, and Kotlin `Application` without React Native app files: native Android.
- `package.json` with `react-native`, `ios/`, `android/`, `metro.config.*`, or `@react-native/*`: React Native.

React Native takes precedence over the native iOS or Android project folders it contains.

## Workflow

1. Inspect the repository root and likely app directories.
2. Identify the target platform and app module.
3. If the current agent supports subagents or thread forking, fork the implementation into the matching platform-specific skill.
4. If the current agent cannot fork, load or follow the matching platform-specific skill directly in the current task.
5. Continue with the selected skill's workflow, including Studio app registration, pairing config issuance, runtime guards, permissions, verification, and `ansight-readme.md`.
6. Include the selected skill URL in the final response so the user can audit which route was used.

Do not claim a platform-specific setup was completed until the selected skill's verification steps have actually passed or the remaining manual steps are listed.