Here is why adding a dedicated tools/ directory to your platform repository is the highest leverage, lowest effort change you can make this quarter. It is not a dumping ground. It is a curated, version-controlled, executable collection of scripts, binaries, and utilities designed to operate your platform.

Now, even the most stressed engineer during an incident can run:

You have three different scripts to clean up AWS resources. Your on-call engineer is running a Python snippet from a forgotten Gist. And your "golden path" documentation is already two major versions behind the actual CLI tooling.

# tools/bootstrap-dev #!/bin/bash # Installs the exact versions of Terragrunt, Helm, and Node used in production ./tools/install-tfenv && tfenv install ./tools/install-helm-3.14 A tools/ folder is useless if nobody knows how to invoke it. Add a Makefile at your repo root to act as the catalog.

# Platform Makefile .PHONY: tools/% tools/%: @echo "🔧 Running platform tool: $ " @./tools/$ clean-volumes: tools/clean-orphaned-volumes db-failover: tools/db-failover

What is the most useful script in your team's tools/ folder? Let me know in the comments below.

When the database is down, you don't want to Google kubectl commands.