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

How to study 20 interactive 3D site patterns for a design brief with Dioramas

Run the gallery locally and review how each example handles scroll and interaction.

Who it is forA product designer or creative lead who wants proven interaction ideas for a 3D web concept before committing to a build.

The problemInteraction ideas for 3D web pages are hard to judge from screenshots alone, and the mechanics are rarely written down.

The outcomeA short list of reusable interaction patterns, each tied to a working example and its brief in docs/briefs/.

What you need first

  • Git and Node.js with npm, to clone the repo and run the dev server
  • A desktop GPU, which the README recommends for 60 fps
  • About 330 MB of disk space for the repo, since models ship in the clone (no LFS)
  • A fal account and FAL_KEY, only if you want to generate new models or images

Steps

  1. Run git clone https://github.com/blendi-remade/dioramas && cd dioramas
  2. Run npm install
  3. Run npm run dev and open http://127.0.0.1:5190 to view the gallery.
  4. Open the examples whose signature interactions fit your concept, such as the scroll-driven or press-and-hold ones in the table.
  5. Read the matching brief in docs/briefs/ to see how each example was specified.

Prompt for your agent

In the blendi-remade/dioramas repo, read the 20 example rows in README.md and the briefs in docs/briefs/, then list the five interaction patterns most relevant to <product or concept>. Expected output: a table with columns for example name, interaction, and the brief file that describes it. Verify that each example name in the table matches a folder under examples/.

Caveat. The examples are tuned for 60 fps on a desktop GPU, so performance on a laptop or phone may differ from what the gallery shows.

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