What do you want to do?
3 use cases
-
Walk a real San Francisco plaza in a browser
Explore a generated Union Square build and its walkthrough route without installing a game engine.
- Fable51 Worlds
- Content
- Intermediate
View prompt
Using the repo PhiloLabs/fable51-worlds, open the union-square-sf build in a browser and check the five walkthrough scenes listed in the README (aerial, plaza, Nintendo, lower level, Apple). Expected output: a pass or fail list for each scene. Verify that every scene named in the README is reachable in the build.
-
Change one building detail as a reviewable code diff
Adjust a shopfront or façade parameter in a world and confirm only that part changed.
- Fable51 Worlds
- Content
- Advanced
View prompt
Using the repo PhiloLabs/fable51-worlds, find the shopfront recess depth setting in the kyoto-higashiyama code, change it by a stated amount, and list every file that changed. Expected output: a short diff with only the recess setting changed. Verify that no other world or module was modified.
-
Check a generated world against reference photos
Run Playwright screenshots of fixed viewpoints and compare them with photos from the same spots.
- Fable51 Worlds
- Content
- Advanced
View prompt
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.
How to use Fable51 Worlds
- Check you have what it needs: 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.
- Open PhiloLabs/fable51-worlds on GitHub and read the README and license.
- Open the union-square-sf folder in the repo.
- Watch union-square-sf/media/union-square-walkthrough.mp4 to see the aerial, plaza, Nintendo, lower level and Apple scenes.
- Open the Three.js build from the union-square-sf folder in a web browser.
- Move through the scene and check each walkthrough scene against the video.
These steps come from our top use case, Walk a real San Francisco plaza in a browser, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forDesigners, technical artists and QA staff who want walkable reference scenes or a verifiable 3D pipeline they can read and edit.
- Why it is hot
- LanguageJavaScript
- Sourcegithub.com/PhiloLabs/fable51-worlds · Back to Hot repos
Requirements
- 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
Maintain Fable51 Worlds? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/philolabs-fable51-worlds/?ref=badge)
Questions about Fable51 Worlds
What is Fable51 Worlds?
A repo of procedurally generated 3D worlds built with Three.js, each walkable in a browser, with the generating code, verification scripts and QA reports included. It is an open-source project on GitHub: https://github.com/PhiloLabs/fable51-worlds.
Who is Fable51 Worlds for?
Designers, technical artists and QA staff who want walkable reference scenes or a verifiable 3D pipeline they can read and edit.
What can I do with Fable51 Worlds?
3 use cases so far, for example: Walk a real San Francisco plaza in a browser; Change one building detail as a reviewable code diff; Check a generated world against reference photos. Each has steps and a copy-paste agent prompt.
What do I need to run Fable51 Worlds?
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.
What are alternatives to Fable51 Worlds?
Other hot AI repos in Content: Voice Studio, Anatomy, Comfy UI, Hyperframes, Earshot.
Is Fable51 Worlds safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.