Improve a generated 3D scene with a screenshot and critic agent loop

What you end up with

The key detail is that the critic is a separate, fresh agent, so it judges the image instead of defending its own code.

What you get

• A plain-language summary of the workflow
• A fill-in prompt template
• What to watch out for
• A link to the original source

Who it is for

Builders who already use AI agents and want a proven workflow they can copy into their own project.

Works with

Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.

Tools needed

Cost to run: Free with the agent plan you already use.
Time to result: One working session

How it works

1. Have the agent build the first version

   Have the agent build the first version.

   Expected: Done before you move to the next step.

2. Have it take a screenshot of the running result

   Have it take a screenshot of the running result.

   Expected: Done before you move to the next step.

3. Start a fresh agent, show it only the screenshot and the goal, and ask

   Start a fresh agent, show it only the screenshot and the goal, and ask for a blunt critique.

   Expected: Done before you move to the next step.

4. Feed the critique back to the builder and repeat two or three times

   Feed the critique back to the builder and repeat two or three times.

   Expected: Done before you move to the next step.

Sample prompt from the pack

Apply this workflow to [your project]:
1. Have the agent build the first version.
2. Have it take a screenshot of the running result.
3. Start a fresh agent, show it only the screenshot and the goal, and ask for a blunt critique.
4. Feed the critique back to the builder and repeat two or three times.
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.

Free preview of the file

# Improve a generated 3D scene with a screenshot and critic agent loop

PaperChase agent use case (free feed entry), version 1.0. Source: [@SKatalystAI (Sinda) on X](https://x.com/SKatalystAI/status/2111809289442435225), 2026-10-18.

## What they did

One prompt produced a first version, then three rounds of screenshot, critique and revise took it from what the creator rated 2 out of 10 to a moody night scene.

## Worth knowing

The key detail is that the critic is a separate, fresh agent, so it judges the image instead of defending its own code. The same loop works for UI, game art and landing pages. Ratings are the creator's own.

Worth knowing

• The key detail is that the critic is a separate, fresh agent, so it judges the image instead of defending its own code. The same loop works for UI, game art and landing pages. Ratings are the creator's own.
• Figures are as reported by the original author and were not re-measured by us.

Details

Version 1.0 · Updated Oct 25, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms

Related

Prompt pack$14

AGENTS.md, CLAUDE.md and Cursor rules starter files

by PaperChaseWebb

Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules) and 8 prompts to write, trim and test your own.

Works withClaude CodeCodexCursorPlain .md

Vibe coding · Beginner · 20 min setup

Prompt pack$19

Ask-first rules for AI agents: hard nos, approval cards and a test set

by PaperChaseWebb

Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.

Works withClaude CodeCodexClaudeCursor+2Plain .md

Solo business · Beginner · 20 min setup