ignition-designer-hook

Integrate DesignerHook tasks into Ignition SDK module projects.

Updated Apr 9, 2026

Search Tags:#integration #workspace #designer #ui-wiring #ignition sdk #designer-hook

Ready to run

npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill ignition-designer-hook

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ignition-designer-hook
Source: https://github.com/Sheon-S/ignition-sdk-agent-kit/tree/main/.agents/skills/ignition-designer-hook
Command: npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill ignition-designer-hook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DesignerHook integration, designer workspace and menu wiring, editor and resource integration, and designer-scope boundary guidance for Ignition SDK modules. Use when tasks touch DesignerHook, designer UI, menus, palettes, workspaces, editors, icons, designer resources, or shared contracts consumed by designer code.

Core Features & Use Cases

Keep designer-only behavior in designer scope.
Route shared contracts through common when they are truly shared.
Consume shared DTO contracts from common.

Quick Start

Map your DesignerHook touchpoints to the designer workspace, menus, and editor resources described here.

Frequently Asked Questions about ignition-designer-hook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I wire UI integration and menus in an Ignition SDK module?▼

Wire UI integration by mapping DesignerHook touchpoints to the designer workspace, menus, and editor resources. This isolates designer-specific behavior to keep UI work safely within the designer scope.

When do I need to separate designer scope from gateway internals in Ignition?▼

Separate designer scope from gateway internals when your module task touches designer UI, workspaces, palettes, or editors. Isolating this behavior prevents unwanted coupling and ensures safe sharing via common contracts.

What is the best way to manage shared contracts across Ignition module teams?▼

Manage shared contracts across Ignition module teams by routing truly shared elements through common. Consume shared DTO contracts from common to ensure safe sharing and avoid coupling to gateway internals.

Does Ignition SDK support custom designer resources and workspace palettes?▼

Yes, Ignition SDK supports custom designer resources and workspace palettes. You can integrate custom icons and editor resources directly into the designer workspace by applying DesignerHook tasks within your module project.

Why does my Ignition designer UI code couple to gateway internals?▼

Designer UI code couples to gateway internals when designer-specific behavior is not properly isolated. Keep designer-only behavior within the designer scope and route shared data through common DTO contracts to prevent this.

How do I integrate icons and editor resources into an Ignition designer workspace?▼

Integrate icons and editor resources into an Ignition designer workspace by applying DesignerHook tasks. This maps your resource touchpoints directly to the designer scope, keeping UI elements strictly within the workspace boundary.