vibe-prototype
Skill1 starsChanged 3 months agoMITView on GitHub
【Vibe】快速原型 — 跳过架构与 ADR,15 分钟出可跑 demo → sandbox/<name>/。当用户说「做个原型/试一版/搞个 demo」时使用。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- heartnetkung/claude-skillstheir own version, first seen Sep 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- heartnetkung/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- studio-arch-designSkill
- studio-discoverySkill
- studio-gate-checkSkill
- studio-project-scanSkill
- studio-reviewSkill
- studio-setup-stackSkill
- studio-sprint-kickoffSkill
- studio-summarize-archSkill
- usds-cost-reportSkill
- usds-debt-logSkill
- usds-micro-adrSkill
- usds-mode-switchSkill
- usds-onboardSkill
- usds-startSkill
- usds-updateSkill
- vibe-branchSkill
- vibe-checkSkill
- vibe-explain-backSkill
- vibe-graduateSkill
- vibe-startSkill
- vibe-taste-reviewSkill
The file
Files
技能:快速原型 (/vibe-prototype)
执行代理: explorer (探索者) + stylist (风格师,前端场景介入)
概述 (Summary)
跳过一切工程仪式,在 sandbox/<name>/ 下直接产出可运行的原型。
明确标注:"此代码为探索性质,可随时丢弃。"
核心 KPI: 从技能启动到用户看到能跑的东西 ≤ 15 分钟。
前置条件 (Preconditions)
docs/specs/lite-spec.md存在(若不存在,建议先跑/vibe-start)- 或用户明确表达"直接开始,我不需要 spec"
工作流 (Workflow)
- 读取意图: 加载
docs/specs/lite-spec.md(若存在) - 确认技术栈:
- 若
lite-spec已声明,直接采用 - 否则用
ask_user提供 3 个推荐组合(如:"Next.js + Tailwind"、"Python Flask + HTMX"、"纯静态 HTML+JS")
- 若
- 创建 sandbox 目录:
sandbox/<name>/ - 生成骨架:
main.<ext>或index.html入口README.md记录如何跑起来- 依赖清单(
package.json/requirements.txt)——必须锁定版本
- 实现核心流程: 只做
lite-spec中"三条必须达成"的第一条 - 验证可运行: 提供启动命令,确认能跑
- 检查点提交: 能跑起来后立即
git add sandbox/<name>/ && git commit -m "wip(sandbox/<name>): <本轮做了什么>"(遵循vibe-mode.md§7,预授权,无需逐次确认;用户明确说不要提交则跳过) - 交付: 打印启动命令给用户
允许的"违规" (遵循 vibe-mode.md)
- ✅ 硬编码配置
- ✅ 单文件塞满逻辑
- ✅ 跳过测试
- ✅ 使用 mock 数据
仍然禁止 (Hard Limits)
- ❌ 硬编码密钥
- ❌ 不锁定依赖版本
- ❌ 沉默捕获异常
成功门控 (Success Gate)
sandbox/<name>/目录创建成功README.md包含:如何启动、已知限制、下一步建议- 用户可以通过 README 中的命令实际跑起来看到东西
- 若为前端项目,Stylist 已给出基本视觉方向(配色 / 字体 / 布局)
输出约束 (Output Budget)
[强制] 完成后返回主上下文只输出:
原型已就绪。
- 位置: sandbox/[name]/
- 启动: [具体命令,一行]
- 已实现: [第一条必须达成的事]
- 下一步: 跑起来看看,然后 `/vibe-check` 校准方向协作路径
- 用户看过 demo 后 →
/vibe-check校准 - 若原型方向正确、想继续投入 → 迭代
/vibe-prototype或直接编辑 sandbox - 若原型值得晋升为正式产品 →
/vibe-graduate
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

