Quanamo — update-docs

quanamo-update-docs keeps Quanamo documentation current with infrastructure, architecture, and feature changes.


Surfaces

LocationPurposeUpdate when...
~/Herd/docs/quanamo/Functional specsArchitecture changes, feature behaviour change
~/Herd/docs/quanamo/README.mdIndexNew docs added
~/Herd/.credentials/quanamo/servers.jsonOdin server detailsIP change, stack change, new services
~/Herd/.credentials/quanamo/api-keys.jsonAI provider keysKey rotation, new provider added
~/Herd/admin.quanamo.test/deploy.sh (script-as-doc)admin deploy contractBackup shape, supervisor program, etc. change
~/Herd/feedz.quanamo.test/deploy.shfeedz deploy contractsame
~/Herd/kanban.quanamo.test/deploy/README.mdkanban MySQL backup gate, Redis index, active.flag ruleskanban-specific deploy semantics change

App-specific operational docs (the per-app deploy/ folder) take precedence over central docs for app-specific detail. Don't duplicate that content into ~/Herd/docs/quanamo/.


Scopes

InvocationBehaviour
/do quanamo-update-docsUpdate everything relevant to recent git changes
/do quanamo-update-docs serversservers.json + Horizon config
/do quanamo-update-docs deploydeploy notes / per-app deploy.sh
/do quanamo-update-docs <feature>Matching feature folder

Global guidelines routing — mandatory

Generic guidelines (PHP / Laravel / git / tests / debugging conventions) do NOT belong in Quanamo docs. They live in ~/.claude/rules/*.md (laravel.md, ui.md, frontend.md, database.md, debugging.md, testing.md, git.md). Detect generic content BEFORE writing into Quanamo docs and route to the matching rule file.


Writing rules — enforced

  • 80-char line wrap.
  • Functional specs only. Code details BANNED — no line-by-line code, no method signatures, no variable names. If it's in the code, don't duplicate it in docs.

Hard rules

  • README first, no exceptions.
  • Update README.md if new files were created.