addon-scaffoldinglisted

# Addon Scaffolding (Extensions Platform) ## Trigger Use this skill when the user: - Wants to start a new Blender add-on - Mentions `bl_info`, `blender_manifest.toml`, "extension", "register_classes_factory" - Is migrating an existing add-on from the legacy `bl_info` format to the Extensions Platform - Is unsure which file layout or registration pattern to use for Blender 4.5+ or 5.x ## Required inputs - **Add-on name and short id** (snake_case for the manifest `id`, human-readable `name`) - **Target Blender versions** (defaults to `blender_version_min = "4.5.0"` so the add-on works on 4.5 LTS and 5.1) - **Maintainer string** (`Name <email@example.com>` form) - **License SPDX identifier** (`SPDX:MIT`, `SPDX:GPL-2.0-or-later`, etc.) ## The Extensions Platform format (5.x default) Since 4.2 and required in 5.x for new submissions to the official extensions site, add-ons ship as Extensions. An Extension is a directory containing a `blender_manifest.toml` plus Python modules. ### `blender_manifest.toml` required fields ```toml schema_version = "1.0.0" id = "my_addon" version = "0.1.0" name = "My Add-on" tagline = "Short description, max 64 chars, no trailing period" maintainer = "TMHSDigital <contact@example.com>" type = "add-on" blender_version_min = "4.5.0" license = ["SPDX:MIT"] copyright = ["2026 TMHSDigital"] ``` Field rules that AIs commonly get wrong: - `tagline` is hard-capped at 64 characters and **must not end with a period**. Blender's manifest validator