agentleFS
arjun988arjun988/blender-skills/CLAUDE.md

blender-skills

CLAUDE.md2.2k starsChanged 4 months agoMITView on GitHub

Blender Skills Pack for Cursor and Claude Code with Blender MCP integration. Blender must be running with the BlenderMCP addon connected. See docs/BLENDER_MCP_SETUP.md.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about arjun988/blender-skills

The biggest 5 of 12 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 12

Talked about on GitHub (12 times).

On GitHub · 12

7 more on GitHub

The file

We split this CLAUDE.md into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If user attaches a reference image: read references/reference-image-match.md and complete Reference Analysis before MCP execution

    line 18
  2. Very specific:

    Read MCP tool schemas before calling (see references/mcp-tools.md)

    line 20
  3. Very specific:

    Follow universal pipeline in references/asset-pipeline.md

    line 21
  4. Very specific:

    Use naming conventions from references/naming-conventions.md

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Blender Skills Project

Blender Skills Pack for Cursor and Claude Code with Blender MCP integration.

Project Structure

.claude-plugin/          # plugin.json + marketplace.json
.claude/skills/          # 94 specialist skills + shared references
.cursor/mcp.json         # Blender MCP (Cursor)
.mcp.json                # Blender MCP (Claude Code)
docs/BLENDER_MCP_SETUP.md

Agent Instructions

  1. For Blender asset tasks, read blender-director first for complex work
  2. If user attaches a reference image: read references/reference-image-match.md and complete Reference Analysis before MCP execution
  3. Check Blender MCP — if connected, execute via MCP; never narrate UI steps
  4. Read MCP tool schemas before calling (see references/mcp-tools.md)
  5. Follow universal pipeline in references/asset-pipeline.md
  6. Validate before export using references/validation-checklist.md
  7. For reference tasks, also run references/visual-match-checklist.md
  8. Use naming conventions from references/naming-conventions.md

MCP Setup

Blender must be running with the BlenderMCP addon connected. See docs/BLENDER_MCP_SETUP.md.

Key Files

  • QUICKSTART.md — Installation
  • SKILLS_GUIDE.md — Decision trees and workflows
  • README.md — Overview

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.