ai-image-run-pacinglisted

# AI Image Run Pacing Generating one image is easy. Generating a set of them in one sitting, through a hosted assistant, is where runs actually fail: throttled halfway, faces drifting between images, references silently dropped, or an agent hammering retries until the account is locked for hours. This skill is the operating discipline for those runs. It is deliberately tool-agnostic and contains no page selectors or automation snippets, because those break the moment a provider redesigns and give a false sense of what is safe to automate. ## When to use - Generating more than two or three images in one session. - Driving a hosted image tool with an agent, an extension, or a script. - Recovering from "too many requests" or a temporary limit. - Deciding how many reference images to attach, and to which turn. - Planning a run that must finish unattended. ## Credentials: the rule that has no exceptions **Never store, type, or automate an account password.** Not in a config file, not in an environment variable, not passed to a browser driver. The reason is not only leak risk. Scripted logins trip bot detection, two-factor prompts break unattended runs, and automating a login is the part most likely to put an account at risk of suspension. The supported pattern is a **persistent browser profile**: open a browser window once, let the person log in by hand, and reuse that profile directory for every later run. Keep it out of version control. Deleting the directory is the logo