reactor-docking

Create IDE-shaped layouts with dockable and tear-out tool windows.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/kusutori/DataViewer --skill reactor-docking-kusutori
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reactor-docking
Source: https://github.com/kusutori/DataViewer/tree/main/skills/reactor-docking
Command: npx skills add https://github.com/kusutori/DataViewer --skill reactor-docking-kusutori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides the necessary tools to create complex IDE-/Office-shaped layouts with dockable tool windows and document wells, addressing the need for flexible and customizable UI designs in applications.

Core Features & Use Cases

  • DockManager: Hosts a tree of dockable panes for drag, split, tear-out, re-dock, and pin operations.
  • Content vs Shape Ownership Model: Follows the rule that the app owns content and the host owns shape, ensuring a robust and predictable UI behavior.
  • Use Case: Ideal for building applications with a multi-document interface, like IDEs or productivity software, requiring dynamic and customizable UI elements.

Quick Start

Initialize the DockManager by calling DockingNativeInterop.Register(host.Reconciler) during startup.

Frequently Asked Questions about reactor-docking

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

FAQPage Schema
How do I build an IDE-style layout with dockable tool windows and document wells?

To build an IDE-style layout with dockable tool windows, initialize the DockManager during startup by calling DockingNativeInterop.Register on the host reconciler to enable drag, split, tear-out, and pin operations.

What is the content vs shape ownership model in UI docking layouts?

The content vs shape ownership model dictates that the application owns the content while the host owns the shape, ensuring robust and predictable UI behavior during layout management and reconciliation.

Do I need a host reconciliation system to manage dockable tool windows?

Yes, managing dockable tool windows requires integration with the host's reconciliation system to properly handle shape management and ensure predictable UI layout behavior.

Can I create tear-out and re-dock functionality for productivity software UI layouts?

Yes, you can create tear-out and re-dock functionality for productivity software UI layouts by using the DockManager, which hosts a tree of dockable panes supporting these specific drag and pin operations.

What is the best way to structure a multi-document interface with dynamic UI elements?

The best way to structure a multi-document interface is using a DockManager to handle complex IDE- or Office-shaped layouts, separating application content ownership from the host's shape management.