Platform Tools Folder 99%

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.

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

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

make db-failover Instead of: Finding the wiki, clicking three links, copying a broken command, and crying. My team used to spend 2 hours every Monday morning cleaning up stale environments. One person ran kubectl get ns , another ran a Python script locally, and a third manually deleted ECR images.

# Platform Makefile .PHONY: tools/% tools/%: @echo "🔧 Running platform tool: $ " @./tools/$ clean-volumes: tools/clean-orphaned-volumes db-failover: tools/db-failover Here is why adding a dedicated tools/ directory

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

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. When the database is down, you don't want

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 .