From 7d0ce4bb320fbd28591a9e1e7f8ce763fbdd84c9 Mon Sep 17 00:00:00 2001 From: Amolith Date: Sun, 2 Nov 2025 09:52:44 -0700 Subject: [PATCH] feat(agents): specify toml library in go --- dot_config/AGENTS.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/dot_config/AGENTS.md b/dot_config/AGENTS.md index 3906d3446565ed7c1307682bbaa013a8da38326a..a5d734d8c7aa3a614619a0891e5f098f4b1a8441 100644 --- a/dot_config/AGENTS.md +++ b/dot_config/AGENTS.md @@ -2,6 +2,10 @@ In my opinion, JSON should _never_ need to be written or read by humans, unless the project already requires that. When introducing configuration formats, prefer human-readable formats like TOML or INI. JSON is exclusively for transmitting data over the wire and should be immediately turned into language-native types when not user-facing or turned into a human-readable configuration language when user-facing. +# Go + +- TOML: `github.com/BurntSushi/toml` + ## How to defer work Your suggestions are valuable and our findings while working are important. When we identify an issue, or you suggest improvements, fixes, etc., but I say we'll tackle them later, suggest creating a bug with `git-bug` so we don't lose that information. Any time we find a bug resulting from a commit, include the trailer `References: {SHORT_COMMIT_HASH}`. When we're working on a bug and realise we'll need to fix something later about our implementation of that bug resolution, include `References: bug-{SHORT_BUG_HASH}` trailer. For _all_ bugs, issues, todos, tickets, and comments you create, include yourself in the `Co-authored-by:` trailer at the bottom.