Using Agents

Using Agents

This page walks through every step of using an agent — from choosing the right one to interpreting the output.

---

Step 1 — Choose the Right Agent

I want to...	Agent to use
Review a Kotlin/Compose file	agents/android/code-reviewer
Debug an Android crash log or ANR	agents/android/android-crash-analyzer
Generate an Android Compose screen	agents/android/compose-screen-builder
Deep-review Compose recomposition / state	agents/android/compose-ui-reviewer
Review a Swift/SwiftUI file	agents/ios/swift-reviewer
Debug an iOS crash report	agents/ios/crash-analyzer
Generate a Flutter widget	agents/flutter/widget-generator
Build a full Flutter BLoC feature	agents/flutter/bloc-feature-builder
Audit React Native performance	agents/react-native/performance-optimizer
Generate a Unity shader	agents/unity/shader-generator
Review an Unreal Blueprint	agents/unreal/blueprint-advisor
Scan code for security vulnerabilities	agents/cross-platform/security-scanner
Audit a UI for accessibility	agents/cross-platform/accessibility-auditor
Write release notes from git log	agents/cross-platform/release-notes-generator
Generate a CI/CD pipeline	agents/cross-platform/ci-cd-generator
Write App Store / Play Store copy	agents/cross-platform/store-listing-writer

---

Step 2 — Read the Agent's README

Every agent folder has a README.md. Read it first — it gives you:

• Supported use cases and crash types
• The input format at a glance
• An output preview so you know what to expect
• Related agents for follow-up work

---

Step 3 — Copy the System Prompt

Open agent.md in the agent folder. Find the ## System Prompt section and copy the text inside the code block. This is what you paste into your AI tool.

---

Step 4 — Prepare Your Input

Use the ## Input Format table in agent.md to structure what you paste. Every agent uses a consistent key-value format:

FIELD_NAME: value
MULTI_LINE_FIELD:
<content starts on the next line>

Tips for better output:

• Paste the full class, not a snippet — context from imports and field declarations matters
• Set FILE_PATH to the real relative path — agents infer the architectural layer from it
• For crash analyzers, always fill USER_ACTION — "User tapped Back while uploading" is more useful than 10 lines of code
• For code reviewers, include RELATED_CODE if you know which class is involved

---

Step 5 — Review the Output

Every agent returns output in the exact structure defined by ## Output Format. All sections are labelled.

Code review agents return [CRITICAL], [WARNING], [INFO] findings with line numbers and corrected code.

Crash analyzers return 9 sections: Crash Summary → Root Cause → Why This Happens → Risk Level → Recommended Fix → Updated Code → Edge Cases → Testing Checklist → Prevention Tips.

Generator agents return complete, compilable code organized by file.

Copy-paste the corrected code snippets directly into your editor.

---

Running the Examples

Every agent comes with real worked examples. To see exactly what an agent produces:

1. Open agents/<platform>/<name>/example-input.md
2. Copy the content (it's already formatted for the agent)
3. Apply the system prompt from agent.md
4. Paste the example input
5. Compare your output to example-output.md

---

Common Mistakes

Mistake	Fix
Pasting only the exception line from a crash log	Paste the full stack trace — every line is needed to trace the call chain
Leaving FILE_PATH blank	Set it — agents infer ViewModel vs Repository vs UseCase from the path
Pasting a 5-line snippet instead of the full class	Paste the full class — context from fields and imports changes the analysis
Using try? after getting an agent finding	Fix the root cause; don't silence exceptions
Running the iOS crash analyzer on an unsymbolicated report	Symbolicate first in Xcode Organizer, then paste

---

Home · Tool Guides · Platform Guide · Reference