DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check a generated world against reference photos with Fable51 Worlds

Run Playwright screenshots of fixed viewpoints and compare them with photos from the same spots.

  • Content
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Who it is forA QA lead who must confirm a generated scene matches its real-world reference before sign-off.

The problemVisual checks by eye are subjective and easy to skip, so wrong geometry or missing props slip through.

The outcomeA list of viewpoints with visible differences from the reference photos, plus the QA report that ships with the world.

What you need first

  • A web browser
  • A local copy of the repo (clone or download from GitHub)
  • Basic familiarity with running a local web app for the Three.js build

Steps

  1. Open the QA report that ships with the world you want to check.
  2. Install Playwright and point it at the running Three.js build. (inferred, check the README)
  3. Capture screenshots from the fixed viewpoints the QA report names.
  4. Compare each screenshot with a reference photo you took from the same spot.
  5. Record each difference as a defect in a new QA note.

Prompt for your agent

Using the repo PhiloLabs/fable51-worlds, run Playwright against the built world and capture screenshots at the fixed viewpoints in its QA report. Expected output: a table of viewpoints with a pass or defect note for each one, compared against reference photos you supply. Verify that each screenshot is taken from the viewpoint the QA report lists.

Caveat. The README says reference photographs are not redistributed, so you must source or take your own photos from matching spots.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page