screenshot-handling

To stop screenshots from cluttering your project root, enforce saving all captured images to a dedicated 'screenshots/' directory. This prevents visual assets from being saved in the root and automatically creates the required folder if it doesn't exist.

The best way to organize visual assets generated during automated testing is to enforce a dedicated 'screenshots/' directory. This guarantees images from capture tools are neatly organized, maintaining a clean project structure and improving asset discoverability.

Yes, this screenshot organization approach works with agent-browser, Playwright, and Puppeteer. It provides clear guidelines for various capture methods, ensuring all images are automatically routed to the correct folder regardless of the tool used.

To automate folder creation for saving testing screenshots, use a skill that enforces a 'screenshots/' directory. It automatically creates the required folder if it doesn't exist before saving files, preventing missing directory errors.

Puppeteer screenshots are saved in the project root because a dedicated output path is not enforced. Without automated routing to a 'screenshots/' directory, the capture tool defaults to the current working directory, causing clutter.