discord-manager: Instructions file for Claude Code

Discord Manager

Self-hosted Discord bookmarks, catch-up digests, and triage for your AI assistant, over MCP — no Nitro required. The product is headless: a discord.js bot ingests one guild's messages into a local append-only SQLite event store, and an MCP stdio server is the entire user surface. Every deployment is single-owner — one bot token, one owner user id, one guild, one database file. docs/architecture.md is the reference for the whole design.

The append-only doctrine

The application schema is 100% append-only and event-sourced, with zero exceptions: INSERT is the only write, current state is derived from events at query time, and deletion/archival/correction are events too. ALWAYS load the database-design skill before designing tables, writing migrations, or writing any query that changes data. The kysely skill covers the query-side rules (updateTable/deleteFrom/doUpdateSet are banned on application tables).

SQLite forces exactly five sanctioned divergences, and no others:

• Ids are monotonic UUIDv7 values from newId() in application code — there is no gen_random_uuid(), and a random id would turn the latest-event-wins id desc tie-break into a coin flip whenever two events share a millisecond. Insert helpers own this; migrations declare text primary keys. The guarantee is per process: the daemon and the MCP server each issue ids in their own order, so two processes writing to one reversible pair in the same millisecond stay unordered. That is accepted — see single-writer WAL below — and no ordering machinery exists to fix it.
• Timestamps are ISO-8601 UTC text columns; createdAt defaults to strftime('%Y-%m-%dT%H:%M:%fZ','now'), so lexicographic order equals chronological order.
• Latest-event-wins uses row_number() over (partition by parentId order by createdAt desc, id desc) filtered to 1 instead of distinct on. The id desc tie-break stays mandatory.
• Booleans are integer 0/1 at the schema level; Zod coerces at the boundary.
• Single-writer WAL replaces Postgres advisory locks: the ingest daemon is the only gateway writer and MCP writes are transactional, so there is no cross-process ordering machinery.