Add a new payee (merchant, person, organization, or UUID) to the correct preludes journal file, maintaining strict lexicographical order.
Note: See AGENTS.md and .agents/instructions/agent-quickstart.instructions.md for agent workflow rules and a concise checklist; use the Todo List Tool for multi-step tasks.
Note: See .agents/instructions/developer-workflows.instructions.md for canonical coding, testing, and formatting rules (type annotations, docstrings, __all__, test conventions). See AGENTS.md for agent workflow rules.
Payee directives must always be added to a preludes/ journal file, never to monthly or yearly journals. If you encounter a strict payee error (e.g., 'payee ... has not been declared'), resolve it by adding the payee to the appropriate preludes/ file as described below.
This skill describes how to add a new payee to the ledger system.
Example & guidance: See for a short example of adding a payee to . Validate with and after adding.
./examples.mdpreludes/self.journalbun run formatbun run checkDetermine the correct preludes file
preludes/ journal file, never in a monthly or yearly journal.preludes/self.journal.preludes/*.journal file.Locate the payee section
payee in the chosen preludes file.Insert the new payee
payee <payee-name-or-UUID>Validation
Note: Use the canonical formatting and validation workflow: see .agents/instructions/developer-workflows.instructions.md and .agents/instructions/common-workflows.instructions.md for steps and examples (prefer bun run format and bun run check).
preludes/ file.For consolidated lessons across all skills, see .agents/instructions/continuous-learning.instructions.md.
Key pattern: Payees must always be kept in strict lexicographical (ASCII/Unicode) order. When adding or editing, scan the entire payee section and proactively correct any out-of-order entries. This prevents merge conflicts and ensures consistency.