view-bridge

Coordinate editor lifecycle and view attachment protocols for Pulp audio plugins.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill view-bridge-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: view-bridge
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/view-bridge
Command: npx skills add https://github.com/Generous-Corp/pulp --skill view-bridge-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of managing the editor lifecycle, view attachment, and host-plugin communication protocols across multiple audio plugin formats (VST3, AU, CLAP, AAX). It prevents common bugs like window leaks, automation latching issues, and ABI mismatches.

Core Features & Use Cases

  • Lifecycle Management: Standardizes the open, notify_attached, resize, and close protocol for plugin editors.
  • Format Adapter Support: Provides the necessary invariants and hooks for implementing new format adapters or overriding Processor::create_view.
  • Use Case: When developing a custom UI for a VST3 or CLAP plugin, use this skill to ensure your editor correctly handles host-side resizing, keyboard routing, and proper teardown to avoid automation record leaks.

Quick Start

Use the view-bridge skill to verify the current processor implementation against the required editor lifecycle protocol.

Frequently Asked Questions about view-bridge

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

FAQPage Schema
How do I manage the editor lifecycle for a VST3 or CLAP audio plugin?

Managing the audio plugin editor lifecycle requires standardizing the open, notify_attached, resize, and close protocols to prevent window leaks and ensure proper teardown across diverse host formats.

What causes automation record leaks and host-side crashes during plugin editor teardown?

Automation record leaks and host-side crashes during plugin editor teardown occur from improper thread-safe destruction and ABI mismatches, requiring strict synchronization procedures to prevent memory corruption.

How do I attach custom view trees and secondary inspector windows to audio plugins?

Attaching custom view trees and secondary inspector windows requires coordinating multi-view attachment protocols that facilitate integration while ensuring consistent parameter gesture handling and host-side automation synchronization.

Can I use this approach to implement new format adapters for audio plugins?

Implementing new format adapters requires providing the necessary invariants and hooks for overriding Processor::create_view, ensuring proper editor lifecycle management across VST3, AU, CLAP, and AAX formats.

Why does my audio plugin editor fail to handle host-side resizing and keyboard routing?

Audio plugin editor resizing and keyboard routing fail when the editor lifecycle protocol is not correctly implemented, preventing proper host-plugin communication and causing automation latching issues.