Golden Paths

A golden path is a single, curated, well-supported way to do something common — start a new service, add a queue, wire up a database — that comes with security, observability, and reliability built in by default. It's not a rule enforced by review; it's the option that requires the least effort, so following it is what happens by default rather than what has to be argued for.

Deviation from the golden path should always remain possible, but it should be a deliberate, visible choice — never an accident born of the path being harder to find than the workaround. The golden path wins by being the least amount of work, not by being the only option allowed.

1. Bundle the boring-but-critical defaults in, not bolted on after

Structured logging, tracing instrumentation, health checks, and a baseline auth setup are exactly the things teams skip under deadline pressure if they're left as separate steps. A golden-path template that generates a service with these already wired in means "secure and observable" is the starting state, not a backlog item someone has to remember to schedule. See observability and kubernetes-security for what belongs in the defaults themselves — this skill is about making sure they ship pre-wired, not about their individual configuration.