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

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

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

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

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

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

The outcomeA code change limited to the requested parameter, with the rest of the world unchanged in the browser.

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. 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 for your agent

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.

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