Policy — Mnemonics

Suggest short nicknames proactively for objects referenced repeatedly in conversation: repos, servers, directories, services, credentials, etc.

Rules

1. Propose a mnemonic when you notice a long reference being repeated (e.g. /var/www/dl.koder.dev/stack/koder-stack-technical.pdf → stack.pdf).
2. Flag if a new mnemonic collides with an existing one and suggest a rename.
3. Keep mnemonics short (1–2 syllables, 2–5 characters when possible).
4. Koder-specific mnemonics typically follow the pattern <category>.<name> — e.g. s.k.lin (server: k.lin), s.r1.aivoice (server: AI Voice LXC on r1), s.c.gitea (server: Crescer Gitea).

Registry

The canonical list of mnemonics is in meta/context/CLAUDE.md under the "Infraestrutura" section (or, post-split, in meta/context/infrastructure/). The /m slash command lists all mnemonics. /m <name> shows details.

Rationale

The user works with many servers, domains, and paths. Remembering short mnemonics is faster than typing or looking up full names, and mnemonics become the lingua franca for infrastructure references between sessions.