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.
教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人". An agent skill from Junliu1066/vibe-coding-kit.
Install Vibe Coding Architecture
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-architecture .claude/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.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/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .claude/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vibe-coding-architecture .agents/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .agents/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vibe-coding-architecture .cursor/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .cursor/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Junliu1066/vibe-coding-kit.git --path skills/vibe-coding-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vibe-coding-architecture .gemini/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .gemini/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vibe-coding-architecture .github/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .github/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Junliu1066/vibe-coding-kit vibe-coding-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Junliu1066/vibe-coding-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vibe-coding-architecture .opencode/skills/vibe-coding-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-coding-architecture" agent skill from https://github.com/Junliu1066/vibe-coding-kit/tree/main/skills/vibe-coding-architecture into .opencode/skills/vibe-coding-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-coding-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-coding-architecture- GitHub stars
- 109
- Token cost
- ~1.2k tokens
- SKILL.md length
- 299 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人". An agent skill from Junliu1066/vibe-coding-kit.
- Works in 3 steps: 读 docs/进度账本.md。 确认 S1 需求对齐的出口门已过（prd.md… → 向用户报一句："需求已就绪，进入 S2 架构选型。" → 本阶段三步对应账本：S2.1 六维度拷问 → S2.2 五步选型 → S2.3…
- Product & Project Management work in your project
- SKILL.md covers 给使用者的话, 准入检查（开始本阶段前必做）, 一、架构素养速成：看懂任何方案的 6 个维度 ★（对应… and 二、把 AI 当老师：边做边学, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe Coding Architecture is an agent skill from Junliu1066/vibe-coding-kit. 教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人"。 当用户问"该用什么技术/框架"、"帮我选技术栈"、"AI 给的方案我看不懂"、"这几个方案怎么选"， 或者需要把 demo 做成更正经的东西、要理解 AI 提出的架构时，使用此 Skill。 这是 vibe-coding-kit 套件里负责"成长"的核心 Skill：用 6 个大白话维度拷问任何方案，再配五步决策法做选择。 即使用户没明说"架构"二字，只要 ta 面对多个技术方案不知道怎么选、或看不懂 AI 的技术建议，就应主动用本 Skill。
Its SKILL.md is about 1.2k 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
- “只会照搬话术的小白”
- “能看穿方案好坏的人”
- “该用什么技术/框架”
- “/vibe-coding-architecture”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- 读 docs/进度账本.md。 确认 S1 需求对齐的出口门已过（prd.md / 需求基准描述齐了）。没过就别开始选型——需求没定，方案必然脱离现实；先回 vibe-coding-prd 或 vibe-coding-requirements 补完 S1。
- 向用户报一句："需求已就绪，进入 S2 架构选型。"
- 本阶段三步对应账本：S2.1 六维度拷问 → S2.2 五步选型 → S2.3 项目结构（可选）。每过一步回写账本。
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 Architecture loads about 1.2k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 299 words of instructions outside code blocks.
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). 299 words, ~1,177 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-coding-architecture/SKILL.md (or your agent's skills folder).- name
- vibe-coding-architecture
- description
- 教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人"。 当用户问"该用什么技术/框架"、"帮我选技术栈"、"AI 给的方案我看不懂"、"这几个方案怎么选"， 或者需要把 demo 做成更正经的东西、要理解 AI 提出的架构时，使用此 Skill。 这是 vibe-coding-kit 套件里负责"成长"的核心 Skill：用 6 个大白话维度拷问任何方案，再配五步决策法做选择。 即使用户没明说"架构"二字，只要 ta 面对多个技术方案不知道怎么选、或看不懂 AI 的技术建议，就应主动用本 Skill。
架构选型：从看不懂，到自己会判断
这是 vibe-coding-kit 里负责"让你成长"的 Skill。目标不是教你写代码，而是给你一套看懂任何技术方案、拷问任何选型的框架。用得越多，你越不需要照搬话术——因为你已经懂了。
前一步是
vibe-coding-requirements（把需求说清）。选完技术后，去vibe-coding-production处理上线。开发全程配合vibe-coding-survival避坑。
给使用者的话
技术上的事，你不需要会写，但要逐步学会看懂和判断。一开始你靠下面的话术问 AI，几个项目之后，你会发现自己已经能直接看穿方案好坏——那就是这个 Skill 想把你带到的地方。
准入检查（开始本阶段前必做）
本 skill 是流程第二阶段 S2·架构选型。开始前：
- 读
docs/进度账本.md。 确认 S1 需求对齐的出口门已过（prd.md / 需求基准描述齐了）。没过就别开始选型——需求没定，方案必然脱离现实；先回vibe-coding-prd或vibe-coding-requirements补完 S1。 - 向用户报一句："需求已就绪，进入 S2 架构选型。"
- 本阶段三步对应账本：S2.1 六维度拷问 → S2.2 五步选型 → S2.3 项目结构（
可选）。每过一步回写账本。
一、架构素养速成：看懂任何方案的 6 个维度 ★（对应 S2.1）
所谓"看懂架构"，本质上就是看懂下面这 6 个维度。 AI 给你的任何方案，都可以拿这 6 条逐条拷问——拷问得多了，你就成行家了。
| 维度 | 大白话是什么 | 它决定你该问什么 |
|---|---|---|
| 1. 数据存哪、留不留得住 | 数据是写进硬盘/数据库（关机还在），还是只在内存里（关机就没）？ | "关机重开后数据还在吗？存在哪？" 这是 demo 和正式系统最大的分水岭。 |
| 2. 在谁的机器上跑 | 跑在你自己电脑上，还是一台一直开着的服务器上？要联网才能用，还是离线也行？ | "这东西要一直开机才能用吗？谁来开着它？没网能用吗？" |
| 3. 一坨还是拆开 | 整个程序是一个进程（单体），还是拆成好几个服务各跑各的（拆分/微服务）？ | "能不能一个进程就跑起来？" 对个人维护者，一坨通常远好过拆开——拆开是给大团队准备的负债。 |
| 4. 依赖了多少外部东西 | 这方案站在多少"别人造的东西"上：第三方库、外部 API、云服务？ | "它依赖哪些外部东西？哪个挂了我就跟着挂？少装点行不行？" 每个依赖都是未来可能坏掉、可能收费的点。 |
| 5. 即时还是排队 | 用户一点就要马上出结果（同步），还是可以先收下、后台慢慢处理（异步/队列）？ | "如果某一步很慢，会不会卡住整个系统？慢操作能不能放后台？" 简单场景别提前上队列。 |
| 6. 多少人用才扛不住 | 现在的方案，1 个人用没问题，那 100 个、10000 个同时用呢？ | "大概多少人同时用会扛不住？" 但新手最常见的错是过度担心这个——先按真实人数设计，扛不住了再升级，别为想象中的百万用户提前把方案搞复杂。 |
怎么用： 让 AI 列方案后，对每个方案用这 6 个维度问一遍，尤其第 1、3、4 条——这是个人项目最容易出事的地方。能把这 6 条问顺，你就有了基本的架构判断力。
隐藏好处：看懂架构，你能更准地判断"这件事我到底能不能自己搞定"——包括什么时候该收手找真人工程师（见
vibe-coding-survival的「红线」）。会判断边界，也是行家的一部分。
二、把 AI 当老师：边做边学
你身边坐着一个不嫌烦、随叫随到的技术老师。别只让它干活，要让它教你。每个项目都这么做，几个项目下来你就脱胎换骨：
- 要大白话解释："用一个生活里的例子解释这个方案，假设我完全不懂技术。"
- 逼它讲取舍："为什么选这个方案，不选另一个？它好在哪、差在哪？"——行家和小白的区别，就在于懂不懂"为什么"。
- 攒自己的词汇表： 遇到不懂的词，让 AI 一句话解释，记进项目说明书。同一个词见三次，你就记住了。
- 项目结束做复盘："把这个项目我们做的架构决定和原因列一遍，我想记住这套思路，下次自己也能判断。"
三、技术选型五步决策法（对应 S2.2）
▸ 过门：列方案 → 砍方案 → 选定一个，且每步都有理由 → 账本 S2.2 标 ✅。这是 S2 的核心步骤，不能省。
先查推荐库再开列方案。 产品形态（prd S1.3）定了之后，先翻
references/技术栈推荐库.md，按平台（网站 / 小程序 / 移动端 / 后端接口）取那个 ★ 默认成熟栈作为起点——它已经替你挑出"最成熟、AI 写得最好、最好维护"的方案。再用下面五步法拿现有资源清单去对照、砍掉、最终选定。不要凭空让 AI 从零列方案——那容易跑偏成它训练里最常见的重栈。
目标： 从多个可行方案里，选出最适合你约束的那个。结合上面的 6 维度，你不只是逼 AI 摊开"代价"，更是在练自己的判断力。
第一步 · 列菜单
"列出 3–5 种可行方案，每种用一句话说明核心思路，先不要展开细节。"
第二步 · 曝代价
"对每个方案，告诉我：① 最适合什么场景 ② 最不适合什么场景 ③ 最大的隐性代价（部署多复杂、维护要花多少精力、我学起来难不难、出问题好不好查）。"
第三步 · 约束过滤——用你的真实约束逐条砍：
| 约束维度 | 砍掉什么 |
|---|---|
| 服务器配置 | 需要多进程、吃内存的方案 |
| 维护人力 | 需要专人盯着运维的方案 |
| 技术能力 | 你完全看不懂、出事全靠运气的方案 |
| 长期稳定性 | 依赖一长串第三方、哪个挂了都跟着挂的方案 |
第四步 · AI 协作评估（Vibe Coding 专属，最容易被忽略）：
| 评估项 | 问你自己 |
|---|---|
| AI 生成质量 | AI 用这技术写代码，一次跑通的概率高吗？ |
| 可读性 | 代码摆在你面前，你能大致看懂它在干嘛吗？ |
| 错误可描述性 | 出 bug 了，你能把错误信息完整复制给 AI 吗？ |
| 社区资料量 | 中文教程、网上现成答案多吗？ |
第五步 · 维护成本裁决
终极问题："一年后这系统出 bug，我还能不能自己（靠 AI）修好？" 修不动的方案，再先进也是坑。
输出物： 选定的技术栈 + 每个被否决方案的否决理由（写下来，防止过两周自己又动摇）。存进项目说明书。
核心原则： 复杂度是负债不是资产；你有权对 AI 的方案说不；从最简单的开始，不够用了再升级；依赖越少，维护越轻松。
四、项目结构设计（对应 S2.3 ·可选）
▸ 过门：画出目录结构、每个目录一句话职责 → 账本 S2.3 标 ✅；只跑 demo、结构显而易见时可跳并留痕。
目标： 让 AI 给出清晰的目录结构，确保你知道每个文件大概干什么。
"请给出这个项目的目录结构，每个目录/文件用一句话说明职责。遵循单一职责原则——每个目录只做一件事，不要把不相干的功能混在一起。"
验收标准（你来检查）：
- 你能指着每个目录说出"这是管 XX 的"。
- 没有那种"啥都往里塞"的杂物目录。
输出物： 项目目录树 + 每个目录的一句话说明。
常用追问话术
| 场景 | 话术 |
|---|---|
| 列方案 | "列出 3–5 种可行方案，每种一句话。" |
| 曝代价 | "每个方案的隐性代价是什么？" |
| 求简化 | "有没有更简单的做法？去掉不必要的组件。" |
| 求大白话 | "用一个生活里的例子解释这个方案，假设我完全不懂技术。" |
| 学取舍 | "为什么选这个方案，不选另一个？它好在哪、差在哪？" |
| 压复杂度 | "我的机器只有 X 配置，给我一个进程就能跑的方案。" |
| 问维护 | "一年后这方案出问题，修复流程是什么？" |
| 问数据 | "关机重开后，我的数据还在吗？数据存在哪？" |
| 问结构 | "给我画一下项目目录结构，每个目录干什么的。" |
| 复盘学习 | "把这个项目我们做的架构决定和原因列一遍，我想记住这套思路。" |
出口门（声称 S2 完成前必过）
以下约束来自项目治理配置
harness.json（workflow.stages[S2].exit_gate）和CLAUDE.md。 在声称"选型阶段完成"之前，你必须逐条确认。 全过之后，最后一步：在docs/进度账本.md把 S2 标记为「已完成、出口门 ✓」，并提示用户"可进入 S3 上线准备（若要做成正式系统）"。
必须产出的内容
-
docs/项目说明书.md中「选定技术栈」已填写 -
docs/进度账本.md中 S2 各必经步骤为 ✅（S2.3 目录结构可跳并留痕） -
docs/项目说明书.md中「目录结构」建议填写（非强制）
硬性检查
- 「选定技术栈」中明确写出了选定了什么方案
- 「选定技术栈」中明确写出了否决了哪些方案及其否决理由
- 选定的方案与 PRD 中「形态与资源约束」的「它活在哪」兼容（如果 PRD 已存在）
- 目录结构中每个目录有一句话职责说明
- 没有"啥都往里塞"的杂物目录
自检完成声明
全部通过后声明： "✅ S2 出口门通过：技术栈已选定并写入项目说明书，否决方案和理由已记录，账本 S2 已标完成。可进入 S3 上线准备。"
© 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-architecture of Junliu1066/vibe-coding-kit.
Open the folder on GitHubat commit cb387af
Compare with similar skills
Vibe Coding Architecture 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Coding Architecture this skillJunliu1066/vibe-coding-kit | 109 | — | ~1.2k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 114 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
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.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
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.
Vibe Coding Prd
Junliu1066/vibe-coding-kit
一个"访谈式"的需求 Agent：通过一问一答 + 在岔路口给建议，把一个说不清需求的人，带到一份 AI 能直接照着开工的 PRD。
Vibe Coding Production
Junliu1066/vibe-coding-kit
把验证过的 Vibe Coding demo，做成能长期运行、给别人用的正式系统. An agent skill from Junliu1066/vibe-coding-kit.
Vibe Coding Requirements
Junliu1066/vibe-coding-kit
Vibe Coding（用 AI 写代码）项目的第一步：把模糊的想法，变成 AI 能精准落地、不会跑偏的需求. An agent skill from Junliu1066/vibe-coding-kit.
Vibe Coding Survival
Junliu1066/vibe-coding-kit
Vibe Coding（用 AI 写代码）开发过程中的避坑与自救——真正翻车大多发生在"开工后". An agent skill from Junliu1066/vibe-coding-kit.
Related
Categories
Questions about Vibe Coding Architecture
What does Vibe Coding Architecture do?
教非技术背景的人看懂技术架构、做好技术选型——把"只会照搬话术的小白"练成"能看穿方案好坏的人". An agent skill from Junliu1066/vibe-coding-kit. Vibe Coding Architecture is an agent skill from Junliu1066/vibe-coding-kit.
When should I use Vibe Coding Architecture?
Vibe Coding Architecture fits situations like: product & Project Management work in your project.
How do I install Vibe Coding Architecture in Claude Code?
Run `npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a claude-code`. Or copy the skill folder (skills/vibe-coding-architecture in Junliu1066/vibe-coding-kit) into .claude/skills/vibe-coding-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Coding Architecture in Codex?
Run `npx skills add Junliu1066/vibe-coding-kit --skill vibe-coding-architecture -a codex`. Or copy the skill folder (skills/vibe-coding-architecture in Junliu1066/vibe-coding-kit) into .agents/skills/vibe-coding-architecture in your project. Codex loads it when a task matches its description.
Can I use Vibe Coding Architecture 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-architecture -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-architecture, .gemini/skills/vibe-coding-architecture, .github/skills/vibe-coding-architecture and .opencode/skills/vibe-coding-architecture in your project.
What does Vibe Coding Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe Coding Architecture is instructions for the agent only.
Does Vibe Coding Architecture 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 Architecture 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 Architecture use?
Vibe Coding Architecture 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 Architecture use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 Architecture?
Skills that share tags, products or a category with Vibe Coding Architecture: 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 Architecture?
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.