Kubby project reference: architecture, conventions, release workflow, and the multi-model subagent workflow for this repo. Use this WHENEVER working on the Kubby codebase — implementing a feature, fixing a bug, understanding project structure, touching the DB schema, or packaging/releasing — even if the request doesn't name "Kubby". Read it before planning any non-trivial change.
Jellyfin media server architecture reference for building self-hosted media management systems. Use when: (1) Designing or building a media library/streaming system similar to Jellyfin/Plex/Emby, (2) Implementing media transcoding pipelines, HLS streaming, or FFmpeg integration, (3) Designing plugin/extension systems, scheduled task frameworks, or event-driven architectures, (4) Building React frontends with TanStack Query, legacy migration, or multi-app architecture, (5) Designing RESTful APIs with custom authentication, WebSocket communication, or media-specific endpoints, (6) Implementing metadata scraping systems, media file naming parsers, or EF Core data models with single-table inheritance, (7) Any task involving self-hosted media server architecture decisions.