From 4d0251281268626f5b7c672126bb07ea6de50361 Mon Sep 17 00:00:00 2001
From: Amolith <amolith@secluded.site>
Date: Wed, 10 Jun 2026 12:33:39 -0600
Subject: [PATCH] go-opinions: document CLI config precedence

---
 skills/amoliths-go-opinions/references/cli.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/skills/amoliths-go-opinions/references/cli.md b/skills/amoliths-go-opinions/references/cli.md
index e0fb03fc07e0b46af88ea428a411e2c4f1ba733d..2bc8059708b8acd42a8d0e60c8fbad0513c6e1bb 100644
--- a/skills/amoliths-go-opinions/references/cli.md
+++ b/skills/amoliths-go-opinions/references/cli.md
@@ -83,8 +83,12 @@ keep the same versioning pattern but remove the static-only flags.
 ## Config
 
 - TOML config: `BurntSushi/toml`.
+- Default config file: read from `$XDG_CONFIG_HOME/<app-name>/config.toml`,
+  falling back to `~/.config/<app-name>/config.toml` when `XDG_CONFIG_HOME` is
+  unset.
 - Env vars: read at the boundary, validate early, and store in a typed config
   struct.
+- Config precedence is flag, then environment variable, then config file.
 - Config discovery should be explicit and documented; avoid magical precedence
   unless the project truly needs layering.