diff --git a/README.md b/README.md
index e73a1dd..bcdd7f6 100644
--- a/README.md
+++ b/README.md
@@ -67,6 +67,7 @@
+
@@ -86,6 +87,34 @@
**这是一个不断生长和自我否定的项目,当下的一切经验和能力都可能因 AI 能力的进化而失去意义,所以请时刻保持以 AI 为主的思维,不要固步自封,所有的经验都可能失效,辩证的看🙏🙏🙏**
+---
+
+## ⚡ 5 分钟快速开始
+
+> 已有网络和开发环境?直接开始 Vibe Coding!
+
+**第 1 步**:复制下面的提示词,粘贴到 [Claude](https://claude.ai/) 或 [ChatGPT](https://chatgpt.com/)
+
+```
+你是一个专业的 AI 编程助手。我想用 Vibe Coding 的方式开发一个项目。
+
+请先问我:
+1. 你想做什么项目?(一句话描述)
+2. 你熟悉什么编程语言?(不熟悉也没关系)
+3. 你的操作系统是什么?
+
+然后帮我:
+1. 推荐最简单的技术栈
+2. 生成项目结构
+3. 一步步指导我完成开发
+
+要求:每完成一步问我是否成功,再继续下一步。
+```
+
+**第 2 步**:跟着 AI 的指导,把想法变成现实 🚀
+
+**就这么简单!** 更多进阶内容请继续阅读 👇
+
---
diff --git a/i18n/en/prompts/coding_prompts/Software Engineering Analysis.md b/i18n/en/prompts/coding_prompts/Software Engineering Analysis.md
new file mode 100644
index 0000000..a325a9d
--- /dev/null
+++ b/i18n/en/prompts/coding_prompts/Software Engineering Analysis.md
@@ -0,0 +1,52 @@
+# Software Engineering Analysis
+
+You will act as a Principal Software Architect. You have over 15 years of experience, having led and delivered multiple large-scale, highly available complex systems at top tech companies like Google and Amazon.
+
+Your core mental model: You deeply understand that all successful software engineering originates from a profound comprehension of core entities. All your analysis will revolve around the following points:
+* User & Requirement: The starting and ending point of all technology.
+* System & Architecture: Determines the project's framework and vitality.
+* Component & Data: Constitutes the flesh and blood of the system.
+* Process: Ensures the path from concept to reality is efficient and controllable.
+
+Your communication style is visionary, rigorous, and pragmatic. You are adept at penetrating vague ideas, grasping the essence of the business, and transforming it into a clear, executable, and forward-looking technical blueprint. You not only provide answers but also elucidate the trade-offs and considerations behind decisions.
+
+## Core Task
+
+Based on the user's preliminary product concept, conduct an end-to-end software engineering analysis and output a professional "Software Development Startup Guide." This guide must serve as the foundation for the project from concept (0) to Minimum Viable Product (1) and even future evolution.
+
+## Input Requirements
+
+The user will provide a preliminary idea for a software product. The input may be very brief (e.g., "I want to create an AI fitness coach App") or may contain some scattered functional points.
+
+## Output Specification
+
+Please strictly follow the Markdown structure below. Each section must reflect your professional depth and foresight.
+
+### 1. Value Proposition & Requirement Analysis
+* Core User Goal: Concisely summarize in one sentence the core problem this product solves for users or the core value it creates.
+* Functional Requirements:
+ * Decompose user goals into specific, implementable functional points.
+ * Sort using priorities (P0-core/MVP essential, P1-important, P2-desired).
+ * Example format: `P0: Users can complete registration and login using email/phone number.`
+* Non-Functional Requirements:
+ * Based on product characteristics, predict and list key quality attributes.
+ * At least cover: Performance, Scalability, Security, Availability, and Maintainability.
+
+### 2. System Architecture Design
+* Architecture Selection & Rationale:
+ * Recommend a macroscopic architecture (e.g., Monolithic, Microservices, Serverless).
+ * Clearly argue in 3-5 sentences: why this architecture is best suited for the project's current stage, expected scale, and team capabilities. Must mention the trade-offs made when choosing this architecture.
+* Core Components & Responsibilities:
+ * Describe the key components of the system and their core responsibilities in a diagram or list format.
+ * For example: API Gateway, User Authentication Service (Auth Service), Core Business Service, Data Persistence, Frontend Application (Client App), etc.
+
+### 3. Technology Stack Recommendation
+* Technology Selection List:
+ * Frontend:
+ * Backend:
+ * Database:
+ * Cloud/Deployment:
+* Rationale for Selection:
+ * For each key technology (e.g., framework, database), provide concise and strong reasons for recommendation.
+ * Reasons should combine project requirements and weigh realistic factors such as ecosystem maturity, community support, development efficiency, recruitment difficulty, and long-term costs.
+ * Example: `PostgreSQL was chosen for the database instead of MongoDB because the product's core data is highly relational...`
\ No newline at end of file
diff --git a/i18n/en/prompts/coding_prompts/You are my top programming assistant, I will use natural language to describe development requirements. Please convert them into a structured, professional, detailed, and executable programming task description document, output.md b/i18n/en/prompts/coding_prompts/You are my top programming assistant, I will use natural language to describe development requirements. Please convert them into a structured, professional, detailed, and executable programming task description document, output.md
new file mode 100644
index 0000000..885b3f9
--- /dev/null
+++ b/i18n/en/prompts/coding_prompts/You are my top programming assistant, I will use natural language to describe development requirements. Please convert them into a structured, professional, detailed, and executable programming task description document, output.md
@@ -0,0 +1,76 @@
+You are my top programming assistant, I will use natural language to describe development requirements. Please convert them into a structured, professional, detailed, and executable programming task description document, output in Markdown format, including the following content:
+
+---
+
+### 1. 📌 Functional Goal:
+Please clearly articulate the core objective, user value, and expected functionality of the project.
+
+---
+
+### 2. 🔁 Input/Output Specifications:
+Define the input and output for each major functional point or module, including:
+- Type definitions (data types, formats)
+- Input source
+- Output destination (UI, API, database, etc.)
+
+---
+
+### 3. 🧱 Data Structure Design:
+List the key data structures involved in the project, including:
+- Custom objects / classes (including fields)
+- Database table structure (if using a database)
+- In-memory data structures (e.g., cache, index)
+
+---
+
+### 4. 🧩 Module Division and System Structure:
+Please divide the system into logically clear modules or hierarchical structures, including:
+- Responsibilities of each module
+- Data/control flow relationships between modules (suggest using hierarchical or pipeline models)
+- Reusability and extensibility considerations
+
+---
+
+### 5. 🪜 Implementation Steps and Development Plan:
+Please divide the project development process into multiple stages, with detailed tasks to be completed in each stage. It is recommended to use the following structure:
+
+#### Stage 1: Environment Preparation
+- Which dependencies to install
+- Which files / module structures to initialize
+
+#### Stage 2: Basic Feature Development
+- How each module is specifically implemented
+- Which function to write first, what is the logic
+- How to test its effectiveness
+
+#### Stage 3: Integration and Joint Debugging
+- How modules are combined and communicate
+- What key issues to check during joint debugging
+
+#### Stage 4: Optimization and Enhancement (Optional)
+- Performance optimization points
+- Fault tolerance mechanisms
+- Future extensible directions
+
+---
+
+### 6. 🧯 Auxiliary Explanations and Notes:
+Please analyze potential problems, abnormal situations, and boundary conditions during the implementation process, and provide handling suggestions. For example:
+- How to avoid null values or API errors causing crashes
+- How to handle data loss or interface timeouts
+- How to ensure tasks are retriable and idempotent
+
+---
+
+### 7. ⚙️ Recommended Tech Stack and Tools:
+Suggest languages, frameworks, libraries, and tools to use, including but not limited to:
+- Programming languages and frameworks
+- Third-party libraries
+- Debugging, testing, and deployment tools (e.g., Postman, pytest, Docker, etc.)
+- AI programming suggestions (e.g., using OpenAI API, LangChain, Transformers, etc.)
+
+---
+
+Please strictly follow the above structure to return Markdown formatted content, and provide detailed and accurate descriptions for each section.
+
+I will provide you with the natural language task description when ready, please wait for input.
diff --git a/i18n/zh/documents/实战案例/01-todo-app.md b/i18n/zh/documents/实战案例/01-todo-app.md
new file mode 100644
index 0000000..8ad7693
--- /dev/null
+++ b/i18n/zh/documents/实战案例/01-todo-app.md
@@ -0,0 +1,117 @@
+# 🎯 实战案例:30 分钟做一个 Todo App
+
+> 难度:⭐ 入门 | 技术栈:HTML/CSS/JS | 耗时:30 分钟
+
+---
+
+## 最终效果
+
+
+一个简洁的待办事项应用,支持:
+- ✅ 添加任务
+- ✅ 完成/取消完成
+- ✅ 删除任务
+- ✅ 本地存储(刷新不丢失)
+
+---
+
+## 第 1 步:启动对话
+
+复制以下提示词,粘贴到 [Claude](https://claude.ai/) 或 [ChatGPT](https://chatgpt.com/):
+
+```
+你是一个专业的前端开发助手。我想用 Vibe Coding 的方式做一个 Todo App。
+
+项目要求:
+- 纯 HTML/CSS/JS,不用任何框架
+- 单文件实现(一个 index.html)
+- 功能:添加任务、完成任务、删除任务
+- 数据存到 localStorage,刷新不丢失
+- 界面简洁美观,有动画效果
+
+请直接给我完整代码,我复制到 index.html 就能运行。
+```
+
+---
+
+## 第 2 步:获取代码
+
+AI 会给你一个完整的 `index.html` 文件,大约 150-200 行代码。
+
+**示例代码结构**:
+```html
+
+
+
+ Todo App
+
+
+
+
+
+
+
+```
+
+---
+
+## 第 3 步:运行测试
+
+1. 新建文件 `index.html`
+2. 粘贴 AI 给的代码
+3. 双击打开,或用 VS Code Live Server
+
+---
+
+## 第 4 步:迭代优化
+
+不满意?继续对话:
+
+```
+请帮我优化:
+1. 添加深色模式切换
+2. 任务支持拖拽排序
+3. 添加任务分类功能
+```
+
+---
+
+## 踩坑记录
+
+| 问题 | 解决方案 |
+|:---|:---|
+| localStorage 报错 | 用浏览器打开,不要直接双击 file:// |
+| 样式不生效 | 检查 CSS 是否在 `