Prompt iteration tracker
Good prompt engineering is empirical: you change one variable, regenerate, and compare. Without a log it is almost impossible to remember which model, seed, or temperature produced your best output three attempts ago. This tracker gives you a structured place to record every attempt so iteration becomes a measurable process instead of guesswork.
How it works
Each time you generate something, fill in the prompt text, the model you used, any settings (temperature, steps, CFG, etc.), the seed, a 1-5 rating of the result, and free-form notes. The attempt is appended to a table with a timestamp and saved to your browser’s localStorage, so the history persists between sessions. Because the data lives only on your device, you can log sensitive or proprietary prompts without anything leaving the browser.
Tips for effective iteration
- Change one variable at a time. If you alter the prompt and the temperature together, you cannot tell which one moved the output. The log only helps if each row isolates a single change.
- Always record the seed. A fixed seed makes a result reproducible; logging it lets you return to a near-miss and tweak just the prompt.
- Rate honestly and consistently. A 1-5 scale only works if a “4” means the same thing across the session. Sort mentally by rating to find your front runners.
- Export before clearing. CSV opens in any spreadsheet for side-by-side comparison; JSON is better if you want to feed the history into another tool.