chore(doc):Add blog cover image
This commit is contained in:
david_bai
@@ -3,13 +3,19 @@ title: "Damit KI nicht mehr abschweift: ein praxistaugliches Collaboration‑Pla
|
||||
description: "Geht KI‑Code ständig am Thema vorbei? Mit AGENTS.md, einem AI Playbook und einem plan-first‑Workflow wird Codex/Claude zum echten Teammate: weniger Nacharbeit, bessere Wartbarkeit. Mit Next.js‑Praxisbeispielen."
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags:
|
||||
["KI‑Zusammenarbeit", "Codex", "Engineering‑Prozess", "Open Source", "Next.js"]
|
||||
[
|
||||
"KI‑Zusammenarbeit",
|
||||
"Codex",
|
||||
"Engineering‑Prozess",
|
||||
"Open Source",
|
||||
"Next.js",
|
||||
]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Kommt dir das bekannt vor?
|
||||
|
||||
@@ -60,10 +66,12 @@ Ein Ziel, zuerst der Plan; Privacy/Architektur‑Redlines nie brechen; done hei
|
||||
Drei Klassiker:
|
||||
|
||||
1. **„Ändere den Code“ ohne Plan**
|
||||
|
||||
- Folge: 10 Dateien später stellst du fest, dass die Richtung falsch war—Rollback wird teuer
|
||||
- Besser: zuerst Change‑Plan, Implementierung erst nach Approval
|
||||
|
||||
2. **Alle Dokus in den Prompt kippen**
|
||||
|
||||
- Folge: Kontext‑Overload; die KI verliert das Wesentliche (findet nicht mal Entry Points)
|
||||
- Besser: High‑Signal‑Index + Code‑Map
|
||||
|
||||
@@ -79,11 +87,11 @@ Sieh `AGENTS.md` als maschinenlesbare Version eurer „Defaults“ und „Red Li
|
||||
|
||||
In PrivyDrop reichen fünf Punkte:
|
||||
|
||||
- Plan first: `AGENTS.en.md`
|
||||
- One change, one purpose: `AGENTS.en.md`
|
||||
- Privacy & architecture red line: `AGENTS.en.md`
|
||||
- Docs must stay in sync: `AGENTS.en.md`
|
||||
- Verification required: `AGENTS.en.md`
|
||||
- Plan first: `AGENTS.en.md:7`
|
||||
- One change, one purpose: `AGENTS.en.md:8`
|
||||
- Privacy & architecture red line: `AGENTS.en.md:9`
|
||||
- Docs must stay in sync: `AGENTS.en.md:12`
|
||||
- Verification required: `AGENTS.en.md:13`
|
||||
|
||||
Datei: [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -166,9 +174,9 @@ Optional: „Common requests → Entry Points“:
|
||||
```md
|
||||
Common request routing
|
||||
|
||||
- New page / SEO: frontend/app/**/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/*
|
||||
- Blog: frontend/content/blog/* + frontend/lib/blog.ts
|
||||
- New page / SEO: frontend/app/\*\*/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/\*
|
||||
- Blog: frontend/content/blog/\* + frontend/lib/blog.ts
|
||||
```
|
||||
|
||||
---
|
||||
@@ -315,4 +323,3 @@ docs/
|
||||
## Schluss
|
||||
|
||||
KI‑gestützte Entwicklung reduziert Rigorosität nicht—sie erhöht sie. Nachhaltige Geschwindigkeit kommt aus starken Constraints: Regeln externalisieren, plan-first, Flows dokumentieren, Kontext langlebig machen.
|
||||
|
||||
|
||||
@@ -3,13 +3,13 @@ title: "Keep AI on Track: A Practical, Repeatable Collaboration Playbook (with T
|
||||
description: "Tired of AI-written code going off the rails? Turn Codex/Claude into a real teammate with AGENTS.md, an AI Playbook, and a plan-first workflow—less rework, more maintainable code. Includes real Next.js examples."
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags:
|
||||
["AI Collaboration", "Codex", "Engineering Process", "Open Source", "Next.js"]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Have you ever been in this situation?
|
||||
|
||||
@@ -60,10 +60,12 @@ Single goal, plan first; never cross privacy/architecture red lines; done means
|
||||
Before we begin, here are the three most common wrong approaches:
|
||||
|
||||
1. **Tell AI to “change code” without a plan**
|
||||
|
||||
- Result: 10 files changed, then you realize the direction is wrong—rollback becomes painful
|
||||
- Better: require a change plan first; implement only after approval
|
||||
|
||||
2. **Dump every document into the prompt**
|
||||
|
||||
- Result: context overload; AI can’t see the signal (it can’t even locate entry points)
|
||||
- Better: provide a high-signal index + code map
|
||||
|
||||
@@ -79,11 +81,11 @@ Think of `AGENTS.md` as a machine-readable version of your team’s “defaults
|
||||
|
||||
In PrivyDrop, five lines are enough to cover the core of engineering collaboration constraints:
|
||||
|
||||
- Plan first: `AGENTS.en.md`
|
||||
- One change, one purpose: `AGENTS.en.md`
|
||||
- Privacy & architecture red line: `AGENTS.en.md`
|
||||
- Docs must stay in sync: `AGENTS.en.md`
|
||||
- Verification required: `AGENTS.en.md`
|
||||
- Plan first: `AGENTS.en.md:7`
|
||||
- One change, one purpose: `AGENTS.en.md:8`
|
||||
- Privacy & architecture red line: `AGENTS.en.md:9`
|
||||
- Docs must stay in sync: `AGENTS.en.md:12`
|
||||
- Verification required: `AGENTS.en.md:13`
|
||||
|
||||
File: [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -166,9 +168,9 @@ Optional: add a “common requests → entry points” cheat sheet to reduce sea
|
||||
```md
|
||||
Common request routing
|
||||
|
||||
- New page / SEO: frontend/app/**/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/*
|
||||
- Blog: frontend/content/blog/* + frontend/lib/blog.ts
|
||||
- New page / SEO: frontend/app/\*\*/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/\*
|
||||
- Blog: frontend/content/blog/\* + frontend/lib/blog.ts
|
||||
```
|
||||
|
||||
How to generate (and iterate) a code map:
|
||||
@@ -378,4 +380,3 @@ If you already have docs scattered everywhere: start with `index.md` to unify en
|
||||
AI-assisted development doesn’t reduce the need for rigor—it increases it. The sustainable speed-up doesn’t come from longer prompts, but from stronger engineering constraints: externalize rules, plan first, codify flows, and make context durable.
|
||||
|
||||
If you want to go further, this can evolve into a “copyable repo scaffold”: PR templates, issue templates, and a ready-to-use `AGENTS.md` + playbook starter kit.
|
||||
|
||||
|
||||
@@ -3,13 +3,19 @@ title: "Que la IA no se desvíe: un método de colaboración realmente aplicable
|
||||
description: "¿La IA escribe código y se sale del tema? Convierte Codex/Claude en un compañero de equipo con AGENTS.md, un AI Playbook y un flujo plan-first: menos retrabajo, más mantenibilidad. Con ejemplos reales en Next.js."
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags:
|
||||
["Colaboración con IA", "Codex", "Proceso de ingeniería", "Código abierto", "Next.js"]
|
||||
[
|
||||
"Colaboración con IA",
|
||||
"Codex",
|
||||
"Proceso de ingeniería",
|
||||
"Código abierto",
|
||||
"Next.js",
|
||||
]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
¿Te suena alguno de estos escenarios?
|
||||
|
||||
@@ -60,10 +66,12 @@ Un solo objetivo, primero el plan; no cruzar líneas rojas de privacidad/arquite
|
||||
Antes de empezar, tres errores típicos:
|
||||
|
||||
1. **Pedirle a la IA “cambia el código” sin plan**
|
||||
|
||||
- Resultado: cambia 10 archivos y luego descubres que la dirección era incorrecta; revertir duele
|
||||
- Correcto: exigir un plan primero; implementar solo tras aprobarlo
|
||||
|
||||
2. **Meter todos los documentos en el prompt**
|
||||
|
||||
- Resultado: explosión de contexto; la IA pierde la señal (ni encuentra los entry points)
|
||||
- Correcto: usar index + code-map como navegación de alta señal
|
||||
|
||||
@@ -79,11 +87,11 @@ Piensa en `AGENTS.md` como la versión “legible por máquina” de los valores
|
||||
|
||||
En PrivyDrop, cinco puntos bastan para cubrir el núcleo:
|
||||
|
||||
- Plan first: `AGENTS.en.md`
|
||||
- One change, one purpose: `AGENTS.en.md`
|
||||
- Privacy & architecture red line: `AGENTS.en.md`
|
||||
- Docs must stay in sync: `AGENTS.en.md`
|
||||
- Verification required: `AGENTS.en.md`
|
||||
- Plan first: `AGENTS.en.md:7`
|
||||
- One change, one purpose: `AGENTS.en.md:8`
|
||||
- Privacy & architecture red line: `AGENTS.en.md:9`
|
||||
- Docs must stay in sync: `AGENTS.en.md:12`
|
||||
- Verification required: `AGENTS.en.md:13`
|
||||
|
||||
Archivo: [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -166,9 +174,9 @@ Opcional: añade una tabla de “solicitud común → entry points”:
|
||||
```md
|
||||
Common request routing
|
||||
|
||||
- New page / SEO: frontend/app/**/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/*
|
||||
- Blog: frontend/content/blog/* + frontend/lib/blog.ts
|
||||
- New page / SEO: frontend/app/\*\*/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/\*
|
||||
- Blog: frontend/content/blog/\* + frontend/lib/blog.ts
|
||||
```
|
||||
|
||||
Cómo generarlo y mantenerlo:
|
||||
@@ -364,4 +372,3 @@ Si ya tienes docs dispersas: empieza por `index.md` para unificar el acceso; lue
|
||||
## Cierre
|
||||
|
||||
El desarrollo asistido por IA no reduce la necesidad de rigor; la incrementa. La velocidad sostenible no viene de prompts más largos, sino de restricciones más fuertes: reglas externalizadas, plan-first, flows codificados y contexto durable.
|
||||
|
||||
|
||||
@@ -3,13 +3,19 @@ title: "Empêcher l’IA de dérailler : une méthode de collaboration vraiment
|
||||
description: "Votre IA part dans tous les sens quand elle code ? Transformez Codex/Claude en vrai coéquipier grâce à AGENTS.md, un AI Playbook et un workflow plan-first : moins de retours en arrière, plus de maintenabilité. Exemples Next.js inclus."
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags:
|
||||
["Collaboration IA", "Codex", "Processus d’ingénierie", "Open Source", "Next.js"]
|
||||
[
|
||||
"Collaboration IA",
|
||||
"Codex",
|
||||
"Processus d’ingénierie",
|
||||
"Open Source",
|
||||
"Next.js",
|
||||
]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
Vous avez déjà vécu ça ?
|
||||
|
||||
@@ -69,11 +75,11 @@ Le remède est toujours le même : index + code-map + flows, puis un plan approu
|
||||
|
||||
`AGENTS.md` = la version “machine‑readable” de vos règles et lignes rouges. Dans PrivyDrop, cinq points suffisent :
|
||||
|
||||
- Plan first : `AGENTS.en.md`
|
||||
- One change, one purpose : `AGENTS.en.md`
|
||||
- Privacy & architecture red line : `AGENTS.en.md`
|
||||
- Docs must stay in sync : `AGENTS.en.md`
|
||||
- Verification required : `AGENTS.en.md`
|
||||
- Plan first : `AGENTS.en.md:7`
|
||||
- One change, one purpose : `AGENTS.en.md:8`
|
||||
- Privacy & architecture red line : `AGENTS.en.md:9`
|
||||
- Docs must stay in sync : `AGENTS.en.md:12`
|
||||
- Verification required : `AGENTS.en.md:13`
|
||||
|
||||
Fichier : [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -158,5 +164,3 @@ docs/
|
||||
## Conclusion
|
||||
|
||||
Le développement assisté par IA ne réduit pas l’exigence de rigueur : il l’augmente. La vitesse durable vient de contraintes claires, de plans approuvés, de flows documentés et d’un contexte qui survit aux conversations.
|
||||
|
||||
|
||||
|
||||
@@ -3,13 +3,13 @@ title: "AIを迷走させない：すぐ使える協働のエンジニアリン
|
||||
description: "AIにコードを書かせると脱線しがち？AGENTS.md・AI Playbook・Plan-first の型で、Codex/Claude を“協働できる相棒”に。手戻りを減らし、保守性を上げる。Next.js 実戦例つき。"
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags:
|
||||
["AI協働", "Codex", "エンジニアリングプロセス", "オープンソース", "Next.js"]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
こんな経験はありませんか？
|
||||
|
||||
@@ -24,7 +24,7 @@ AI を「速い検索ボックス」として使うなら、これらの問題
|
||||
最終的に、どんなリポジトリにもそのまま移植できる最小セットが手に入ります：
|
||||
|
||||
- `AGENTS.md`：プロジェクトのハード制約（レッドライン、デフォルト、Done の定義）
|
||||
- `docs/ai-playbook/index.md`：高シグナルな入口（1ページ索引）
|
||||
- `docs/ai-playbook/index.md`：高シグナルな入口（1 ページ索引）
|
||||
- `docs/ai-playbook/code-map.md`：コード地図（どこを触るか）
|
||||
- `docs/ai-playbook/flows.md`：重要フロー（どう動くか）
|
||||
- `docs/ai-playbook/collab-rules.md`：協働ルール + 変更計画テンプレ（どう進めるか）
|
||||
@@ -60,10 +60,12 @@ AI を「速い検索ボックス」として使うなら、これらの問題
|
||||
始める前に、ありがちな 3 つの間違い：
|
||||
|
||||
1. **計画なしで AI に「コードを直して」と言う**
|
||||
|
||||
- 結果：10 ファイル変わってから方向違いに気づき、戻すコストが爆発する
|
||||
- 正解：先に変更計画を出させ、承認してから実装
|
||||
|
||||
2. **ドキュメントを全部 AI に投げる**
|
||||
|
||||
- 結果：文脈が飽和して要点が消える（入口ファイルすら見つけられない）
|
||||
- 正解：高シグナルな index + code-map に絞る
|
||||
|
||||
@@ -79,11 +81,11 @@ AI を「速い検索ボックス」として使うなら、これらの問題
|
||||
|
||||
PrivyDrop では、工学的な協働に必要な要点は 5 行に集約できます：
|
||||
|
||||
- Plan first：`AGENTS.en.md`
|
||||
- One change, one purpose：`AGENTS.en.md`
|
||||
- Privacy & architecture red line：`AGENTS.en.md`
|
||||
- Docs must stay in sync：`AGENTS.en.md`
|
||||
- Verification required：`AGENTS.en.md`
|
||||
- Plan first：`AGENTS.en.md:7`
|
||||
- One change, one purpose：`AGENTS.en.md:8`
|
||||
- Privacy & architecture red line：`AGENTS.en.md:9`
|
||||
- Docs must stay in sync：`AGENTS.en.md:12`
|
||||
- Verification required：`AGENTS.en.md:13`
|
||||
|
||||
ファイル： [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -166,9 +168,9 @@ AI が脱線する最大要因のひとつは、**あなたのコードの“入
|
||||
```md
|
||||
Common request routing
|
||||
|
||||
- New page / SEO: frontend/app/**/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/*
|
||||
- Blog: frontend/content/blog/* + frontend/lib/blog.ts
|
||||
- New page / SEO: frontend/app/\*\*/page.tsx + metadata.ts
|
||||
- i18n copy: frontend/constants/messages/\*
|
||||
- Blog: frontend/content/blog/\* + frontend/lib/blog.ts
|
||||
```
|
||||
|
||||
生成と運用：
|
||||
@@ -191,7 +193,7 @@ code-map が「どこを触るか」なら、flows は「どう動くか」で
|
||||
|
||||
1. **重要フロー / 時系列**（必要なら Mermaid）
|
||||
2. **デバッグ要点**（見るべきログ/状態）
|
||||
3. **マイクロ計画テンプレ**（計画→承認→実装を強制）
|
||||
3. **マイクロ計画テンプレ**（計画 → 承認 → 実装を強制）
|
||||
|
||||
運用のコツ：
|
||||
|
||||
@@ -378,4 +380,3 @@ docs/
|
||||
AI 支援開発は厳密さを減らすのではなく、むしろ増やします。持続可能なスピードは、長いプロンプトではなく強い工程制約から生まれます：ルールの外部化、Plan-first、フローの文書化、そして文脈の持久力。
|
||||
|
||||
さらに工程化するなら、PR/issue テンプレと、すぐ使える `AGENTS.md`/playbook 初期セットを含む「コピーできるリポジトリ雛形」に進化させるのも良いです。
|
||||
|
||||
|
||||
@@ -3,13 +3,12 @@ title: "AI가 엇나가지 않게: 바로 적용 가능한 협업 엔지니어
|
||||
description: "AI로 코드를 쓰면 자꾸 탈선하나요? AGENTS.md, AI Playbook, plan-first 워크플로로 Codex/Claude를 ‘함께 일하는 동료’로 만들 수 있습니다. 재작업을 줄이고 유지보수성을 높입니다. Next.js 실전 예시 포함."
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
tags:
|
||||
["AI 협업", "Codex", "엔지니어링 프로세스", "오픈 소스", "Next.js"]
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags: ["AI 협업", "Codex", "엔지니어링 프로세스", "오픈 소스", "Next.js"]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
이런 상황을 겪어본 적 있나요?
|
||||
|
||||
@@ -69,11 +68,11 @@ OpenAI의 실전 글도 접근 방식이 매우 비슷합니다:
|
||||
|
||||
`AGENTS.md`는 팀의 “기본값과 레드라인”을 기계가 읽을 수 있게 만든 버전입니다. PrivyDrop에서는 아래 다섯 가지가 핵심입니다:
|
||||
|
||||
- Plan first: `AGENTS.en.md`
|
||||
- One change, one purpose: `AGENTS.en.md`
|
||||
- Privacy & architecture red line: `AGENTS.en.md`
|
||||
- Docs must stay in sync: `AGENTS.en.md`
|
||||
- Verification required: `AGENTS.en.md`
|
||||
- Plan first: `AGENTS.en.md:7`
|
||||
- One change, one purpose: `AGENTS.en.md:8`
|
||||
- Privacy & architecture red line: `AGENTS.en.md:9`
|
||||
- Docs must stay in sync: `AGENTS.en.md:12`
|
||||
- Verification required: `AGENTS.en.md:13`
|
||||
|
||||
파일: [AGENTS.en.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.en.md)
|
||||
|
||||
@@ -158,5 +157,3 @@ docs/
|
||||
## 마무리
|
||||
|
||||
AI 보조 개발은 엄밀함을 줄이지 않습니다. 오히려 더 필요합니다. 지속 가능한 속도는 더 긴 프롬프트가 아니라 더 강한 엔지니어링 제약에서 나옵니다: 규칙 외부화, 계획 선행, 플로우 문서화, 그리고 문맥의 지속성.
|
||||
|
||||
|
||||
|
||||
@@ -3,13 +3,12 @@ title: "让 AI 不再跑偏：可落地的协作工程化方法（附模板）"
|
||||
description: "用 AI 写代码总跑偏？这套方法让 Claude code/Codex 变成可协作队友：AGENTS.md、AI Playbook、变更计划模板，减少返工、提升代码可维护性。附完整实现与 Next.js 实战案例。"
|
||||
date: "2025-12-26"
|
||||
author: "david bai"
|
||||
cover: "/blog-assets/privydrop-open-source.jpg"
|
||||
tags:
|
||||
["AI 协作", "Codex", "工程流程", "开源", "Next.js"]
|
||||
cover: "/blog-assets/ai-collaboration-playbook.webp"
|
||||
tags: ["AI 协作", "Codex", "工程流程", "开源", "Next.js"]
|
||||
status: "published"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
你是否遇到过这样的场景：
|
||||
|
||||
@@ -60,10 +59,12 @@ status: "published"
|
||||
在开始之前，先看看最常见的 3 个错误做法：
|
||||
|
||||
1. **直接让 AI "改代码"，不要计划**
|
||||
|
||||
- 后果：改了 10 个文件，最后发现方向错了，回滚成本巨大
|
||||
- 正确做法：先让 AI 输出变更计划，你批准后再动手
|
||||
|
||||
2. **把所有文档都塞给 AI**
|
||||
|
||||
- 后果：上下文爆炸，AI 反而抓不住重点（连"入口文件在哪"都找不到）
|
||||
- 正确做法：用 index + code-map 提供高信噪比导航
|
||||
|
||||
@@ -79,11 +80,11 @@ status: "published"
|
||||
|
||||
在 PrivyDrop 里，建议重点展示这 5 条（足够代表"工程协作约束"的核心）：
|
||||
|
||||
- 计划先行：`AGENTS.zh-CN.md`
|
||||
- 单一主题：`AGENTS.zh-CN.md`
|
||||
- 隐私与架构红线：`AGENTS.zh-CN.md`
|
||||
- 文档同步：`AGENTS.zh-CN.md`
|
||||
- 验证要求：`AGENTS.zh-CN.md`
|
||||
- 计划先行：`AGENTS.zh-CN.md:7`
|
||||
- 单一主题：`AGENTS.zh-CN.md:8`
|
||||
- 隐私与架构红线：`AGENTS.zh-CN.md:9`
|
||||
- 文档同步：`AGENTS.zh-CN.md:12`
|
||||
- 验证要求：`AGENTS.zh-CN.md:13`
|
||||
|
||||
对应文件：[AGENTS.zh-CN.md](https://github.com/david-bai00/PrivyDrop/blob/main/AGENTS.zh-CN.md)
|
||||
|
||||
@@ -107,13 +108,15 @@ status: "published"
|
||||
|
||||
- 创建 `AGENTS.zh-CN.md` 和 `AGENTS.en.md`
|
||||
- 每个协作者首次 clone 仓库后，根据语言选择创建符号链接：
|
||||
|
||||
```bash
|
||||
# 中文用户
|
||||
ln -s AGENTS.zh-CN.md AGENTS.md
|
||||
|
||||
|
||||
# 英文用户
|
||||
ln -s AGENTS.en.md AGENTS.md
|
||||
```
|
||||
|
||||
- 在 `.gitignore` 中添加 `AGENTS.md`，避免符号链接冲突
|
||||
|
||||
不同语言版本的 `AGENTS.md` 已经包含了各自语言的其他文档引用路径。
|
||||
@@ -344,7 +347,7 @@ OpenAI 在《我们如何使用 Codex 在 28 天内构建 Android 版 Sora》里
|
||||
- 上下文续航：当达到背景窗口限制时，把计划写入文件供下一次会话继续
|
||||
- 多会话并行：更像在“管理一个团队”，而不是使用单一工具
|
||||
|
||||
虽然安卓开发与web开发领域不一样，但方法值得借鉴：**先把输入变好，输出自然会稳定**。
|
||||
虽然安卓开发与 web 开发领域不一样，但方法值得借鉴：**先把输入变好，输出自然会稳定**。
|
||||
|
||||
---
|
||||
|
||||
@@ -366,7 +369,6 @@ docs/
|
||||
collab-rules.md
|
||||
```
|
||||
|
||||
|
||||
如果你已经有文档但分散在各处：先做 index，把入口收束；然后再补 code-map/flows/模板即可。
|
||||
|
||||
---
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 59 KiB |
Reference in New Issue
Block a user