Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

blender-addon-dev

/blender-addon-dev

Buduje, rozszerza, testuje i ocenia dodatki Blendera z natywnym interfejsem: panele, okna, menu kołowe i narzędzia modalne.

Licencja
GPL-3.0
Ostatnia zmiana repozytorium
07.11.2026

Ocena i bezpieczeństwo

93/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena13 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
4
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

GPL-3.0, otwarta.

Co robi i kiedy

Buduje, rozszerza, testuje i ocenia dodatki Blendera z natywnym interfejsem: panele, okna, menu kołowe i narzędzia modalne.

Wyzwalacze z opisu

wheelCopy AI Report
Oryginalny opis (EN)

Build, extend, test and review Blender add-ons (bpy, tested on Blender 5.2) so their UI feels native. Covers custom UI (panels, dialogs, popovers, pie and radial "wheel" menus drawn with gpu/blf, modal tools, toolbar tools, custom editors), writing into Blender's existing UI (menus, headers, native panels and popovers, the Properties editor, including a real-looking extra main tab via scripts/properties_tabs.py), AI review tooling (a right-click "Copy AI Report" add-on and a layout recorder), and how to verify all of it headless and in a real window with screenshots and simulated input. Use th

Jak działa

  1. Workflow
  2. Where should it go?
  3. Rules that hold everywhere
  4. Scripts
  5. Reference files
Sekcje z nagłówków SKILL.md, w oryginale · 106 linii, 1 132 słów
Podgląd SKILL.md
---
name: blender-addon-dev
description: Build, extend, test and review Blender add-ons (bpy, tested on Blender 5.2) so their UI feels native. Covers custom UI (panels, dialogs, popovers, pie and radial "wheel" menus drawn with gpu/blf, modal tools, toolbar tools, custom editors), writing into Blender's existing UI (menus, headers, native panels and popovers, the Properties editor, including a real-looking extra main tab via scripts/properties_tabs.py), AI review tooling (a right-click "Copy AI Report" add-on and a layout recorder), and how to verify all of it headless and in a real window with screenshots and simulated input. Use this skill whenever you create, edit, debug, test or review a Blender add-on or a bpy script that touches UI, operators, keymaps, handlers or registration, including Render Studio and unified_3d_workflow_tools, even if the user only says "Blender", "add-on", "panel", "N-panel", "Properties tab", "pie menu" or "bpy". Load ui-ux-design-thinking with it for any UI decision.
---

# Blender add-on development

This skill is built from two working add-ons: **Render Studio** (custom editor, hooks in
Blender's own panels and popovers, render queue) and **unified_3d_workflow_tools** (a
pipeline in an emulated Properties tab). Everything under `scripts/` was run in Blender 5.2
and has a test next to it. `<skill>` below means this folder.

Blender can't be restyled, so a native-feeling add-on comes down to placement (put each
thing where Blender users already look for it), Blender's own widgets and idioms, and state
the user can see. The ui-ux-design-thinking skill decides what goes where and why. This skill
says how to build that in bpy and how to prove it works.

## Workflow

1. **Understand.** Read the add-on's `docs/` (Render Studio keeps `DESIGN.md` and
   `UI_LEDGER.md`), its `register()` order, and where its data lives (Scene, Object,
   WindowManager, preferences). The memory note on headless testing applies to both
   add-ons: they live in `addons_core` (admin only, no git), so edit a staged copy.
2. **Place it** with the table below and ui-ux-design-thinking. Each part goes where its
   data belongs. The user dislikes N-panel (sidebar) add-ons, so the sidebar is the last
   choice, never the default.
3. **Build** from the scripts and recipes in `references/native-ui.md` and
   `references/custom-interaction.md`. Vendor scripts into the add-on unchanged.
4. **Verify** (`references/testing.md`): `validate_panels.py` headless after every UI
   edit; for new or changed UI, a GUI scenario with `bl_ui_harness.py`, then look at every
   PNG it writes. A change you haven't seen rendered isn't done.
5. **Report** UI changes as a decision ledger (append to the add-on's `docs/UI_LEDGER.md`
   when it has one), and run the design skill's slop gate.

## Where should it go?

| The user wants... | Build | Where to read |
|---|---|---|
| Settings of one datablock (object, material, world, scene) | Panel with `bl_context` of that Properties tab; subpanels via `bl_parent_id` | native-ui.md §1 |
| A whole workflow with its own home, like a Blender feature | **Extra Properties tab**: `scripts/properties_tabs.py` | native-ui.md §5 |
| A workspace-sized tool (boards, queues, graphs) | Custom editor from a `NodeTree` type (Editor Type menu), like Render Studio | native-ui.md §6 |
| A control inside Blender's own panel or popover | Subpanel with `bl_parent_id` set to Blender's panel (e.g. `VIEW3D_PT_shading`) | native-ui.md §3 |
| A command in an existing menu or header | `Menu.append` / `Header.append` | native-ui.md §2 |
| Blender's own panel to show something else | A draw wrapper installed once, never removed | native-ui.md §4 |
| A quick switcher in a header | Header popover (`bl_region_type='HEADER'`) | native-ui.md §2 |
| Pick one of up to 8 actions at the pointer | Blender's pie menu (`layout.menu_pie()`) | custom-interaction.md §1 |
| Pick from more than 8, or preview while hovering | `scripts/radial_menu.py` (the "wheel") | custom-interaction.md §2 |
| A tool that lives in the T toolbar | `WorkSpaceTool` + `bpy.utils.register_tool` | custom-interaction.md §4 |
| Click-drag in the viewport with drawn feedback | Modal operator + draw handler (gpu, blf) | custom-interaction.md §3 |
| Context for an AI about a button or panel | `scripts/ai_context_report/` add-on | ai-review.md |
| Progress of background work | Status bar append, and a progress bar where it started | native-ui.md §2 |

## Rules that hold everywhere

- **Never change a registered class in place.** Blender holds borrowed references to a
  registered class's functions. Replacing `poll` crashes it, and so does restoring a
  replaced `draw` while Blender still uses it (Render Studio, 2026-10-27). Safe ways: `append` /
  `prepend`; swapping an entry in `cls.draw._draw_funcs`; a wrapper installed once and
  re-pointed; or `unregister_class`, change, `register_class` (properties_tabs.py does this).
- **Blender's own words and widgets.** `use_property_split = True` with `use_property_decorate
  = False` for settings, `layout.panel()` for collapsible sections, list + side column of
  `+ - ▲ ▼`, `poll_message_set()` to say why something is disabled, `active = False` for "has
  no effect right now", `alert` for invalid. Operator labels are verbs the user would say.
- **Empty states:** one sentence on what the thing is for, plus the one button that starts it
  (`scale_y = 1.4` on that row only).
- **Hotkeys ship unassigned** and are listed in the add-on preferences
  (`rna_keymap_ui.draw_kmi`): Blender's keymap is crowded.
- **State the user can see:** a running job shows progress where it was started; a modal
  tool sets the status bar text and clears it on every exit path.
- **Draw code must be cheap and read-only.** Memoize anything that walks many items (a
  Render Studio board went from 5.7 s to 15 ms per redraw). Never write ID data in `draw()`.
- **Every handler is `@persistent`, and timers that must survive File > Open pass
  `persistent=True`.** Unregister them all.
- Read `references/pitfalls.md` before touching registration, handlers, timers, enum
  callbacks or the tab column.

## Scripts

| File | What it is |
|---|---|
| `scripts/properties_tabs.py` | Extra main tab in the Properties editor, drawn as a real tab. Vendor into the add-on. |
| `scripts/radial_menu.py` | `RadialMenuOperator` mixin: a wheel menu in the theme's pie colors, any number of items, hover preview, hold-and-release, keys 1-9. Includes the `view3d.select_type_wheel` example. |
| `scripts/ai_context_report/` | Installable add-on: right-click any button > **Copy AI Report**. Its `recorder.py` is a copy of `scripts/recorder.py` (the add-on must stand alone): change both. |
| `scripts/recorder.py` | A stand-in `UILayout` that records a draw function's calls with their source lines (outline, find, validate). |
| `scripts/validate_panels.py` | `blender -b` check of every panel, header and menu of an add-on: unknown properties, operators, icons, draws that raise. |
| `scripts/bl_ui_harness.py` | Windowed test driver: generator steps, screenshots, simulated mouse and keys, exit code. |
| `scripts/tests/` | GUI tests for the three features above (the tab also with two add-ons sharing the column), plus `demo_tab/`, a minimal add-on using the tab. |

Run a GUI test (Blender ignores the real mouse and keyboard while it runs, so the user can
keep working):

```
"C:\Program Files\Blender Foundation\Blender 5.2\blender.exe" --factory-startup --enable-event-simulate ^
  --window-geometry 0 0 1400 900 --python <skill>\scripts\tests\test_properties_tab.py -- <out_dir>
```

## Reference files

- `references/native-ui.md`: every surface Blender offers an add-on and how to write into
  Blender's existing UI: panels in Properties tabs, menus, headers, popovers, subpanels in
  native panels, draw wrappers, layout proxies, the extra Properties tab (and porting
  unified_3d_workflow_tools to it), custom editors, and native look recipes.
- `references/custom-interaction.md`: pie menus, the radial wheel, modal operators, gpu and
  blf drawing in 5.2, theme colors, toolbar tools, keymaps, gizmos.
- `references/ai-review.md`: the Copy AI Report add-on, what a report contains, how to act on
  one you're given, and the AI design-review loop with screenshots and layout outlines.
- `references/testing.md`: staging, headless tests, `validate_panels.py`, the GUI harness,
  simulated input quirks, screenshots, the Blender MCP, deploying to `addons_core`.
- `references/pitfalls.md`: crashes, silent failures and 5.x changes that cost time before.
Pliki w paczce (4)
  • .gitignore 1 KB
  • LICENSE 34 KB
  • README.md 10 KB
  • SKILL.md 8 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · N4m-N4m/blender-addon-dev-skill93GPL-3.0
TerminalSkills/skills100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 42ca14a7237a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100blender-addon-development
    Pisze dodatki do Blendera 5.2 jako rozszerzenia: blender_manifest.toml, operatory, panele, menu i preferencje, zasady bpy.props po wersji 5.0, undo, tryby modalne, rysowanie gpu, pakowanie wheels, CLI i testy bez interfejsu.
  • 100blender-addon-development
    Prowadzi tworzenie dodatków Blendera: operatory, panele UI, bpy.props, metody poll() i rejestracja.
  • 100blender-syntax-panels
    Pomaga tworzyć panele, menu i listy UIList w interfejsie Blendera, dobierając poprawne typy przestrzeni i regionu.
  • 100blender-python-addon
    Podpowiada dobre praktyki pisania dodatków do Blendera w API bpy: operatory, panele, właściwości, rejestrację, bezpieczne skryptowanie i debugowanie w konsoli Pythona.
  • 100blender-addon-engineer
    Działa jako specjalista od narzędzi Blendera: buduje dodatki w Pythonie, walidatory zasobów, eksportery i automatyzacje potoku, które zamieniają powtarzalną pracę w niezawodne przepływy jednym kliknięciem.
  • 100blender-impl-addons
    Projektuje, testuje i pakuje dodatek produkcyjny do Blendera, w tym strukturę plików, CI/CD i manifest dla extensions.blender.org.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.