Platform Tools Folder May 2026

The Secret Weapon of Platform Teams: Why You Need a tools/ Folder

Every platform engineering team starts the same way. You build a beautiful internal developer portal (IDP), write some Terraform modules, and set up a few CI pipelines. But six months later, you hit the wall . platform tools folder

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. The Secret Weapon of Platform Teams: Why You

# tools/find-orphaned-volumes #!/bin/bash # Lists PVCs not attached to a running pod kubectl get pvc --all-namespaces -o json | jq -r '.items[] | select(.status.phase=="Lost") | .metadata.name' Stop asking devs to install 14 different CLIs. Here is why adding a dedicated tools/ directory

# 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.

You don’t need a new platform. You need a .

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.