feat(cli-tooling): add generic CLI, tooling and script-placement rules

Extracted from the per-agent profile files and the private ai-agents skill,
where they were duplicated and environment-coupled:

- discovery over guessing: walk the help tree, never invent flags, never
  hand-roll a script when a dedicated CLI exists
- non-interactive invocation: explicit targets, the tool's own --wait
- machine-readable output flags (json/compact/csv) vs. never filtering
  diagnostics
- orient before starting: project instructions, git log, prior work records,
  and verifying TODOs against the code
- script placement: dedicated version-controlled dir, symlinked into PATH
- destructive/outward-facing command care; environment drift verification

coding-dev.md and code-languages/bash.md now cross-reference it instead of
carrying their own one-line versions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

coding-dev.md

@@ -294,8 +294,12 @@ Run the **whole** gate, not the convenient part of it. A typical full gate:
 
 ## 13. Environment & Tooling
 
+Full version in [`cli-tooling.md`](./cli-tooling.md); the essentials:
+
 - **Read `<tool> --help` before using a CLI.** Do not guess flags, and do not write an ad-hoc
   script when an existing tool already does the job.
+- **Standalone scripts live in a dedicated, version-controlled scripts directory**, symlinked
+  into `PATH` — never written directly into `~/.local/bin` or another `PATH` directory.
 - **Build inside the project's designated environment** (container, venv, toolchain manager)
   rather than the host, when the project specifies one. Note that entering a container
   typically resets the working directory — chain `cd` inside the same command string.