When a team has no golden path, every engineer who creates a new service makes the same decisions from scratch. Which framework, which logger, which CI tool, which deploy target, which observability stack. The decisions are independently reasonable and collectively chaotic: ten services later the team is operating ten near-identical foundations with subtle differences that do not matter individually and matter a lot in aggregate when something has to be fixed across all of them. The fix is the golden path: the opinionated, supported way to do common engineering tasks, with the template, dev setup, CI, deploy, and monitoring baked in so engineers create new services that start right and stay consistent.
Golden paths are platform engineering's most leveraged artifact. A team with a good golden path ships new services in hours rather than days, troubleshoots in one place rather than ten, and applies improvements (a new linter rule, a security patch, a logging upgrade) by updating the template once. The discipline takes upfront investment to define the path; the payback compounds with every service that uses it. The /pave-golden skill produces the golden path as the artifact rather than letting it stay in the senior engineer's head.
What a golden path requires
A golden path has five components. Project scaffold: the template that bootstraps a new service with the right structure. Local dev setup: one-command startup so an engineer can run the service in five minutes. CI pipeline: tests, linting, security scans, and the deploy gates. Deployment configuration: how this kind of service deploys, with the rollout strategy and rollback. Monitoring instrumentation: the structured logs, metrics, traces, and alerts already wired so the new service is observable on day one. Each component is documented with the reasoning so engineers know when to deviate and when to follow.
How /pave-golden works
The skill asks for the service type the path covers (REST API, worker, scheduled job, frontend) and the team's current opinions on framework, deploy target, and observability vendor. The output is the template plus the documentation. The template is in a format the team's tooling can use (Backstage software template, Cookiecutter, Yeoman, GitHub template repo). The documentation explains the path: how to use it, when to deviate, who maintains it. The combination is the artifact teams need to operate consistently as they grow.
The biggest mistake in golden path design is making it mandatory. The right framing is opinionated and supported: the path is the easiest way to do the task, but engineers can deviate when they have a real reason. Mandatory paths produce shadow paths; supported paths produce convergence over time.
Tonone's /pave-golden skill defines opinionated golden paths with template, dev setup, CI, deploy, and monitoring baked in so new services start consistently.
When to use /pave-golden
/pave-golden is the right call when a team is starting to build multiple services and consistency matters, or when an existing team has accumulated divergent service foundations and needs to converge. Skip it for one-service teams; the discipline is overhead before the second service joins.
| Capability | Tonone | Generalist chatbot | Cursor / Copilot |
|---|---|---|---|
| Template + dev setup + CI + deploy + monitoring | Yes, all five together | One layer at a time | Variable |
| Reasoning per choice | Yes, when to deviate documented | Asserted choices | Implicit |
| Format usable by team's tooling | Yes, Backstage/Cookiecutter/etc. | Generic | Variable |
| Maintenance ownership documented | Yes, who maintains it | Not in scope | Variable |
Related skills
/pave-golden defines the path. /pave-env produces local dev environments with one-command startup. /pave-catalog builds the service catalog that surfaces the paths. /pave-audit audits developer experience.
Install
/pave-golden ships with the Pave agent in Tonone for Claude Code. Install Tonone, invoke /pave-golden, and the skill produces the golden path artifact calibrated to the team's stack.
1. Add to marketplace
2. Install Pave
Frequently asked questions
- What does /pave-golden do?
- It defines a golden path for a service type with project scaffold, local dev setup, CI pipeline, deployment configuration, and monitoring instrumentation, with reasoning per choice.
- What service types does /pave-golden support?
- REST API services, background workers, scheduled jobs, and frontends. The skill produces a different golden path per service type because the right defaults differ.
- When should I use /pave-golden?
- When a team is building multiple services and consistency matters, or when an existing team needs to converge divergent foundations.
- What template format does /pave-golden produce?
- Backstage software templates, Cookiecutter, Yeoman, or GitHub template repositories. The skill detects the team's tooling and matches it.
- How do I install /pave-golden?
- Install Tonone for Claude Code via tonone.ai/get-started. /pave-golden ships with the Pave agent. Tonone is free and MIT-licensed.
- Is /pave-golden free?
- Yes. Tonone is MIT-licensed.