makepad-screenshot

Automated screenshot visual debugging captures, analyzes, and reports UI screenshots to identify rendering issues in Makepad apps. It handles current-running apps, named targets, and build-run workflows to verify UI rendering across demos and custom apps.

You can capture a Makepad app screenshot by invoking the /screenshot slash command for the current app, or using /run-and-capture <package> to build, run, and capture a named app. The tool brings the target window to front for reliable captures.

Yes, Makepad visual debugging requires macOS-native tooling for window handling and screen capture. These native tools ensure deterministic screenshot workflows by bringing the target Makepad app window to the front for reliable captures.

Yes, you can build and run a named Makepad app before capturing its UI screenshot by using the /run-and-capture <package> slash command. This triggers an end-to-end workflow that builds, runs, and captures the target app.

Captured Makepad GUI screenshots are analyzed using a Read tool to evaluate UI rendering. The tool then generates actionable UI reports to help identify and resolve visual debugging issues within the Makepad application.