ersatztv-programmer

Build or rebuild an ErsatzTV Next channel. Args optional — pass a channel number to refresh just that one, or omit to start a free-form build conversation. User-invocable only — programming writes playout JSON files, so the user controls when it runs.

Specialized scheduling subagent for ErsatzTV Next channels. Use when programming three or more channels in one request, when a "channel pack" or "package of channels" is requested, when running the daily refresh routine, or when the main session would otherwise fill with media-library query results. Has its own context window so library queries don't pollute the parent session.

Procedures for programming an ErsatzTV Next channel — building, validating, and writing playout JSON files from a media library. Loads when the user asks to plan, schedule, build, modify, or rebuild a channel; or when "playout JSON," "marathon," "channel programming," or similar phrases appear.

First-run wizard for the ersatztv-programmer plugin. Captures the user's media server connection, ErsatzTV Next paths, and channel preferences, then optionally registers a daily refresh routine. User-invocable only — run /setup explicitly when you want to configure or reconfigure.

Audit an existing ErsatzTV Legacy install against a Next-based setup and report gaps. Loads when the user runs /audit, asks to "migrate from Legacy," asks "what channels do I already have?" or wants a one-time inventory before pivoting to Next. Read-only — never modifies either install.

Senior-engineer mental model for the ErsatzTV ecosystem. Project history, repository layout, where things live on disk, common debugging paths, upstream entry points, key concepts. Loads when the user asks "where does X live," "why is Y not working," "what's the difference between Legacy and Next," or otherwise needs deep ErsatzTV context the schedule/reference skills don't cover.

Pinned schema reference for ErsatzTV Next playout.json, channel.json, and lineup.json. Loads when the schedule skill needs exact field shapes, when a validation error mentions a specific field, or when the user asks "what fields does X support?"

1 hook across 1 event