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

How to turn a street scene into a rainy night with puddles with Blender Skills

Set a street scene to night with rain, wet surfaces, puddles and lightning using agent-run skills.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA 3D artist making a mood render or a short animation of a city street.

The problemGetting time of day, rain, wet roads and lightning to look right together takes many separate lighting and material steps.

The outcomeA night street scene with rain, puddles and lightning, set up by the time of day and weather skills and ready to render.

What you need first

  • Blender 5.2 or newer installed
  • git to clone the repository
  • An AI coding agent such as Claude Code, Codex, Gemini CLI or Cursor
  • Optional: a Blender MCP server so agents can work in your open Blender session

Steps

  1. Clone the repository: git clone https://github.com/EL4CTEO/blender-skills
  2. Install the skills: ./blender-skills/install/install.sh (macOS / Linux) or .\blender-skills\install\install.ps1 (Windows)
  3. Ask the agent to set the scene to night with fog and mood lighting using the time of day skill.
  4. Ask the agent to add rain, wet streets, puddles and lightning using the weather effects skill.
  5. Ask the agent to render a test frame with the rendering skill and review it.

Prompt for your agent

Using the blender-skills repo, change <street scene .blend> to a rainy night with puddles and lightning, then render one test frame. Expect the rendered image and a short list of the lighting and weather changes made. Verify that the puddles sit on flat ground and not on slopes, and that the lightning flash is visible in the render.

Caveat. The README gives no render time or hardware figures for these effects, so expect the render speed to depend on your machine and scene.

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