# Use Cases

<details>

<summary>UI Creation</summary>

* “*Import this Figma flow and generate the menus for Settings, Shop, and Inventory.”*
* *“Create prefabs for Primary/Secondary buttons and hook up `onClick` placeholders.”*
* *“Apply anchors for 16:9 → 20:9 and pack UI sprites into a single atlas.”*

</details>

<details>

<summary>Live Debugging</summary>

**Crash & error debugging**

* *“Why did the game crash for users on iPhone 12 during the tutorial level?”*
* *“Explain the memory leak causing players’ sessions to freeze after 20 minutes.”*
* *“What’s behind this spike in exceptions in Scene\_BossFight?”*

**Performance drops**

* *“Why does FPS drop when players enter the Forest level?”*
* *“Find out why Draw Calls spiked after the last patch.”*
* *“Diagnose stutters happening on Android mid-battle.”*

</details>

<details>

<summary>Profiling &#x26; Optimization</summary>

**Snapshots & spikes**

* *“Show me where RAM usage spikes across Chapter 3.”*
* *“Identify the assets with the heaviest GPU load.”*
* *“Detect memory leaks introduced since version 1.4.”*

**Optimization**

* *“Optimize Dungeon\_01 scene for low-end Android devices.”*
* *“What textures are oversized and should be compressed?”*
* *“Find redundant scripts in the Inventory system.”*

</details>

<details>

<summary>Game Data Analysis</summary>

**User flows & funnels**

* *“What % of players drop out before completing the tutorial?”*
* *“Build a funnel from entering the shop → selecting an item → completing a purchase.”*
* *“What’s the most common sequence of actions before churn?”*

**Complex analysis**

* *“Run a regression to see if session length predicts revenue.”*
* *“Forecast player retention for next month using past cohorts.”*
* *“Which factors most strongly predict in-app purchase likelihood?”*

**Schema & joins**

* *“Which tables store my purchase events?”*
* *“Link sessions with crash logs and return top 5 correlations.”*
* *“Detect undefined event properties in my analytics schema.”*

</details>

<details>

<summary>LiveOps Orchestration</summary>

#### **Event management**

* *“Set up a double XP weekend event for all players in NA.”*
* *“Test different difficulty configs for the boss fight with 5% of users.”*
* *“Roll back the Halloween event for APAC due to crash spikes.”*

#### **Config updates**

* *“Lower health of Boss\_Dragon by 15% in real time.”*
* *“Swap the loot table for DailyChest in build 1.3.2.”*
* *“Test new spawn rate configs against 10% of players.”*

</details>

<details>

<summary>Knowledge &#x26; Learning</summary>

Flow synthesizes Unity, your project context, docs, and live telemetry to answer questions that usually require hours of digging across forums, dashboards, and internal wikis.

#### **Unity/game questions**

* *“What’s the best way to reduce Draw Calls in Unity URP?”*
* *“Explain how Unity Addressables manage memory on mobile.”*
* *“How do you properly clean up after a coroutine?”*

#### **Game-specific knowledge**

* *“Walk me through the CombatManager.cs script.”*
* *“Which prefabs are actually referenced in Scene\_City?”*
* *“List all monetization mechanics currently live.”*

</details>

<details>

<summary>Search Across Project &#x26; Data</summary>

No parameter is too specific. Flow indexes your Unity project, analytics, configs, and logs so you can instantly retrieve exactly what you’re looking for.

#### **Project search**

* *“Which prefabs use Texture\_4K\_Forest?”*
* *“Find all scripts that reference PlayerHealth.”*
* *“List objects tagged with ‘BossArena’.”*

#### **Data search**

* *“Find all events tagged ‘purchase\_failed’ last week.”*
* *“Which devices reported GPU crashes in March?”*
* *“Show me high-value players affected by the bug in Scene\_Market.”*

</details>

<a href="https://flow.letsterra.com/" class="button primary">Visit Website</a> <a href="https://cal.com/terra-demo/30min?overlayCalendar=true" class="button secondary">Schedule a demo</a>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.letsterra.com/use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
