From dedfb60a4c37858850b9bf018978dfa5d7c7332f Mon Sep 17 00:00:00 2001 From: dal4segno Date: Thu, 26 Mar 2026 12:35:41 +0900 Subject: [PATCH] =?UTF-8?q?chore:=20Codex=20=EB=AC=B8=EC=84=9C=20=EB=B3=B4?= =?UTF-8?q?=EC=99=84=20=EB=A9=94=EB=AA=A8=20=EA=B7=9C=EC=B9=99=20=EC=B6=94?= =?UTF-8?q?=EA=B0=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 사용자 작성 옵시디언 문서는 원문 구조를 유지하도록 작업 규칙을 추가함 - Codex가 보완한 내용은 별도 구역으로 분리해 표시하도록 명시함 - 이후 세션에서도 동일한 문서 수정 규칙을 따르도록 AGENTS 지침을 보강함 --- AGENTS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 89a1e5a6..b077cdc2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -15,6 +15,9 @@ Design docs are maintained in Obsidian Vault: `\\Truenas\smb\Obsidian Vault\Colo - Always use the shared Obsidian Vault at `\\Truenas\smb\Obsidian Vault\Colosseum` for project documentation updates. - Do not write Colosseum design notes to `C:\Users\dal4s\OneDrive\문서\Obsidian Vault\Colosseum`; that path is not the active vault for this project. +- When editing user-authored Obsidian notes, preserve the user's original text structure as much as possible. +- If Codex adds interpretation, clarification, proposals, or implementation notes to a user-authored note, put them in a clearly labeled separate section such as `Codex 보완 메모` or `Codex 제안` so the added content is visibly distinguishable from the user's original writing. +- Avoid silently rewriting or blending Codex-authored guidance into the user's original bullet lists unless the user explicitly asks for a rewrite. ### Game Concept - **Genre**: Online multiplayer co-op action RPG (3rd person)