# Vibe Coding Template — 5-Step Prompts for Shipping

> Vibe Coding Template provides five prompts (research → PRD → tech design → agent files → build) to make AI-assisted shipping structured.

## Install

Paste the prompt below into your AI tool:

## Quick Use

1. Clone (or use as a GitHub template):
   ```bash
   git clone https://github.com/KhazP/vibe-coding-prompt-template
   cd vibe-coding-prompt-template
   ```
2. Start with Step 1 (copy-paste into your chat tool):
   ```bash
   sed -n '1,120p' part1-deepresearch.md
   ```
3. Verify:
   - Complete Steps 1–3 and save outputs as files (research + PRD + tech design) before moving to IDE execution.

## Intro

Vibe Coding Template provides five prompts (research → PRD → tech design → agent files → build) to make AI-assisted shipping structured.

- **Best for:** builders who want a repeatable prompt workflow for turning an idea into an MVP
- **Works with:** any chat LLM + an AI IDE (Cursor/VS Code/Copilot/Claude Code) for execution
- **Setup time:** 45–120 minutes

## Practical Notes

- Quant: Step 1 deep research is listed as ~20–30 minutes; treat that as a timebox.
- Quant: keep one PRD + tech design per project and measure scope creep weekly.

## Why it works

Most AI coding failures come from missing constraints. This template forces you to:
- decide what the MVP is,
- choose a stack you can ship,
- and generate the files your agent will follow (AGENTS.md + docs).

## Practical usage tip

Treat each phase output as a *handoff artifact*:
- `research-*.md`
- `PRD-*.md`
- `TechDesign-*.md`

When you switch chat sessions or models, reload only those artifacts to keep context clean and avoid hallucinated requirements.

### FAQ

**Q: Do I need to use Cursor specifically?**
A: No. Any AI IDE works; the key is keeping artifacts (PRD/design) as files.

**Q: How do I keep the build phase manageable?**
A: Break work into small passes and stop after each feature for review and tests.

**Q: What’s the minimum I should save?**
A: At least PRD + tech design. Those two prevent most scope and architecture drift.

## Source & Thanks

> Source: https://github.com/KhazP/vibe-coding-prompt-template
> License: MIT
> GitHub stars: 2,366 · forks: 299

---

<!-- ZH -->

## 快速使用

1. 克隆（或直接用 GitHub Template）：
   ```bash
   git clone https://github.com/KhazP/vibe-coding-prompt-template
   cd vibe-coding-prompt-template
   ```
2. 从第 1 步开始（复制到你的聊天工具）：
   ```bash
   sed -n '1,120p' part1-deepresearch.md
   ```
3. 验证：
   - 先完成前 3 步并把输出保存为文件（调研/PRD/技术设计），再进入 IDE 执行阶段。

## 简介

Vibe Coding Template 提供一套 5 步提示词流程：从调研到 PRD、技术设计、生成 agent 文件再到迭代开发；它把“凭感觉写 prompt”变成可复用的方法，让 AI 辅助开发更有章法。

- **适合谁：** 想把想法稳定落地成 MVP、需要可复用 prompt 流程的开发者
- **可搭配：** 任意聊天式 LLM + AI IDE（Cursor/VS Code/Copilot/Claude Code）用于执行
- **准备时间：** 45–120 分钟

## 实战建议

- 量化建议：Step 1 调研文档写明约 20–30 分钟，把它当作时间盒。
- 量化建议：每个项目保留 1 份 PRD 与技术设计，每周复盘一次范围膨胀。

## 为什么有效

很多 AI 编程翻车来自“约束缺失”。这套模板强制你：
- 说清 MVP 做什么，
- 选一个能交付的技术栈，
- 并生成 agent 真正会遵循的文件（AGENTS.md + docs）。

## 落地小技巧

把每个阶段的输出当作交接产物：
- `research-*.md`
- `PRD-*.md`
- `TechDesign-*.md`

当你切换聊天/模型时，只加载这些文件，能显著减少上下文污染与“凭空加需求”。

### FAQ

**一定要用 Cursor 吗？**
答：不一定。任何 AI IDE 都行，关键是把 PRD/设计等产物写成文件。

**如何让 build 阶段可控？**
答：拆成小步迭代；每个功能完成后停下来复查并跑测试。

**最少需要保存哪些？**
答：至少保存 PRD + 技术设计，这两份能防止大多数范围/架构漂移。

## 来源与感谢

> Source: https://github.com/KhazP/vibe-coding-prompt-template
> License: MIT
> GitHub stars: 2,366 · forks: 299


---
Source: https://tokrepo.com/en/workflows/vibe-coding-template-5-step-prompts-for-shipping
Author: Prompt Lab