MCP backend

Use when: Multi-skill Blender orchestration, skill graph audits, resolving overlaps between text-to-blender/pro-workflow/reference-to-3d/wireframe/UV/fit/repair skills, defining source-of-truth precedence, artifact contracts, and sequential-vs-parallel execution plans.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Blender Skill Harmonizer

This is the meta-layer for the Blender skill stack. It prevents independently useful skills from producing incoherent work when combined.

Use a Merge → Consistency → Optimize → Store cycle:

1. Merge: list all triggered skills and their intended outputs.
2. Consistency: detect conflicts in assumptions, coordinate systems, source hierarchy, object naming, or validation gates.
3. Optimize: choose one orchestrator, one source-of-truth policy, and a staged/parallel execution plan.
4. Store: write the chosen plan and durable lessons into project docs/memory.

Skill category map