Builder Trainer Guide for Screenshot Analysis and UI Learning

Settings Reference

Trainer workflow controls

The interface is intentionally simple because the screenshot does most of the teaching.

• Screenshot Upload: Provides the builder or editor UI image that the analyzer scans for visible controls, regions, and labels. Use the clearest screenshot you can, preferably focused on one UI context.
• Re-analyze: Runs the detector again if the screenshot or results need another pass. Use it after uploading a new screenshot or when the first pass misses important controls.
• Hotspot Selection: Opens a detailed explanation with title, description, usage notes, and tips for one detected element. Use it to drill into a specific control instead of reading the full list of detected UI elements.
• Build Helper Tab: Moves from UI-element explanation into broader assistant guidance with text questions and optional screenshot upload. Switch here when the issue is not what a button does but how to approach a Unity, material, lighting, transform, or workflow problem overall.

Workflow

Use Builder Trainer to upload a builder or editor screenshot, let AI detect the important interface elements, and turn the screenshot into a teachable walkthrough for your workflow.

Step 1: Upload a clear screenshot

The tool works best when the screenshot shows readable controls and interface labels. Busy or blurry screenshots reduce detection quality.

Step 2: Let the analyzer detect important elements

Builder Trainer automatically focuses on the most important UI elements instead of trying to explain everything at once.

Step 3: Click hotspots and review the explanations

Use the hotspot list and sidebar to learn what each control does, when to use it, and what to watch out for.

Step 4: Switch to Build Helper when you need broader guidance

Screenshot analysis explains visible controls. Build Helper is better when you need broader advice about building or workflow decisions.

Common Pitfalls

• Do not expect strong results from blurry or zoomed-out screenshots.
• Do not use Builder Trainer as a substitute for workflow documentation when the real problem is process, not UI recognition.

What kind of screenshot works best?

A clear screenshot with visible controls, readable labels, and one dominant interface context gives the best detection results.