bridge-patterns

Define standardized Bridges for plugin-core communication in BrainDrive development.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill bridge-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bridge-patterns
Source: https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode/tree/main/.claude/skills/bridge-patterns
Command: npx skills add https://github.com/BrainDriveAI/BrainDrive-Plugin-Builder-ClaudeCode --skill bridge-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges provide a standardized interface for plugin components to communicate with BrainDrive core services, enabling data access, settings persistence, theming, event handling, and state management without leaking internals.

Core Features & Use Cases

  • API Bridge to call BrainDrive backend endpoints for conversations, messages, and settings.
  • Settings Bridge to store and retrieve per-user plugin configuration.
  • Theme Bridge to align UI with BrainDrive color and theming.
  • Event Bridge to subscribe to and react to BrainDrive events (e.g., messages, conversations, user changes).
  • Plugin State Bridge to persist plugin state across sessions (local or backend).
  • Log Bridge to emit structured logs to BrainDrive.
  • Real-world use: A chat plugin reads user preferences from Settings Bridge, displays data via API Bridge, adapts UI with Theme Bridge, and persists last viewed thread via Plugin State Bridge.

Quick Start

Create a new plugin project and wire up the API, Settings, and Theme Bridges to begin exchanging data with BrainDrive.

Frequently Asked Questions about bridge-patterns

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

FAQPage Schema
How do I handle plugin-core communication in BrainDrive plugin development?

Plugin-core communication is handled using standardized Bridges for API calls, settings, themes, events, and state, preventing internal service leakage. They provide a consistent interface for frontend components to interact with backend services without exposing internals.

What's the best way to persist per-user plugin settings in a BrainDrive frontend?

To persist per-user plugin settings in a BrainDrive frontend, use the Settings Bridge to store and retrieve configurations. This ensures user preferences are maintained across sessions without direct backend access.

How do I subscribe to BrainDrive events like conversation or user changes from a plugin?

You subscribe to BrainDrive events by implementing the Event Bridge within your plugin. This allows frontend components to react to messages, conversations, and user changes through a standardized event handling interface.

Does BrainDrive plugin development provide a standard way to align plugin UI with core themes?

BrainDrive plugin development provides a Theme Bridge to align plugin UI with core themes. This standardizes how frontend components adapt to BrainDrive color schemes and theming rules without hardcoding values.

Can I persist plugin state across sessions locally or on the backend?

You can persist plugin state across sessions locally or on the backend using the Plugin State Bridge. This allows plugins to maintain stateful data like last viewed threads between user interactions reliably.

How do I call BrainDrive backend endpoints for conversations and messages from a plugin?

To call BrainDrive backend endpoints for conversations and messages, implement the API Bridge in your plugin. This provides a structured method to request data from backend services without managing direct HTTP connections.