Build Blender add-on interfaces from ideas and reference images, one step at a time.
AI uses the companion Skill to write and revise code. You check the results in Blender. Start with a small window that opens, reads the scene, closes, and opens again.
An optional way to build · The same framework and public APIs
IDEA → CODE → WORKING TOOL
01
Describe your idea
Describe the layout, reference images, and what each button should do.
02
Build with AI assistance
Use the Skill and template to write code and connect Blender functionality.
03
Check it in Blender
Check the actual result, then give feedback to refine it.
01 / GET READY
Prepare your materials. Then build your first window.
Requires an AI tool that supports local Skills, can read and write project files, and can run the required build commands, plus the matching framework, template, and Blender. The Skill provides guidance; it does not include the framework or runtime components.
Give AI the installation instructions and your available materials to prepare the environment.
Read the full instructions
Please install the Nexus UI Web Skill for me. I want to use it to build attractive Blender add-on interfaces. First confirm that you can access local files and support local Skills. If not, tell me directly.
Framework source, official examples, and starter templates are available in the project's GitHub repository.
Official source: https://github.com/AIGODLIKE/NexusUIWeb; complete Skill: https://github.com/AIGODLIKE/NexusUIWeb/tree/main/skill/nexus-ui-web. Prefer the authorized local materials I have already provided; otherwise obtain them from the official repository. If the repository is inaccessible or required files are missing, explain what is missing and ask me for access or complete authorized local materials. Do not proceed, guess alternative sources, or claim success before obtaining them.
If I provide a repository URL, verify its source and obtain the complete nexus-ui-web Skill directory. If I provide local files, read them directly. Preserve all contents of SKILL.md, LICENSE, NOTICE.md, references, scripts, assets, and agents.
For Codex, install to ~/.agents/skills/nexus-ui-web for the current user. For other tools, first verify their official Skill installation location. If a Skill with the same name exists, compare and explain the differences before replacing it; do not duplicate it.
Check files and relative references, confirm you can recognize and read the Skill, and tell me whether a new conversation or restart is required.
This step installs only the Skill. Do not install a Blender add-on or runtime components, modify my project, or commit code.
02
Confirm it is recognized
Ask AI to confirm it can read the Skill, framework, and template before building.
Read the full instructions
I want to build a Blender add-on interface with the Nexus UI Web Skill. Confirm that you recognize it, read its entry point and reference materials, and explain its purpose in one sentence. Check the environment first; do not create an add-on yet. Requires Blender 5.0.0 or later, supporting Apple silicon Mac · Windows x64. Check Python, the available Nexus UI Web framework and templates, and runtime component status.
Framework source, official examples, and starter templates are available in the project's GitHub repository.
The official framework comes from https://github.com/AIGODLIKE/NexusUIWeb under nexus_web/. If no local copy is available, verify repository access and the required files. If complete materials cannot be obtained, explain what is missing, ask me for access or complete authorized local source, and stop at preparation. Distinguish files being ready from successful execution in Blender.
03
Build a small window
Start with My Scene: a button that reads the scene name and object count.
Read the full instructions
Use the Nexus UI Web Skill to create a standalone Blender add-on for me.
Confirm where to save it first; do not modify the framework or official examples.
Interface: a compact dark window titled My Scene, a Read Scene button, and a clear results area.
Clicking the button should show the current Blender scene name and object count.
For this first version, implement only opening the window, reading information, closing, and reopening it. Do not modify scene content.
Check the environment and framework source, then build from the Skill template.
Framework source, official examples, and starter templates are available in the project's GitHub repository.
Official source: https://github.com/AIGODLIKE/NexusUIWeb. If materials are missing and the repository is inaccessible or incomplete, explain what is missing and ask for access or complete authorized local source. Do not continue building or create fake framework files before obtaining them. If runtime components are missing, explain and ask me to confirm installation. Tell me where to open the add-on and which operations were actually checked. Do not automatically commit, push, or publish.
Copying instructions only copies text. Your tool must perform installation and check the real result.
02 / DESCRIBE YOUR IDEA
Make your request concrete.
Describe the layout to keep, what to change, and what should happen when a button is clicked. Reference images show appearance; describe behavior in words. State explicitly if the window needs edge resizing; using a component library does not enable it automatically.
01 / Scene controls
Everyday operations. One panel.
Build a compact scene tool that lets me select an object, adjust position, rotation, and scale, and see the changes in the interface.
Read the request to copy
Use the Nexus UI Web Skill to build an interface for my Blender add-on.
Build a compact scene tool that lets me select an object, adjust position, rotation, and scale, and see the changes in the interface.
First confirm my project location, framework source, and the actions the buttons should perform. Explain any missing materials. Do not modify the framework or official examples.
Build a draggable floating tool for adjusting a model's color and size, with an interface that goes beyond a rectangular box.
Read the request to copy
Use the Nexus UI Web Skill to build an interface for my Blender add-on.
Build a draggable floating tool for adjusting a model's color and size, with an interface that goes beyond a rectangular box.
First confirm my project location, framework source, and the actions the buttons should perform. Explain any missing materials. Do not modify the framework or official examples.
Build a texture studio where I can switch textures, adjust surface parameters, and apply the result to an object.
Read the request to copy
Use the Nexus UI Web Skill to build an interface for my Blender add-on.
Build a texture studio where I can switch textures, adjust surface parameters, and apply the result to an object.
First confirm my project location, framework source, and the actions the buttons should perform. Explain any missing materials. Do not modify the framework or official examples.
The assistant is an optional integration example inside the add-on, a separate use from building add-ons with AI. It needs uv, an isolated environment, and your own compatible service URL, credentials, and model. You pay third-party service charges. Scene tools also need model tool-calling support and Blender MCP configuration; fetching a model list does not verify chat or scene actions.
Nexus