vibe-coding-prompt-template
Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
Runssource: GitHubhomepageTypeScriptMITcommit db481763c24e
TypeScript, MIT licensed. The project labels itself: ai agents, ai workflow, beginner friendly, chatgpt, claude code, code quality, cursor and developer tools.
vibe-coding-prompt-template runs. An Argusic agent installed it in 3.2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The vibeworkflow CLI builds from source, all 27 unit tests pass, the packaged install smoke test passes, all 13 repo validation checks pass, and the CLI correctly scaffolds skills and project files from PRD/TechDesign metadata with auto-filled values.
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.
- test failure: 'scaffold fills app name and commands deterministically' — AGENTS.md template missing [Discovery / Foundation / Core MVP / Polish / Launch] placeholder for prd.phase fill2 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 27 passed; npm run test:package printed 'Packaged CLI: clean install, full setup, preservation, and dry-run passed'; node bin/vibeworkflow.js --help printed correct usage; python3 scripts/validate.py passed 13/13 checks
- Model tokens used
- 57,534
- Exact commit tested
- db481763c24e
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
all 11 skill(s) declare 'allowed-tools'
Result: all 13 checks passed.
All clear. Let me compile the report.
**Installation**: `npm ci` + `npm run build` (tsc + template copy) succeeded with no errors.
**Test fix**: One test ("scaffold fills app name and commands deterministically") failed because th…
**Final state**: All 27 tests pass, package smoke test passes, `--help` prints correct usage, `--sk…
tokens used
57,534
All clear. Let me compile the report.
**Installation**: `npm ci` + `npm run build` (tsc + template copy) succeeded with no errors.
**Test fix**: One test ("scaffold fills app name and commands deterministically") failed because th…
**Final state**: All 27 tests pass, package smoke test passes, `--help` prints correct usage, `--sk…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 3.2 minutes, faster than the median of the 121 comparable projects Argusic has measured.
- Recovered from all 1 error 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.
- Measured 2 times, so the result is not a one-off.
Of the 122 ai-agents projects Argusic has installed and timed, vibe-coding-prompt-template was the 45th fastest to reach a running state, and 94 of 122 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3.2 minutes after the clone.
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)
ai-agentsai-workflowbeginner-friendlychatgptclaude-codecode-qualitycursordeveloper-toolsgeminillmllm-toolsmvp-developmentnodejsnpmproject-managementprompt-engineeringtechnical-designtypescriptvibe-codingworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibe-coding-prompt-template)Questions
- Does vibe-coding-prompt-template run?
- Yes. vibe-coding-prompt-template runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test vibe-coding-prompt-template?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit db481763c24e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vibe-coding-prompt-template?
- The run that produced this verdict cost $0.10: 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-prompt-template take to install?
- 3.2 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-prompt-template need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vibe-coding-prompt-template?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does vibe-coding-prompt-template compare with the alternatives?
- Of the 122 ai-agents projects Argusic has installed and timed, vibe-coding-prompt-template was the 45th fastest to reach a running state, and 94 of 122 reached one at all.
- Where is the evidence for vibe-coding-prompt-template?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.