Repository navigation
Cursor Integration
Cursor reads .cursorrules from the repo root automatically. When you open this repo in Cursor, the AI already knows the agent index, platform conventions, and severity levels — no setup needed.
Cursor loads .cursorrules at the start of every session in the workspace. It acts as a persistent system prompt for Cursor Chat and Composer. You can verify it's active by asking:
"What agents are available in this repo?"
Cursor should list all agents from the agent index in .cursorrules.
Use when: You want to review or improve one file.
- Open the file you want to review (e.g.,
ProfileViewModel.kt) - Open Cursor Chat (Cmd+L)
- Type:
Review this file using the Android Code Reviewer agent at
agents/android/code-reviewer/agent.md
Or more naturally:
Review this ViewModel for Clean Architecture violations and coroutine safety.
Cursor will read the agent rules from .cursorrules and produce a structured CRITICAL/WARNING/INFO report.
With file reference:
@ProfileViewModel.kt
Review for Clean Architecture violations, GlobalScope usage, and Compose best practices.
Use when: You want to review AND automatically apply fixes across one or more files.
- Open Composer (Cmd+I or Cmd+Shift+I)
- Reference the file(s) and the agent:
@agents/android/code-reviewer/agent.md @ProfileViewModel.kt
Review ProfileViewModel.kt, then apply the CRITICAL and WARNING fixes directly to the file.
Composer will:
- Run the agent review
- Show you a diff of every proposed change
- Let you accept or reject each change individually
Multi-file example:
@agents/react-native/performance-optimizer/agent.md
Review every file in src/screens/ for performance issues and apply the HIGH-impact fixes.
- Open or paste the crash log into a new file (e.g.,
crash.txt) - In Cursor Chat:
@crash.txt @agents/android/crash-analyzer/agent.md
Analyze this crash log. The user was on Android 14 / Pixel 8 Pro.
Cursor will return the full 9-section crash analysis: Summary, Root Cause, Why It Happens, Risk Level, Recommended Fix, Updated Code, Edge Cases, Testing Checklist, Prevention Tips.
Flutter widget:
@agents/flutter/widget-generator/agent.md
Generate a Flutter widget for a swipeable onboarding screen with 3 pages,
a dot indicator, skip button, and a Get Started button on the last page.
Flutter 3.27, Dart 3.6, no state management package.
Unity shader:
@agents/unity/shader-generator/agent.md
Generate a URP unlit shader for a dissolve effect using a noise texture.
The dissolve threshold should be a tweakable property. Mobile-friendly.
@agents/cross-platform/ci-cd-generator/agent.md
Generate a GitHub Actions pipeline for my Flutter app.
Platforms: Android + iOS.
Distribution: Firebase App Distribution (Android) + TestFlight (iOS).
Tests: flutter test.
Notify Slack on success/failure.
- @codebase in Cursor Chat gives the agent awareness of your entire project structure — useful for architecture-level questions.
-
Cursor Tab (autocomplete) uses
.cursorrulesimplicitly — it will suggest Kotlin idioms, avoid!!, and preferStateFlowin Android files automatically. - For agents with long output (CI/CD Generator, Store Listing Writer), use Composer rather than Chat — Composer handles long outputs better and can write directly to files.
- Combine multiple
@filereferences to give the agent cross-file context:
@ProfileViewModel.kt @ProfileRepository.kt @ProfileUseCase.kt
Review the full data flow for Clean Architecture violations.
When new agents are added to the repo, update the Agent Index table in .cursorrules so Cursor Chat can reference them. The table is at the top of the file.
Getting Started
Documentation
- All Documentation
- Installation
- Figma MCP and Design Handoff
- Figma Spec Tools
- Core Loops
- Mobile Engineering Loop
- Mobile Memory
- Performance Loop
Reference
- Agents
- Platform Guide
- Skills and Prompts
- Android Device QA Setup
- Mobile App Design Skill
- Mobile Harness
- Enterprise Mobile Harness
- Workflows
- Reference
Community
Repository github.com/salmanashraf/mobile-ai-agents
Version: v1.0.38 · MIT License