Expo Dev Assistant AI Integration

Create a new Expo project with a selected template. This tool creates a new Expo project directory with all necessary files and dependencies. It's the first step in creating a new Expo application. **When to use:** Starting a new Expo/React Native project from scratch. **Templates available:** - blank: Minimal template with just the essential dependencies - tabs: Template with tab-based navigation using Expo Router - blank-typescript: Blank template with TypeScript configured - navigation: Template with React Navigation pre-configured **Example usage:** - Create a blank TypeScript project: projectName="my-app", template="blank-typescript" - Create app with tabs: projectName="my-app", template="tabs" **Returns:** Success message with project path and next steps. **Errors:** - Directory already exists - Invalid template name - Network errors during package installation

Install packages with automatic version validation for React Native compatibility. This tool uses Expo's smart package installer which automatically selects compatible versions of packages based on your Expo SDK version. **When to use:** Installing new dependencies in an Expo project. **Benefits over npm/yarn:** - Automatic version compatibility checking - Warns about incompatible versions - Suggests correct versions for your SDK **Example usage:** - Install single package: packages=["expo-camera"] - Install multiple: packages=["expo-camera", "expo-location", "expo-sensors"] **Returns:** Installation results with package versions installed. **Errors:** - Package not found - Version incompatibility - Network errors - Must be run in an Expo project directory

View the evaluated Expo app configuration (app.json/app.config.js). This tool reads and evaluates your app's configuration, showing the final computed values including all dynamic values from app.config.js. **When to use:** - Debugging configuration issues - Verifying config values before builds - Understanding current app settings **Configuration includes:** - App name, slug, and version - Platform-specific settings (iOS, Android, web) - Build configuration - Asset and icon paths - Permissions and capabilities **Example usage:** - View current config: projectPath="." (or omit for current directory) - View another project: projectPath="/path/to/project" **Returns:** Complete app configuration in JSON or Markdown format. **Errors:** - No app.json or app.config.js found - Invalid configuration syntax - Missing required fields

Generate native iOS and Android project directories for customization. This tool runs "prebuild" which generates native project folders (ios/ and android/) from your app.json configuration and config plugins. This is necessary when you need to: - Add custom native code - Modify native project files - Use libraries requiring manual linking - Debug native build issues **When to use:** - Need to add custom native code - Library requires manual native configuration - Debugging native build issues - Migrating from bare workflow **Important:** Generated folders should generally be gitignored and regenerated as needed, unless you're committing native code modifications. **Example usage:** - Generate both platforms: (use defaults) - Clean regenerate: clean=true - Specific platform: platform="ios" **Returns:** Success message indicating which platforms were generated. **Errors:** - Invalid configuration - Missing dependencies - Platform-specific errors

Run comprehensive diagnostics on an Expo project to identify issues. This tool checks for common problems including: - Package version mismatches - Configuration errors - Missing dependencies - Environment setup issues - Compatibility problems **When to use:** - Troubleshooting build or runtime errors - After upgrading SDK versions - Setting up a project on a new machine - Before starting development **What it checks:** - Expo SDK compatibility - Package versions alignment - Configuration validity - Required native dependencies **Example usage:** - Check current project: projectPath="." - Fix issues automatically: fixIssues=true **Returns:** List of issues found and suggestions for fixes. **Errors:** - Not an Expo project - Unable to read configuration