金路指引

本条目介绍 金路指引 的公开用途。DeepSkill 当前公开目录说明:“定义一条黄金路径——即针对常见开发任务(如创建新服务、搭建环境、部署功能)所推荐的、经过验证的标准做法。提供具体的步骤、模板和工具支持。当被问及“黄金路径”、“创建项目模板”、“为新服务搭建脚手架”、“我们应如何创建服务”或“标准化我们的设置”时,使用此方案。” 适用场景包括部署发布与上云、系统管理。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "pave-golden":https://skillpi.com/zh/skills/deepskill-719589b1b0d9ba0be7a6207bae0c7edccb139844faf0533a52cc6a86fbea57b6。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-golden/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-golden --skill pave-golden
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目介绍 金路指引 的公开用途。DeepSkill 当前公开目录说明:“定义一条黄金路径——即针对常见开发任务(如创建新服务、搭建环境、部署功能)所推荐的、经过验证的标准做法。提供具体的步骤、模板和工具支持。当被问及“黄金路径”、“创建项目模板”、“为新服务搭建脚手架”、“我们应如何创建服务”或“标准化我们的设置”时,使用此方案。” 适用场景包括部署发布与上云、系统管理。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: pave-golden
description: 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".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

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

```
Task: [e.g., "Create a new backend API service"]
Stack: [e.g., "Python/FastAPI, PostgreSQL, deployed to Fly.io"]
Who does this: [e.g., "Any engineer, ~2x/quarter"]
Current pain: [e.g., "No template — each service is structured differently, setup takes 2 hours"]
```

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:

```
1. Run: npx create-myapp my-service --template api
   (or: cookiecutter gh:org/service-template)
2. cd my-service && make setup
3. make dev  →  app running at http://localhost:8000
4. make test →  test suite passes
5. git push  →  CI runs, preview deploy created
6. make deploy →  ships to production
```

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:**

```
my-service/
├── Makefile          # setup, dev, test, deploy targets
├── README.md         # 3-step quickstart at the top
├── .env.example      # every variable, with description and example value
├── docker-compose.yml # local dependencies (db, cache, etc.)
├── src/              # application code with a working hello-world
├── tests/            # test setup with one passing example test
└── .github/
    └── workflows/
        └── ci.yml    # lint → test → build → (deploy if main)
```

Write real file contents, not placeholders. `TODO: add your code here` is a failed template.

**Makefile targets (minimum):**

```makefile
setup:   ## Install deps, create db, seed data, copy .env.example → .env
dev:     ## Start app + all dependencies
test:    ## Run test suite
lint:    ## Run linter + formatter check
deploy:  ## Deploy to production (requires ENV=prod or similar)
clean:   ## Tear down local environment
```

**README quickstart (3 steps, always at the top):**

```markdown
## Quickstart

1. `make setup`
2. `make dev` → http://localhost:8000
3. `make test`
```

### 2c. Escape Hatches

Document what to do when golden path doesn't fit:

```markdown
## When to go off-path

- Different language/runtime: [link to polyglot guide or process]
- Need a different database: change DB_URL in .env and docker-compose.yml
- Deploying somewhere else: swap the deploy target in Makefile, CI config stays the same
- Monorepo vs polyrepo: [describe the adjustment]
```

Escape hatches are not failures. They're how you keep golden path from becoming a bureaucratic mandate.

## Step 3: Validate It

Golden path is not done until someone has followed it cold:

- [ ] Clone template into a clean directory
- [ ] Run `make setup` — does it succeed without error?
- [ ] Run `make dev` — does the app start?
- [ ] Run `make test` — do tests pass?
- [ ] Push to a branch — does CI run and pass?
- [ ] Onboard a developer who didn't build it — what did they get stuck on?

Fix every point of friction before publishing.

## Step 4: Publish and Measure

**Publish:**

- Link template from team wiki / README
- Add `make new-service` target that runs scaffolding command
- Announce with a 2-sentence summary: what it does, how to use it

**Measure (30/60/90 days):**

- How many new services created using template vs off-path?
- Did onboarding time change? (baseline it now if you haven't)
- What escape hatches are being used most? (signals for next iteration)

A golden path with no adoption data is a guess. A golden path with low adoption is a design bug, not a developer attitude problem.

## Output Format

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Summarize:

- What task the golden path covers
- What files were created or modified
- How to use it (the 3-step quickstart)
- What to measure over next 30 days

## Key Rules

- Write template, don't describe it — real files, real commands
- One command to set up, one command to run — or path has failed
- No TODO placeholders — they're a broken window that discourages use
- Match existing tooling — don't introduce new tools without clear reason
- Opinionated, not mandatory — always document escape hatch
- Measure adoption — if developers aren't using it, fix path, not developers

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

提供标准化项目脚手架和最佳实践路径

触发精准90/100
评分依据

触发词覆盖完整且边界清晰

结构规范85/100
评分依据

Phase/步骤清晰完整

执行可靠90/100
评分依据

工具来源明确且为标准开发工具

证据可验 (前四项均值)88/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

  • 安装或获取外部依赖

    使用官方来源并锁定版本,在隔离环境检查安装脚本。当前文档检查不覆盖后续下载的代码。

    主文档提及 · 第 50 行
文档引用的域名或地址

这些地址可能用于文档链接或示例,不是已批准的联网清单。使用前核对实际目的地及发送的数据。

  • localhost

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。