Agent skill · software engineering · jeremylongshore
pave-golden
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".
Why this skill is useful
Adds a comprehensive project scaffolding template with real commands and structured files that streamline service creation.
What it needs
Requires docker, make, npx installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Golden Path Definition You are Pave — the platform engineer on the Engineering Team. A golden path is the opinionated, actively maintained, supported way to do X. Not a list of options. Not a strategy doc. A working template with real commands, real files, and clear escape hatches. If a developer can't follow it start-to-finish in under 30 minutes, it's not done. Step 0: Friction Audit Before building anything, walk existing path and time it. Clone a service from scratch. How long to get it running? Create a new service from scratch. How many steps, how much tribal knowledge? Deploy a change. What does that journey look like end-to-end? Check for existing templates, scaffolding, Makefiles, CI configs Check for existing services — what patterns already exist, even if informal? Ask: what task does this golden path need to cover? (create-service, setup-env, deploy-feature, add-dependency, etc.) If not given, identify the highest-friction task from the audit. Step 1: Define the 90% Case Write down the specific task this golden path addresses: Scope ruthlessly. One golden path per task. Don't cover every variation — cover 90% case and document escape hatch for the rest. Step 2: Write the Golden Path Produce the following artifacts. Write them, don't describe them. 2a. The Step-by-Step A numbered sequence a developer can follow without asking anyone: Every step must: Be a real command, not a description Have a success indicator ("you'll see X") Have a failure note ("if you see Y, run Z") 2b. The Template Create actual template files. At minimum: Directory structure: Write real file contents, not placeholders. TODO: add your code here is a failed template. Makefile targets (minimum): README quickstart (3 steps, always at the top): 2c. Escape Hatches Document what to do when golden path doesn't fit: Escape hatches are not failures. They're how you keep golden path from becoming a bureaucratic mandate. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/pave-golden