create-plugin
The create-plugin skill provides a complete architectural guide and implementation contract for building plugins within the Sidecar application framework. Use this when developing new plugins to understand the Bubble Tea model integration, required interface methods, plugin lifecycle stages from registration through cleanup, context provisioning, command mapping, and epoch-based stale message detection for async operations.
git clone --depth 1 https://github.com/marcus/sidecar /tmp/create-plugin && cp -r /tmp/create-plugin/.claude/skills/create-plugin ~/.claude/skills/create-pluginSKILL.md
# Create Plugin
## Architecture Overview
- **Bubble Tea model**: `internal/app/model.go` owns the active plugin index, dispatches key events, renders plugin views.
- **Registry**: `internal/plugin/registry.go` stores plugins, handles lifecycle with panic protection, keeps an `unavailable` map when `Init` fails (silent degradation).
- **Plugin contract**: `internal/plugin/plugin.go` defines the interface every plugin must satisfy.
- **Context**: `internal/plugin/context.go` provides `WorkDir`, `ConfigDir`, `Adapters`, `EventBus`, `Logger`, `Epoch`, and `Keymap`.
- **Keymap**: `internal/keymap` maps keys to command IDs. Footer/help reads bindings by context using `Plugin.Commands()` + `Plugin.FocusContext()`.
## Plugin Interface
Every plugin must implement all of these methods:
```go
ID() string // Stable kebab-case identifier
Name() string // Short human label for headers/help
Icon() string // Single-character glyph for tab strip
Init(ctx *Context) error // Lightweight setup; return error to degrade gracefully
Start() tea.Cmd // Kick off async work (non-blocking)
Update(msg tea.Msg) (Plugin, tea.Cmd) // Pure state transition
View(width, height int) string // Render within provided dimensions
IsFocused() bool // Check focus state
SetFocused(bool) // App calls this on tab switch
Commands() []plugin.Command // Footer hints per context
FocusContext() string // Current context name for keymap
Stop() // Idempotent cleanup
```
Optional: implement `Diagnostics() []plugin.Diagnostic` for the diagnostics overlay.
## Lifecycle Order
1. **Registration** (`cmd/sidecar/main.go`): `registry.Register(myplugin.New())`. No work here.
2. **Init**: Detect prerequisites (repos, adapters, env vars). Use `ctx.Logger` for warnings. Return error to degrade gracefully.
3. **Start**: Batch initial commands with `tea.Batch`. Never block.
4. **Update**: Pattern-match on custom `Msg` types and `tea.KeyMsg`. Keep I/O in commands, not directly in Update.
5. **View**: Render only; no side-effects. Honor `width/height`.
6. **Focus/Blur**: `SetFocused` called on tab switch. Pause expensive work when unfocused.
7. **Stop**: Close watchers, timers, channels. Guard with `sync.Once`/flags.
## Epoch Pattern (Stale Message Detection)
When switching projects/worktrees, async operations may deliver stale data. Use the epoch pattern:
### Step 1: Add Epoch to message type
```go
type MyDataLoadedMsg struct {
Epoch uint64
Data string
Err error
}
func (m MyDataLoadedMsg) GetEpoch() uint64 { return m.Epoch }
```
### Step 2: Capture epoch in command creators
```go
func (p *Plugin) loadData() tea.Cmd {
epoch := p.ctx.Epoch // Capture synchronously before closure
return func() tea.Msg {
data, err := fetchData()
return MyDataLoadedMsg{Epoch: epoch, Data: data, Err: err}
}
}
```
### Step 3: Check staleness in Update
```go
case MyDataLoadedMsg:
if plugin.IsStale(p.ctx, msg) {
return p, nil // Discard stale message
}
p.data = msg.Data
```
Apply this to any async message that fetches data from filesystem/external sources or updates project-specific state.
## Keymap, Contexts, and Commands
- Define **contexts** mirroring your view modes (e.g., `git-status`, `git-diff`). Return the active one from `FocusContext()`.
- Expose **commands** with matching contexts via `Commands()`. These power footer hints and help overlay.
- Add default **bindings** in `internal/keymap/bindings.go`.
- Keep command IDs stable (verbs preferred: `open-file`, `toggle-diff-mode`).
### Command structure
```go
plugin.Command{
ID: "stage-file",
Name: "Stage", // Keep 1-2 words max
Category: plugin.CategoryGit,
Priority: 10, // Lower = higher priority; 0 treated as 99
Context: "git-status",
}
```
Categories: `CategoryNavigation`, `CategoryActions`, `CategoryView`, `CategorySearch`, `CategoryEdit`, `CategoryGit`, `CategorySystem`
### Context naming convention
- `plugin-name` for main view
- `plugin-name-detail` for detail/preview
- `plugin-name-modal` for modals
- `plugin-name-search` for search modes
### Dynamic binding registration
```go
func (p *Plugin) Init(ctx *plugin.Context) error {
if ctx.Keymap != nil {
ctx.Keymap.RegisterPluginBinding("g g", "go-to-top", "my-context")
}
return nil
}
```
## Event Bus (Cross-Plugin Communication)
- Subscribe: `ch := ctx.EventBus.Subscribe("topic")` in `Start()`, forward messages into `Update`.
- Publish: `ctx.EventBus.Publish("topic", event.NewEvent(event.TypeRefreshNeeded, "topic", payload))`.
- Best-effort, buffered (size 16), drops when full. Design listeners to be resilient.
## Inter-Plugin Messages
App-level messages (`internal/app/commands.go`):
- `FocusPluginByIDMsg{PluginID}` / `app.FocusPlugin(id)`
File browser messages (`internal/plugins/filebrowser/plugin.go`):
- `NavigateToFileMsg{Path}` - navigate to and preview a file
Pattern for cross-plugin navigation:
```go
func (p *Plugin) openInFileBrowser(path string) tea.Cmd {
return tea.Batch(
app.FocusPlugin("file-browser"),
func() tea.Msg { return filebrowser.NavigateToFileMsg{Path: path} },
)
}
```
## Plugin Focus Events
`PluginFocusedMsg` (from `internal/app`): sent when your plugin becomes active tab. Use to refresh data only needed when visible:
```go
case app.PluginFocusedMsg:
if p.pendingRefresh {
p.pendingRefresh = false
return p, p.refresh()
}
```
## External Editor Integration
```go
func (p *Plugin) openFile(path string, lineNo int) tea.Cmd {
editor := p.ctx.Config.EditorCommand
return func() tea.Msg {
return plugin.OpenFileMsg{Editor: editor, Path: path, LineNo: lineNo}
}
}
```
## Rendering Rules
**CRITICAL: Always constrain plugin output height.** The app header/footer are always visible. Plugins must not exceed allocated height.
```go>
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
Create prompts for sidecar workspaces. Covers prompt structure (name, ticketMode, body), template variables (ticket with fallbacks), config file locations (global vs project), and scope overrides. Use when creating or modifying prompts in sidecar config files.
>
>
Creating and using feature flags in sidecar for gating experimental functionality. Covers flag registration, checking flags in code, config file and CLI overrides, and priority resolution. Use when adding feature flags, toggling features, or gating new functionality behind flags.
>
>