audiobook-boss

Canonical metadata strategy for Audiobook Boss. Use when changing tag mappings, metadata intent behavior, or ABS/Plex/Apple interoperability rules.

Pick the next Audiobook Boss flow when the user asks which step to use. Use for smell-to-ship routing in audiobook-boss only.

Resolve ABB external-library/API uncertainty for Effect, Svelte, Tauri, Specta, or tauri-specta when implementation, IPC contract, codegen, installed-version, or upstream-source behavior affects the work. Use route cards, Context7, lockfiles, and repos/* for the active question only.

Audit and fix Audiobook Boss resource-lifetime foot-guns with high bug potential. Use when the user asks to hunt for lifecycle bugs, file-handle contention, Windows/cross-platform file behavior, temp-file cleanup, process lifetime, FFmpeg/mp4ameta reopen issues, rename/replace semantics, or "similar in-kind" high-ROI issues.

ABB repo-grounded alignment when substantial work needs a locked decision or GitHub issue capture. Inspect repo truth first; at most two action-changing questions. Default capture is GitHub issues.

Audiobook Boss release workflow for deciding whether changes need a formal version/changelog release, preparing release metadata, validating the local app or DMG artifact, tagging, and publishing manually. Use when the user mentions release, version bump, changelog, tag, GitHub Release, DMG, publish, ship, release notes, or asks whether a change should be released.