Source Part Segmentation logo

Source Part Segmentation

Community
RobLe3
source-part-segmentation

Segment overlapping visual parts from source images, wireframes, texture atlases, and decals before mesh reconstruction. Use when a mascot/logo/template contains touching or overlapping components and exact structural part masks are needed before contour-to-mesh, UV fitting, or landmark repair.

Overview

PublisherRobLe3
Repositorycc-blender-skill
Skill namesource-part-segmentation
Stars
131
Forks
14
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by RobLe3 on GitHub. Read the source before you install it.

Installation

Install the Source Part Segmentation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/source-part-segmentation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RobLe3/cc-blender-skill.git /tmp/cc-blender-skill
mkdir -p .claude/skills
cp -r /tmp/cc-blender-skill/plugin/skills/source-part-segmentation .claude/skills/source-part-segmentation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Source Part Segmentation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Source Part Segmentation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Source Part Segmentation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

MCP backend

Use when: Overlapping part extraction, component masks, marker/watershed segmentation, contour hierarchy analysis, atlas part isolation, manual seed fallback for source-locked Blender reconstruction.

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.

Source Part Segmentation

Use this before contour-to-mesh when a source image contains overlapping or touching designed parts. The output is not “nice masks”; it is a source-of-truth part inventory that downstream geometry must obey.

Inputs

  • source image, wireframe, decal, or texture atlas;
  • optional manual seed manifest with named parts, polygons, seed points, rough rectangles, or HSV/color ranges;
  • source manifest with structural/decorative/context classification and expected part count.

Workflow

  1. Choose the cleanest modality: alpha, edge, dark-line, bright-on-dark, color-band, or atlas region.
  2. Extract contours and hierarchy to identify candidate objects, holes, nested details, and strokes.
  3. If components touch, run distance-transform marker watershed first.
  4. If watershed over/under-splits, switch to seeded segmentation:
    • create named part seeds (bbox, polygon, or seed_point + optional flood/HSV tolerance);
    • save one mask per named structural part;
    • mark ambiguous overlaps explicitly instead of merging them.
  5. Classify masks as structural, decorative, face_feature, aura_context, or validation_only.
  6. Pass structural masks to contour-to-mesh; pass feature masks/landmarks to landmark-fit-repair; pass atlas regions to atlas-uv-fitting.

Hard rules

  • Do not infer repeated parts from symmetry; segment what the source shows.
  • Do not merge overlapping components if the manifest expects separate structural meshes.
  • Do not proceed to final modeling when part count differs between source images; write a conflict report or canonical policy.
  • If automatic segmentation is ambiguous, write an ambiguity report and require or create manual seed rectangles/points.
  • Keep stroke/line masks separate from filled-part masks; wireframe strokes are guides unless explicitly used as the contour boundary.

Seed manifest schema

json
{
  "schema": "source_part_seed_manifest.v1",
  "image": "path/to/source.png",
  "parts": [
    {"name":"leaf_top", "class":"structural", "bbox":[x,y,w,h], "mode":"non_background"},
    {"name":"face_shell", "class":"structural", "polygon":[[x,y],[x,y],...], "mode":"polygon"}
  ]
}

Allowed mode values: polygon, bbox, non_background, dark_lines, bright_on_dark, hsv_range.

Scripts

  • scripts/segment_source_parts.py produces component masks and a JSON report from an image, with optional watershed.
  • scripts/seeded_part_masks.py converts a named seed manifest into deterministic named masks and a part inventory.

Sources distilled

  • OpenCV contours/hierarchy/moments are the base measurement layer.
  • OpenCV distance transform + marker watershed is the first automated split method for touching components.
  • Active contour refinement can improve a rough mask boundary after segmentation.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Source Part Segmentation AI skill do?

Segment overlapping visual parts from source images, wireframes, texture atlases, and decals before mesh reconstruction. Use when a mascot/logo/template contains touching or overlapping components and exact structural part masks are needed before contour-to-mesh, UV fitting, or landmark repair.

Why use Source Part Segmentation on TypingMind?

Because you install it once and use it with any model. Source Part Segmentation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Source Part Segmentation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/source-part-segmentation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Source Part Segmentation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Source Part Segmentation?

As many as you like. As long as a model supports skills, you can use Source Part Segmentation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Source Part Segmentation AI skill free?

Yes. It is published on GitHub by RobLe3 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇