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

How to make a riso film from a one-line prompt with Riso Windowseat

Describe a scene to Claude Code and get a single-file procedural riso film you can open and play in a browser.

  • Top pick
  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code

Who it is forA creator or designer who wants a short animated piece in the riso style and has no animation toolchain set up.

The problemMaking an animated film from scratch usually needs asset pipelines, libraries and export tooling.

The outcomeA new film folder with an index.html that plays in a browser, with its design recorded in a FILM.md.

What you need first

  • Git, to clone the repo
  • npm, since the setup runs npm install and npm run setup
  • Claude Code, the coding agent the README names for making new works
  • A web browser, to open the index.html files and press play

Steps

  1. git clone https://github.com/sevenevesai/riso-windowseat
  2. cd riso-windowseat/tools
  3. npm install && npm run setup && npm test
  4. Open Claude Code in the repo root and ask for a film, for example "Make a 40 second riso film of a lighthouse keeper's night."
  5. Open the new index.html in a browser and press play to check the result.

Prompt for your agent

In the riso-windowseat repo, make a riso film of <scene description> using the riso-film skill in .claude/skills/. Expect a single index.html plus a FILM.md in films/. Verify the film plays in a browser and that its design notes are recorded in FILM.md.

Caveat. The films use no libraries, fonts, images or network calls, but any new audio you add must carry its own license, as the repo's AUDIO-SOURCES.md files show.

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