Blender Skills is a pack of 99 Claude Code skills that turn a prompt into a finished 3D render or video. Blender never has to open. https://github.com/automatorsplus/blender-skills Blender has a full Python API and a command-line mode. So Claude writes the whole scene as one Python script, Blender runs it in the background and ffmpeg stitches the frames into an MP4. No addon, no MCP to connect. How it works: 1. You ask for a render in plain English. 2. Claude writes scene.py: the models, materials, lights, camera and animation, all in code. 3. It renders six preview frames at half size first, builds a contact sheet and estimates how long the full render will take. 4. You say go, or ask for one change and get a new preview. 5. The final render runs in the background with a time-left readout, so the chat stays free. To install it, get Blender (free from blender.org) and ffmpeg, then: git clone https://github.com/automatorsplus/blender-skills.git What's the first thing you'd render?

who need help with mobile app or website development, debugging, AI/ML, Agent, bots, automation, SAAS or ai training? Feel free to comment your questions or challenges in this post. I’d be happy to discuss your requirements, exchange ideas, and help you work through problems. Please include relevant details so we can have a productive discussion!

Worktrunk lets you run several Claude Code sessions on the same project at once without them overwriting each other's work. It has 11,269 stars on GitHub. https://github.com/max-sixty/worktrunk The trick underneath is a git feature called worktrees. Each agent gets its own copy of the project folder on its own branch, so one can build a feature while another fixes a bug. Plain git makes this painful: you type the branch name three times just to start one. Worktrunk cuts it to one command. How it works: 1. wt switch -c -x claude feat creates a branch called feat, makes its own folder and opens Claude Code inside it. 2. Repeat with a different name for each job. Every agent works in its own folder. 3. wt list shows every worktree with its changes and how far ahead of main it is. 4. wt switch feat jumps you into any of them. 5. wt remove deletes the folder and the branch when the job is done. Worth knowing next: hooks can run a command whenever a worktree is created or merged. It can write commit messages from the diff. Ten worktrees can share one node_modules folder instead of copying it. And wt switch pr:123 jumps straight to a pull request's branch. Install it on Mac or Linux with: brew install worktrunk && wt config shell install On Windows it installs through winget as git-wt. It's free and open source. What would you hand to a second Claude Code session if you could run two at once?

Claude Code has an effort setting that controls how hard Claude thinks before it acts. The higher you go, the more of your usage limit it burns, so I tested whether the top levels earn it. I gave Opus 5.5 the same prompt three times, in three empty folders, changing only the effort setting. One shot each, nothing fixed afterwards. → Low: 2m 14s, 1,137 thinking tokens, $0.48 → High: 65m 04s, 92,531 thinking tokens, $6.57 → Max: 63m 07s, 204,869 thinking tokens, $20.06 The dollar figures are what each build would cost if you paid per token on the API. On a Max plan it comes out of your usage limit instead. Low never opened the game it built. High tested its own in Chrome and checked screenshots. Max playtested while it built, redesigned two tracks and had a second agent review the code. Same hour as high, over twice the thinking. The video covers how each game plays, the full scoreboard, and how I'd use each level day to day. The three games and the prompt (zip attached below): → neon-drift-low.html, one track, five rivals, drift to charge a boost. Needs internet to load → apex-runners-high.html, three tracks, three difficulties, slipstream → afterglow-gp-max.html, full menu with mode, track, car, paint, rivals and laps Download the zip, unzip it, then double-click any game to play. Arrows or WASD to drive, hold Space while turning to drift, R resets the car. The prompt, the same one for all three: Build me an original 3D racing game that runs in the browser. One HTML file I can open by double-clicking. Make it fun to play. Don't ask me questions, make the calls yourself, and tell me when it's done. Try it at different effort levels in your own Claude Code and see how far apart the results land. One run per level, so it's not a benchmark, but the gap was big enough to show.

Blender is a free, open source 3D app for modelling, animation and rendering. It also takes Python scripts, so you can build and render a scene without ever opening its window. 👉 https://www.blender.org How it works: 1. Download it from blender.org. There are builds for Windows, Mac (Apple Silicon, macOS 13 or newer) and Linux. You don't need an account. The current release is 5.2.3 LTS, out 22 October. 2. Build a scene. That means models, cameras, lights and materials. You can do it by hand in the app or in Python, because Blender's docs say any setting you can change with a button can also be changed with Python. 3. Pick a render engine. EEVEE renders in real time, so it's the quick one. Cycles is a path tracer built for photo-real results. It runs on your CPU or GPU. 4. Render from the terminal. blender -b runs Blender in the background with no window at all. Add -P and a script file to run your Python first, then -a to render every frame of the animation (or -f for a single frame). That last step is where Claude Code fits. You describe the shot. Claude Code writes the Python that builds it, then runs blender -b to render it. Blender's window never opens. Worth knowing: you can switch engine from the command line too. -E CYCLES renders in Cycles. blender -E help lists every engine you have. On cost: nothing. Blender is under the GNU GPL, free to use for any purpose, commercial work included. Whatever you make with it is yours. What would you get Claude Code to build in Blender first?