Agent skill

Vibe Coding Survival

by Junliu1066 in Junliu1066/vibe-coding-kit

Vibe Coding(用 AI 写代码)开发过程中的避坑与自救——真正翻车大多发生在"开工后". An agent skill from Junliu1066/vibe-coding-kit.

MITAuto-check passedProduct & Project Management

Install Vibe Coding Survival

skills CLI
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-survival -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-survival --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vibe-coding-survival .claude/skills/vibe-coding-survival && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-coding-survival
GitHub stars
109
Token cost
~857 tokens
SKILL.md length
168 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Vibe Coding(用 AI 写代码)开发过程中的避坑与自救——真正翻车大多发生在"开工后". An agent skill from Junliu1066/vibe-coding-kit.

  • Works in 4 steps: 管理好和 AI 的对话(最易忽略,却最致命) → 守住范围(别让 demo 越长越大) → 保住能用的版本(别把唯一能跑的版本改坏) → …
  • Product & Project Management work in your project
  • SKILL.md covers 一、贯穿全程的四件事, 二、⚠ 红线:这些情况,请找真人工程师把关, 三、📄 你的项目说明书(把一切串起来) and 关键原则速查(全套件通用), plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Coding Survival is an agent skill from Junliu1066/vibe-coding-kit. Vibe Coding(用 AI 写代码)开发过程中的避坑与自救——真正翻车大多发生在"开工后"。 当用户说"AI 越改越乱"、"demo 改坏了退不回去"、"AI 老忘记之前说的"、"功能越加越多很乱"、 "AI 说做好了但其实没用",或者正在用 AI 持续开发一个项目时,主动使用此 Skill。 涵盖:管理 AI 对话(防忘事)、守住范围(防膨胀)、保住能用的版本(防丢失)、让 AI 证明给你看(防轻信), 以及哪些事必须找真人工程师的「红线」,和把一切串起来的「项目说明书」。 这是 vibe-coding-kit 套件里贯穿整个开发过程的 Skill,建议从第一行代码起就配合使用。

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management. The repository describes itself as: 不教你写代码,教你把"用 AI 写代码"彻底想明白 — 给非技术产品人的 vibe coding 规划工具包. The licence is MIT.

When your agent uses it

  • Product & Project Management work in your project

Example prompts

  • “。 当用户说”
  • “demo 改坏了退不回去”
  • “AI 老忘记之前说的”
  • “/vibe-coding-survival”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. 管理好和 AI 的对话(最易忽略,却最致命)
  2. 守住范围(别让 demo 越长越大)
  3. 保住能用的版本(别把唯一能跑的版本改坏)
  4. 让 AI 证明给你看(别轻信"我做好了")

What it can do on your machine

Read from SKILL.md and the folder at commit cb387af. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Coding Survival loads about 857 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 168 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~857

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Junliu1066/vibe-coding-kit at commit cb387af, republished under its MIT licence (© Junliu1066). 168 words, ~857 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-coding-survival/SKILL.md (or your agent's skills folder).
name
vibe-coding-survival
description
Vibe Coding(用 AI 写代码)开发过程中的避坑与自救——真正翻车大多发生在"开工后"。 当用户说"AI 越改越乱"、"demo 改坏了退不回去"、"AI 老忘记之前说的"、"功能越加越多很乱"、 "AI 说做好了但其实没用",或者正在用 AI 持续开发一个项目时,主动使用此 Skill。 涵盖:管理 AI 对话(防忘事)、守住范围(防膨胀)、保住能用的版本(防丢失)、让 AI 证明给你看(防轻信), 以及哪些事必须找真人工程师的「红线」,和把一切串起来的「项目说明书」。 这是 vibe-coding-kit 套件里贯穿整个开发过程的 Skill,建议从第一行代码起就配合使用。

开发避坑与自救:贯穿全程的纪律

这是 vibe-coding-kit 里贯穿整个开发过程的 Skill。前面几个 Skill 是"开工前想清楚",但 Vibe Coding 真正翻车,大多发生在"开工后"。下面这些不属于某个阶段,要在整个开发过程里持续做。对不写代码的人来说,这几件事比任何技术选型都重要。

配套:vibe-coding-requirements(需求)、vibe-coding-architecture(选型)、vibe-coding-production(上线)。

流程角色: 本 skill 是 harness.json 里的 always_on——不占流水线某一阶段,而是全程在跑。它和账本(docs/进度账本.md)的关系有两条:① 卡住、改坏、改不动时,把问题记进账本的「阻塞项」;② 红线(动钱 / 动别人隐私)是硬提示,一旦触及,不管在哪个阶段都要停下来提醒用户找真人把关——这条优先级高于"按门推进"。


一、贯穿全程的四件事

1. 管理好和 AI 的对话(最易忽略,却最致命)

AI 在长对话里会"忘事"——聊久了它会忘记早先的决定、自相矛盾,甚至改坏之前好的部分。对策:

  • 维护一份项目说明书(见第三节),每开一个新对话,先把它整段贴进去。
  • 一个功能做完、对话变得又长又乱时,果断开新对话,别恋战。
  • 重要决定(选了什么技术、定了什么规则)随手记进说明书,别只存在对话里——对话会丢、会乱、会被你关掉。
2. 守住范围(别让 demo 越长越大)

做着做着冒出"要不再加个……",AI 每次都说行,于是越加越多、越来越脆,最后全盘崩掉。对策:

  • 准备一个"以后再说"清单。新点子先记进去,不打断当前这件事。
  • 当前这件事彻底做好、能用了,再回头看清单,挑真正值得的做。一次只推进一件事。
3. 保住能用的版本(别把唯一能跑的版本改坏)

非技术用户最痛的事:改着改着坏了,又退不回去,之前能用的也没了。对策:

  • 每当一个版本"能正常用",就完整复制一份存好(比如把整个文件夹复制成 项目-2024-06-能用版)。
  • 之后再大胆改也不怕,坏了就从备份拿回来。
  • 懂 git 的话用 git 更专业;但对不写代码的人,"复制整个文件夹"是最朴素可靠的保险,别嫌土。
4. 让 AI 证明给你看(别轻信"我做好了")

AI 经常很自信地说"已完成",但实际没跑通——它不是骗你,是它自己也没真运行过。对策:

  • 每次它说做好了,就追问:"我怎么自己验证它真的好了?给我具体步骤。"
  • 然后你亲手按步骤跑一遍。没亲眼看到它在你这儿跑通,就别当它做完了。

二、⚠ 红线:这些情况,请找真人工程师把关

有些事,一个不写代码的人靠 AI 单干风险太高,一个 bug 就可能是真金白银或法律责任。碰到下面这些,强烈建议找一个懂行的人帮你过一遍,别全压在 AI 身上:

  • 真实收付款 / 动到钱:自己接支付、转账、扣费、管钱。出错就是真实损失。
  • 存别人的个人信息:手机号、身份证、住址、聊天记录等。这涉及隐私和法律合规,做错可能违法。
  • 出错有真实后果的场景:医疗、安全、合同、关键业务等。
  • 要给很多人用、且一旦挂掉影响很大的系统。

会判断"哪些我能自己搞定、哪些该收手找人",本身就是行家的一部分。能看懂架构(见 vibe-coding-architecture)会让这个判断更准。


三、📄 你的项目说明书(把一切串起来)

各个 Skill 的产出,汇总进一个文档,这就是你的"项目说明书"。它有两个作用:① 让你随时看得懂自己的项目;② 每开新对话先整段贴给 AI,直接解决"AI 忘事"。

完整可复制的模板见仓库 examples/项目说明书-模板.md。骨架:

【项目说明书】
· 一句话:这个项目是做什么的
· 需求基准描述:……
· 选定技术栈:…… / 为什么选它
· 目录结构:……
· 开发规范要点:……
· 安全清单:……
· 部署步骤:……
· 验收清单:……
· "以后再说"清单:……
· 当前进度 / 还剩什么没做:……
· 能用版备份在哪:……

让 AI 帮你维护它:

"每次有重要改动,提醒我该更新项目说明书的哪一部分。"


关键原则速查(全套件通用)

原则含义
需求没说清,等于没说AI 会朝着模糊的方向飞速跑偏
先说问题,再说方案描述方案会锁死 AI,描述问题才有更优解
AI 会忘事长对话里它会丢失上下文,靠项目说明书兜底
一次只推进一件事范围一散,项目就脆
先备份,再动手永远留一个能用的版本可退回
没亲眼跑通,就不算做完别轻信 AI 的"已完成"
复杂度是负债每引入一个组件,都是在向未来借债
你有权说不AI 推荐的任何东西都是可选的
没有代价的方案不存在不讲代价的推荐不可信
维护成本是最终裁决一年后修不修得动,比什么都重要
懂"为什么"才算懂用 6 维度拷问、追问取舍,把每个项目变成一次升级
动钱和动别人隐私,先找人这两条红线别独自硬上

救急话术

场景话术
AI 忘事了(开新对话)"这是我的项目说明书,请基于它继续:……"
demo 不对"我做了 X,看到的是 Y,但我期望的是 Z,怎么回事?"
报错了"这是完整报错(贴上),帮我看怎么回事,用大白话说。"
验证"我怎么自己验证它真的好了?给我具体步骤。"
改坏了(从"能用版"备份恢复,然后)"我们从这个能用的版本重新来,这次只改 X。"
记进度"每次有重要改动,提醒我该更新项目说明书的哪一部分。"

输出格式硬约束(交付前必检)

以下约束来自项目治理配置 harness.json 和 CLAUDE.md。 在声称"完成"之前,你必须逐条确认。

必须产出的内容
  • docs/项目说明书.md 中「以后再说清单」已存在(可以暂时为空,但不能缺这一节)
  • docs/项目说明书.md 中「能用版备份在哪」建议填写
  • docs/项目说明书.md 中「当前进度 / 还剩什么没做」建议填写(与 docs/进度账本.md 的当前阶段/步骤对得上)
硬性检查
  • 「以后再说清单」这一节存在(标题可见)
  • 如果开发中冒出了新点子,已记入「以后再说」而不是直接动手加功能
  • 至少做过一次"能用版"备份,且路径已记入项目说明书
自检完成声明

全部通过后声明: "✅ 硬约束自检通过:以后再说清单已建立,范围已守住,能用版备份已记录。"

© Junliu1066, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/vibe-coding-survival of Junliu1066/vibe-coding-kit.

Open the folder on GitHubat commit cb387af

Compare with similar skills

Vibe Coding Survival next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Coding Survival compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Coding Survival this skillJunliu1066/vibe-coding-kit109—~857Automated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Game Changing FeaturesopenstatusHQ/data-table-filters2.3k3 repos~2.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Convex Create Componentspokvulcan/poker-planning1148 repos~2.6kAutomated safety check: PassMIT
Self Improving Agentfarm-fe/farm5.6k2 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Game Changing Features

    openstatusHQ/data-table-filters

    Find 10x product opportunities and high-leverage improvements.

    2.3k GitHub starsUsed in 3 repos~2.1k tokens
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Convex Create Component

    spokvulcan/poker-planning

    Builds reusable Convex components with isolated tables and app-facing APIs.

    114 GitHub starsUsed in 8 repos~2.6k tokens
    Product & Project ManagementAuto-check passed
  • A universal self-improving agent that learns from ALL skill experiences.

    5.6k GitHub starsUsed in 2 repos~3.3k tokens
    Product & Project ManagementAuto-check: notes
  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from Junliu1066/vibe-coding-kit

  • Vibe Coding Harness

    Junliu1066/vibe-coding-kit

    质检 Agent:检查 vibe-coding-kit 其他 Skill 的产出物是否符合治理规范. An agent skill from Junliu1066/vibe-coding-kit.

    109 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed
  • Vibe Coding Prd

    Junliu1066/vibe-coding-kit

    一个"访谈式"的需求 Agent:通过一问一答 + 在岔路口给建议,把一个说不清需求的人,带到一份 AI 能直接照着开工的 PRD。

    109 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed
  • Vibe Coding Production

    Junliu1066/vibe-coding-kit

    把验证过的 Vibe Coding demo,做成能长期运行、给别人用的正式系统. An agent skill from Junliu1066/vibe-coding-kit.

    109 GitHub stars~993 tokensUpdated 3 mo ago
    Auto-check passed
  • Vibe Coding Requirements

    Junliu1066/vibe-coding-kit

    Vibe Coding(用 AI 写代码)项目的第一步:把模糊的想法,变成 AI 能精准落地、不会跑偏的需求. An agent skill from Junliu1066/vibe-coding-kit.

    109 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Vibe Coding Architecture

    Junliu1066/vibe-coding-kit

    教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人". An agent skill from Junliu1066/vibe-coding-kit.

    109 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Vibe Coding Survival

What does Vibe Coding Survival do?

Vibe Coding(用 AI 写代码)开发过程中的避坑与自救——真正翻车大多发生在"开工后". An agent skill from Junliu1066/vibe-coding-kit. Vibe Coding Survival is an agent skill from Junliu1066/vibe-coding-kit.

When should I use Vibe Coding Survival?

Vibe Coding Survival fits situations like: product & Project Management work in your project.

How do I install Vibe Coding Survival in Claude Code?

Run `npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-survival -a claude-code`. Or copy the skill folder (skills/vibe-coding-survival in Junliu1066/vibe-coding-kit) into .claude/skills/vibe-coding-survival in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Coding Survival in Codex?

Run `npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-survival -a codex`. Or copy the skill folder (skills/vibe-coding-survival in Junliu1066/vibe-coding-kit) into .agents/skills/vibe-coding-survival in your project. Codex loads it when a task matches its description.

Can I use Vibe Coding Survival in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-survival -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-coding-survival, .gemini/skills/vibe-coding-survival, .github/skills/vibe-coding-survival and .opencode/skills/vibe-coding-survival in your project.

What does Vibe Coding Survival need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Coding Survival is instructions for the agent only.

Does Vibe Coding Survival access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Coding Survival safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vibe Coding Survival use?

Vibe Coding Survival is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Coding Survival use?

About 857 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Coding Survival?

Skills that share tags, products or a category with Vibe Coding Survival: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Coding Survival?

Junliu1066 (a GitHub user) maintains it in Junliu1066/vibe-coding-kit, which has 109 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 30, 2026.

Source: Junliu1066/vibe-coding-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.