Summarize what the current branch changes versus origin/main (committed + uncommitted) and flag cross-package contract risks specific to this monorepo. Use when the user asks "what's different from main", "what would this PR contain", "diff against main", "review my branch", or anything similar before opening or refining a PR.
Create or modify a Luminary ticket — a GitHub issue in bccsa/luminary on the Luminary Development project board with Status (column), Priority, Size, and Complexity set. Use when the user says "log a ticket", "create a bug ticket", "file an issue", "add a ticket to the board", "make a P2 for…", or wants to change an existing ticket ("move issue X to In progress", "bump
Rebuild luminary-shared's dist so app/cms TypeScript picks up shared TYPE/signature changes. Runtime/behavioural changes need no rebuild (Vite consumes shared/src directly via HMR). Use when the user edited shared/ and a consumer's type-check/editor reports stale shared types, or asks "rebuild shared", "after changing shared what do I do", or similar.
Investigation playbook for why a document isn't syncing to a client (app or CMS) as expected. Walks the full sync path — syncList registration, permissions, connectivity, design docs, socket rooms, bulkPut filters. Use when the user reports "doc X isn't showing up", "sync seems stuck", "I edited X in the CMS but the app doesn't see it", or similar.
Walk through adding a new Mango sync query end-to-end — the design doc (CouchDB index), the consumer's syncList registration, and the watcher in app/src/sync.ts or cms/src/sync.ts. Use when the user wants to "sync a new doc type", "add a Mango sync query", "register X in syncList", or hits a "sync query rejected" / "Unknown index" error.
Mirror DTO field changes between api/src/dto/*.ts (class-based, decorator-validated) and shared/src/types/dto.ts (plain TypeScript types). Use when the user adds, renames, or removes a field on a document DTO on one side, or asks "keep DTOs in sync", "mirror DTO change", "I added X to ContentDto", or similar.
Generate a new database schema upgrade (vN.ts) — file boilerplate, wiring into db.upgrade.ts chain, README update, and seeding-doc sync. Use when the user asks to "add a schema upgrade", "bump the schema version", "migrate existing docs for X", or has changed a doc shape that needs backfilling on existing databases.
Trace why a user can or cannot perform a given action on a given doc type — walking through their group membership, the ACL entries on those groups, the resulting AccessMap, and the verifyAccess decision. Use when the user asks "why can/can't user X do Y to a Z", "permission seems wrong", "ACL not taking effect", "explain access for…", or similar.