Vibe_coding_guide
中文优先的 Vibe Coding / AI coding engineering workflow guide: specs, agents, worktrees, skills, CI, and review.
Runssource: GitHubhomepageJavaScriptMITcommit 5fea8fc17f20
JavaScript, MIT licensed. The project labels itself: agent workflows, agentic engineering, ai agents, ai assisted development, ai coding, bilingual, codex and coding agents.
Vibe_coding_guide runs. An Argusic agent installed it in 35 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The static tutorial site installs with zero dependencies, serves HTTP 200 on python3 -m http.server 4173, and works in real headless Chrome: schedule/day navigation, checklist progress persisted in localStorage, and reader mode rendering the markdown course; its only 404 is the optional favicon.ico.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- puppeteer browser download failed: no zip archiver available (system lacks unzip)8 minutes
- pip install blocked by PEP 668 externally-managed environment4 minutes
- Chrome launch crash: chrome_crashpad_handler Permission denied3 minutes
- background http.server died between exec invocations2 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- puppeteer headless Chrome: goto http://127.0.0.1:4173/ loaded with title 'Vibe Coding Guide | AI Coding 工程工作流手册', zero page/console errors; day-2 click switched day; checklist checkbox toggled and persisted in localStorage after reload; reader mode rendered the markdown guide (131 headings, 'Chapter 01 What Is Vibe Coding?' visible)
- Model tokens used
- 238,537
- Exact commit tested
- 5fea8fc17f20
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Real behavior verified in headless Chrome (tier1):**
- Page loads, title = "Vibe Coding Guide | AI Coding 工程工作流手册", H1 = "Day 1: Learn Chapter 1", body …
- No page errors (zero `pageerror`/console errors)
- Day 2 navigation works (`SHOWS_DAY2=true`)
- Checklist checkbox toggles `false → true`, persists in `localStorage` after reload (`PERSISTS_AFT…
- Reader mode renders the markdown course content (131 headings, `Chapter 01 What Is Vibe Coding?` …
**PDFs (decoded, not just header):** `pypdf` parsed both; zh 96 pages, en 88 pages, first/last page…
**Errors encountered (all fixed):**
1. `pip install` blocked by PEP 668 (externally-managed env) → worked around with a local venv
2. Puppeteer browser download failed ("no zip archiver is available") because container lacks `unzi…
3. Chrome crash on launch ("`chrome_crashpad_handler: Permission denied`") → zipfile didn't preserv…
4. Mid-session http server died between exec calls (process-group reaping) → restarted server befor…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 35 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-workflowsagentic-engineeringai-agentsai-assisted-developmentai-codingbilingualcodexcoding-agentsdeveloper-productivitydeveloper-toolsdocumentationengineering-workflowenglish-chinesegit-worktreesmulti-agentprompt-engineeringsoftware-engineeringtutorialvibe-codingworktree
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibe-coding-guide)Questions
- Does Vibe_coding_guide run?
- Yes. Vibe_coding_guide runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Vibe_coding_guide?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5fea8fc17f20. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Vibe_coding_guide?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Vibe_coding_guide take to install?
- 35 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Vibe_coding_guide need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Vibe_coding_guide?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Vibe_coding_guide?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.