Borrowing it
Nothing to install: this file belongs to clxzl/claude-code-best-practice-cn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/clxzl/claude-code-best-practice-cn/main/.claude/skills/presentation/vibe-to-agentic-framework/SKILL.mdgit clone --depth 1 https://github.com/clxzl/claude-code-best-practice-cnWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/clxzl/claude-code-best-practice-cn/vibe-to-agentic-framework)<a href="https://agentmods.dev/skills/clxzl/claude-code-best-practice-cn/vibe-to-agentic-framework"><img src="https://agentmods.dev/badge/skills/clxzl/claude-code-best-practice-cn/vibe-to-agentic-framework/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/clxzl/claude-code-best-practice-cn/vibe-to-agentic-framework"><img src="https://agentmods.dev/badge/skills/clxzl/claude-code-best-practice-cn/vibe-to-agentic-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.03487 |
| Opus 5 | $0.00026 | $0.01743 |
| Sonnet 5 | $0.00011 | $0.00697 |
| Haiku 4.5 | $0.00005 | $0.00349 |
Grade A, and why
vibe-to-agentic-framework scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
"从 Vibe Coding 到 Agentic Engineering"框架
本技能教授演示文稿背后的概念模型。每张幻灯片和每个章节都在讲述一个故事:开发者如何从无结构的"vibe coding"(低级)逐步进阶到高级的 agentic engineering(高级)。
核心概念
Vibe Coding(低级) 是指开发者在没有任何结构的情况下使用 Claude Code —— 没有项目上下文、没有约定、没有可复用的知识。每次提示都像抛硬币一样。Claude 可能会创建随机的端点、忽略现有模式、跳过测试,并生成不一致的代码。代码库在每次交互中都趋向混乱。
Agentic Engineering(高级) 是指 Claude Code 作为一个完全配置的工程系统运行。它了解项目架构(CLAUDE.md)、遵循作用域约定(Rules)、按需加载领域专业知识(Skills)、委派给专业工作者(Agents)、编排多步骤工作流(Commands)、自动化生命周期事件(Hooks),并连接外部工具(MCP Servers)。每次提示都能产生一致的、经过测试的、生产就绪的代码。
这两个极端之间的旅程是渐进且累积的。每个最佳实践都建立在前一个之上,演示文稿按照开发者应采用的顺序来教授它们。
4 级旅程系统
演示文稿使用 4 级评分系统,而非百分比进度条:
| 级别 | 顺序 | 颜色 | 旅程条高度 | 描述 |
|---|---|---|---|---|
| Low | 1 | 红/橙色 (hsl(0, 70%, 45%)) |
25% | Vibe coding 地带 —— 无结构 |
| Medium | 2 | 黄色 (hsl(40, 70%, 45%)) |
50% | 结构化工作流,部分自动化 |
| High | 3 | 浅绿色 (hsl(80, 70%, 45%)) |
75% | 领域知识、Skills、自定义 Agents |
| Pro | 4 | 深绿色 (hsl(120, 70%, 45%)) |
100% | 完全的 agentic engineering,多代理团队 |
旅程条在第 1 张幻灯片(标题幻灯片)上隐藏,从第 2 张幻灯片开始显示。级别通过关键过渡幻灯片上的 data-level 属性设置,并被后续幻灯片继承,直到下一次级别变更。当级别变更时,.level-badge 通过 JS 注入到幻灯片的 h1 上(不要在 HTML 中硬编码这些)。
贯穿示例:TodoApp Monorepo
每项技术都在一个真实的全栈项目上进行演示。演示文稿展示了从普通项目(vibe coding)到具有完整 Claude Code 配置(agentic engineering)的项目的转变:
改造前(Vibe Coding):
todoapp/
├── backend/ # FastAPI (Python)
│ ├── main.py
│ ├── routes/
│ ├── models/
│ └── tests/
└── frontend/ # Next.js (TypeScript)
├── components/
├── pages/
└── lib/
改造后(Agentic Engineering):
todoapp/
├── .claude/ # Claude Code 配置
│ ├── agents/ # 自定义 Subagents
│ ├── skills/ # 领域知识
│ ├── commands/ # Slash Commands
│ ├── hooks/ # 生命周期脚本
│ ├── rules/ # 模块化指令
│ ├── settings.json # 团队设置
│ └── settings.local.json # 个人设置
├── backend/
│ └── CLAUDE.md # 后端指令
├── frontend/
│ └── CLAUDE.md # 前端指令
├── .mcp.json # 托管的 MCP 服务器
└── CLAUDE.md # 项目指令
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 171 lines · 53 tokens per session scan A b48e5941bba7
vibe-to-agentic-framework is a skill published in the GitHub repository clxzl/claude-code-best-practice-cn (127 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 3,487 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…