seed-golden-journey
Use when an app needs a keystone acceptance test that proves the real product actually works end to end, not just that units pass or coverage is high. Scaffolds a HELD-OUT golden-journey test that launches the REAL app, drives the ONE primary user journey, and asserts a REAL artifact on disk (a valid media file via ffprobe, a downloaded file, a screenshot) rather than element-present. Parameterized for Electron (playwright electron launch), web (Playwright page goto), and CLI (spawn plus assert output file), with an annotated fill-in-the-blanks template derived from the Reframe exemplar. Makes the journey the merge gate and forbids citing coverage as done. NOT for broad unit/integration coverage (see two-tier-verify); NOT for mocked component tests.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- seed-golden-journey
- description
- Use when an app needs a keystone acceptance test that proves the real product actually works end to end, not just that units pass or coverage is high. Scaffolds a HELD-OUT golden-journey test that launches the REAL app, drives the ONE primary user journey, and asserts a REAL artifact on disk (a valid media file via ffprobe, a downloaded file, a screenshot) rather than element-present. Parameterized for Electron (playwright electron launch), web (Playwright page goto), and CLI (spawn plus assert output file), with an annotated fill-in-the-blanks template derived from the Reframe exemplar. Makes the journey the merge gate and forbids citing coverage as done. NOT for broad unit/integration coverage (see two-tier-verify); NOT for mocked component tests.
03 SKILL.md 正文
seed-golden-journey
Coverage and "unit-green" are a proxy the implementer controls, so a capable agent optimizes that proxy and stops — while the real A→B→C user journey stays broken. Live proof: Reframe shipped v1.4 with 100% coverage and green units, and "Make Shorts" never produced a file on Windows. Three real Windows-only bugs sat exactly at the seams the unit tests mock and Linux CI can't reach. The one signal that caught them was a held-out golden-journey that drove the real app and asserted a real vertical short on disk.
This skill scaffolds that keystone: the single external done-signal the implementer can't author or fake. It is the highest-leverage thing a user provides — no hook substitutes for it.
The five rules of a golden journey
- Pick the ONE money journey. The single flow that is the product's reason to exist — the thing that, if it silently broke, the product is worthless regardless of coverage. Reframe: "Make Shorts produces a real vertical short file on disk." One journey, not a matrix.
- Drive the REAL app — nothing stubbed. Launch the actual built binary/app; drive the real UI; let it hit the real backend/sidecar, real ffmpeg, real filesystem. The bugs live precisely at the seams unit tests mock; a mocked journey re-hides them.
- Assert a REAL produced artifact, not element-present. "Button rendered" / "toast appeared" is theater. The pass condition is the thing the user came for existing and being valid on
The assertion ladder (climb every rung — stopping early is theater)
Wiring the async completion (background jobs)
Stack recipes — the LAUNCH is the only part that changes
Make it the gate + forbid the reward-hack surface
Anti-patterns
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files