Why it matters
The project describes itself as skills and rules "for Cursor and Claude Code", but only Cursor has a real install path. A Claude Code user who follows the README gets nothing loaded:
- Claude Code discovers project skills under
.claude/skills/<name>/SKILL.md (or through a plugin), not a top-level skills/ directory.
- Claude Code does not read Cursor
.mdc rules at all, so the 9 anti-pattern rules have no effect for Claude users.
- There is no
.claude-plugin/plugin.json or marketplace entry, so there is no one-command /plugin install.
That leaves half the stated audience with a manual, undocumented setup, which is a reach and first-impression problem.
Evidence
README.md:60: "Claude Code — copy skills/ and rules/ into your project workspace." This doesn't name the .claude/skills/ destination, and copying rules/ does nothing.
README.md:1281: "point Cursor at it as a skills/rules source". The setting and path aren't named.
scripts/site/site.json installSteps[2] repeats the vague step on the landing page.
.cursor-plugin/plugin.json exists, but there is no .claude-plugin/ directory. plugin.json keywords are only cursor-plugin, developer-tools, blender, and author.email is a contact@users.noreply.github.com placeholder.
- The skill frontmatter (
name, description) is already Claude-Code-compatible, so the content is ready and only the packaging is missing.
Suggested approach
- Add
.claude-plugin/plugin.json, plus marketplace.json if you want /plugin marketplace add TMHSDigital/Blender-Developer-Tools, pointing at skills/. CI-gate it the same way .cursor-plugin/plugin.json is gated (validate.yml:189-246).
- Bridge the rules for Claude. Either generate a
rules skill, or a CLAUDE.md include snippet summarizing the 9 rules, from rules/*.mdc in CI so it can't drift.
- Rewrite README "Install" as two tabs, Cursor and Claude Code, each with copy-pasteable commands. Mirror them in
site.json.
- Fix the
plugin.json placeholder email and add keywords: claude-code, bpy, blender-addon, blender-python.
Done when
Why it matters
The project describes itself as skills and rules "for Cursor and Claude Code", but only Cursor has a real install path. A Claude Code user who follows the README gets nothing loaded:
.claude/skills/<name>/SKILL.md(or through a plugin), not a top-levelskills/directory..mdcrules at all, so the 9 anti-pattern rules have no effect for Claude users..claude-plugin/plugin.jsonor marketplace entry, so there is no one-command/plugin install.That leaves half the stated audience with a manual, undocumented setup, which is a reach and first-impression problem.
Evidence
README.md:60: "Claude Code — copyskills/andrules/into your project workspace." This doesn't name the.claude/skills/destination, and copyingrules/does nothing.README.md:1281: "point Cursor at it as a skills/rules source". The setting and path aren't named.scripts/site/site.jsoninstallSteps[2]repeats the vague step on the landing page..cursor-plugin/plugin.jsonexists, but there is no.claude-plugin/directory.plugin.jsonkeywords are onlycursor-plugin,developer-tools,blender, andauthor.emailis acontact@users.noreply.github.complaceholder.name,description) is already Claude-Code-compatible, so the content is ready and only the packaging is missing.Suggested approach
.claude-plugin/plugin.json, plusmarketplace.jsonif you want/plugin marketplace add TMHSDigital/Blender-Developer-Tools, pointing atskills/. CI-gate it the same way.cursor-plugin/plugin.jsonis gated (validate.yml:189-246).rulesskill, or aCLAUDE.mdinclude snippet summarizing the 9 rules, fromrules/*.mdcin CI so it can't drift.site.json.plugin.jsonplaceholder email and add keywords:claude-code,bpy,blender-addon,blender-python.Done when