🤖 Codex 协作协议 (Codex Collaboration Protocol - CAP)
📌 项目指纹
- 项目名称：Codex 蓝皮书
- 项目类型：Markdown 指南 / 电子书项目
- 写作风格：专业、精炼、技术密度高、易读的中文，伴以恰当的格式与图表。
- 引用规范：链接必须使用
file:///格式的绝对路径（例如：[link text](file:///Users/hunkwu/Desktop/ai/book/README.md)）。
🎯 目标受众
- 希望利用 AI 智能体（尤其是 OpenAI Codex）进行高效开发的专业开发者。
- 想要自主构建商业级 MVP 的独立黑客与创业者。
🛑 约束红线
- 严禁使用占位符：必须提供真实、可运行的示例代码和配置。
- 注重实操：每个章节必须包含逐步的代码片段、命令行执行或配置文件模版。
- 链接完整：确保各章节之间的链接引用正确，无死链。
- 杜绝冗长摘要：避免重复内容；专注于可落地的洞察、心智模型和步骤演练。
🧪 验证标准
- 所有 Markdown 文件必须语法正确，且链接到真实存在的目标路径。
- 所有代码块必须带有正确的语言标签（例如：
```bash,```markdown,```json）。
🌐 English Version
🤖 Codex Collaboration Protocol (CAP)
📌 Project Signature
- Project Name: Codex Blue Book
- Framework: Markdown Guide / Book Project
- Coding Style: Professional, concise, tech-rich, easy-to-read Chinese with proper formatting and diagrams.
- Reference Style: Links should be absolute paths with
file:///scheme (e.g.[link text](file:///Users/hunkwu/Desktop/ai/book/README.md)).
🎯 Target Audience
- Professional developers looking to leverage AI agents (especially OpenAI Codex) for high-efficiency development.
- Indie Hackers / Entrepreneurs wanting to build commercial-grade MVPs autonomously.
🛑 Hard Constraints
- Do not use placeholders: Always provide real, functional examples and configurations.
- Keep it practical: Every chapter must contain step-by-step code snippets, command executions, or configuration templates.
- Preserve Links: Ensure all links between chapters are correctly referenced.
- No verbose summaries: Avoid repeating contents; focus on actionable insights, mental models, and step-by-step walkthroughs.
🧪 Verification Specs
- All markdown files must be syntactically valid and link to actual target paths.
- Code blocks must have language tags (e.g.
```bash,```markdown,```json).