Build an add-on with AI

Check your materials, then build a small first window

Describe your idea, let AI write code with the Skill, then try it in Blender and give feedback. Nexus UI Web hosts the interface; the Skill supplies AI with guides, templates, and tools.

Get started: Framework source, official examples, and starter templates are available in the project's GitHub repository. Obtain matching framework and template versions before building. Runtime components are installed separately through the add-on's download card.

• Have the materials: Prepare the complete Skill, framework, and template from the same source and give AI their paths or an accessible repository URL. Check the materials list.
• No materials yet: You can first try the browser demos or plan your tool. Stop at preparation if files are missing; copying instructions does not obtain materials.
• Computer requirements: Blender 5.0.0 and later, Apple silicon Mac · Windows x64. Runtime components are not currently available for Intel Macs or Linux. View requirements.
• AI tool: Requires an AI tool that supports local Skills, can read and write project files, and can run the required build commands. This tutorial uses local Codex; for other tools, see Tools and installation. Chat-only tools cannot install for you, and ordinary cloud sessions cannot inspect local Blender directly.
• Only using an add-on: You do not need the Skill or development tools. Follow requirements for using a finished add-on.

Start with My Scene: one button reading scene name and object count. Ask AI to check Python and matching materials. For missing runtime components, use Runtime components. Complete opening, reading, closing, and reopening before adding features.

Copy setup instructions for Codex

Copy the instructions below, paste them into Codex, and send. It will verify the source, obtain complete materials, install in a supported location, and check recognition. You need not research installation directories yourself.

Framework source, official examples, and starter templates are available in the project's GitHub repository. Send your material source with the instructions. If you have no materials, complete preparation above first.

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.

Copied means the text reached the clipboard, not that installation finished. Codex must execute and verify it. This route requires local file access and Skill support; chat-only tools cannot install directly.

Confirm installation

Send the verification instructions after installation. Codex discovers new Skills automatically and should recognize Nexus UI Web and read its entry point and references. If absent, restart and check again.

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.

Manual installation

Obtain the complete Skill directory from the provider, preserving its entry point, licenses, notices, references, scripts, and templates. Do not copy only SKILL.md. The Skill does not contain the framework or runtime components and is not a Blender add-on. You can give its location to Codex with the instructions above.

Place the complete nexus-ui-web folder in the user's .agents/skills/ so the entry point is at ~/.agents/skills/nexus-ui-web/SKILL.md. Compare any existing Skill with the same name rather than accumulating copies.

Source: OpenAI's official Skills documentation. It defines local loading locations; verify this project's complete workflow in the target environment.

Copy your first request and build a usable window

Give the request below to Codex after Skill recognition. Confirm the new add-on location and build from the template. If unsure where to save it, ask what each location is for.

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.

See Complete starter tutorial for template and opening steps without needing to understand every line first. Generated files, visible pages, and successful Blender actions are three different outcomes.

Turn the examples into your own tools

The three homepage demos simulate browser interactions. Use these requests as starting points; confirm generated layout and behavior afterward. An exact match to the website is not guaranteed in one attempt.

Scene controls: Everyday operations. One panel.

Select objects and adjust transforms, with your everyday scene tools in one place.

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.

You can follow up: “Put the scale control at the top and add a reset button next to its value.” Explore scene integration.

Transparency and floating tools: Floating tools you can move.

Place tools over the viewport and organize controls in shapes and layouts that suit the task.

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.

You can follow up: “Make the interface more compact, keep a drag area, and arrange the colors in one row.” Explore transparent shapes and dragging.

Texture studio: Preview first. Apply when ready.

Choose textures, tune surface properties, and apply the result in one interface.

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.

You can follow up: “Make the preview larger so I can inspect the texture before applying it.” Explore images and resources.

Try the corresponding demo →

Start from a reference image

Give Codex an image you have rights to use, identify the relevant layout and colors, and describe what each main button should do. Images convey appearance; behavior still needs words.

Use the Nexus UI Web Skill and my attached reference image to build a window for my Blender add-on. Keep the layout hierarchy and color palette. Adapt the text to English and replace content with my own functionality. Start with one button that reads and displays current scene information. Confirm the project location, reference scope, and button behavior before building. Do not assume every feature in the image already exists.

Check layout and one real operation first, then refine details. Window size, fonts, and assets affect the final appearance.

Review the first version, then refine through conversation

Continue in the same add-on project and specify what to keep and change: for example, keep reading functionality, narrow the window, and move the button right. Do not recreate the add-on each time.

Use the Nexus UI Web Skill to continue my Blender add-on. Confirm the existing project location and preserve its functionality and entry point. Change only this: make the window narrower and put the read button to the right of the title. Check that it still reads the scene and can reopen after closing. Do not recreate the project, upgrade the framework, or change unrelated features.

For search, image import, or other additions, request one complete small goal at a time. See Continue development and diagnose problems; when ready to deliver a package, read Package and deliver your add-on.

Continue according to your current project

• No existing add-on: use the first request above to create an independent project.
• Existing add-on needing a web UI: provide source, describe one new window and features to preserve. See Integrate into an existing add-on.
• Existing Nexus UI Web window: continue the same project with its entry point and framework version.

Check results and troubleshoot

Ask Codex what it actually verified. At minimum, check opening, reading the real scene correctly, closing, and reopening. Screenshots or browser previews alone do not prove Blender integration.

• Skill not recognized: Check the complete folder and loading location, restart Codex, and check duplicate or disabled Skills.
• No framework source: Follow Obtain materials Obtain the provider's matching source materials.
• Runtime missing or installation failed: First follow Runtime components; if it fails, see Installation troubleshooting.
• Window does not open or page is blank: See respectively Window did not open and Blank page.
• Button does nothing: Record the action, expectation, and actual result, then follow Operation troubleshooting to diagnose further.

For further real-operation checks, see Local preview and Blender verification. Drag feel and animation smoothness require personal hands-on confirmation.

Choose an AI tool and installation method

This tutorial uses local Codex by default; complete environment and opening checks to verify usability. Claude Code and Cursor also document local Skill directories, but their full installation-to-Blender workflow has not been tested end to end for this project.

• Claude Code: ~/.claude/skills/nexus-ui-web/. See official Skills documentation.
• Cursor: ~/.cursor/skills/nexus-ui-web/. See official Skills documentation.

This describes local tools. Cloud sessions and other products differ in installation, file access, and Blender preview capabilities; do not assume the same guarantees.