# AI use cases for Fable51 Worlds (PhiloLabs/fable51-worlds)

Repo: [PhiloLabs/fable51-worlds](https://github.com/PhiloLabs/fable51-worlds) | Use cases: 3 | Page: https://dedupedai.com/use-cases/philolabs-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.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Walk a real San Francisco plaza in a browser: https://dedupedai.com/use-cases/philolabs-fable51-worlds/walk-real-street-in-browser/
- Change one building detail as a reviewable code diff: https://dedupedai.com/use-cases/philolabs-fable51-worlds/edit-world-with-reviewable-diff/
- Check a generated world against reference photos: https://dedupedai.com/use-cases/philolabs-fable51-worlds/check-world-against-reference-photos/

## How to walk a real San Francisco plaza in a browser with Fable51 Worlds

Repo: [PhiloLabs/fable51-worlds](https://github.com/PhiloLabs/fable51-worlds) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Explore a generated Union Square build and its walkthrough route without installing a game engine.

**Who it is for:** A game or film designer who needs a walkable reference of a real public plaza before a location shoot or level build.

**The problem:** Photos and maps do not show how a plaza feels to move through, and a full 3D engine is heavy for a quick look.

**The outcome:** A walkable Three.js scene of Union Square, with the walkthrough video as a guide to the key viewpoints.

### Steps

1. Open the union-square-sf folder in the repo.
2. Watch union-square-sf/media/union-square-walkthrough.mp4 to see the aerial, plaza, Nintendo, lower level and Apple scenes.
3. Open the Three.js build from the union-square-sf folder in a web browser.
4. Move through the scene and check each walkthrough scene against the video.

### Prompt to paste into your agent

```text
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.
```

### Caveat

The README describes the walkthrough and build but gives no run command, so the browser setup step depends on how you serve the files.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/philolabs-fable51-worlds/walk-real-street-in-browser/

## How to change one building detail as a reviewable code diff with Fable51 Worlds

Repo: [PhiloLabs/fable51-worlds](https://github.com/PhiloLabs/fable51-worlds) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Adjust a shopfront or façade parameter in a world and confirm only that part changed.

**Who it is for:** A technical artist revising a generated district after a client asks for deeper shopfront recesses.

**The problem:** Re-rolling a generated scene changes everything at once, so small fixes are hard to review and undo.

**The outcome:** A code change limited to the requested parameter, with the rest of the world unchanged in the browser.

### Steps

1. Clone the repo and open the kyoto-higashiyama folder.
2. Find the façade or townhouse generator code that sets the shopfront depth.
3. Change the shopfront recess depth value and save the file. (inferred, check the README)
4. Open the build in a browser and compare the affected street with the previous version.
5. Commit the change as a separate diff so it can be reviewed and reverted. (inferred, check the README)

### Prompt to paste into your agent

```text
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.
```

### Caveat

The README says edits are diffs but does not name the exact file that holds the recess setting, so the agent has to locate it in the code first.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/philolabs-fable51-worlds/edit-world-with-reviewable-diff/

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

Repo: [PhiloLabs/fable51-worlds](https://github.com/PhiloLabs/fable51-worlds) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

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

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

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

**The outcome:** A list of viewpoints with visible differences from the reference photos, plus the QA report that ships with the world.

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/philolabs-fable51-worlds/check-world-against-reference-photos/