From 13d1949dede3b8f0da90429659e81e0843687492 Mon Sep 17 00:00:00 2001 From: dal4segno Date: Thu, 26 Mar 2026 16:43:37 +0900 Subject: [PATCH] =?UTF-8?q?chore:=20=ED=94=84=EB=A1=9C=ED=86=A0=ED=83=80?= =?UTF-8?q?=EC=9E=85=20=EC=B2=B4=ED=81=AC=EB=A6=AC=EC=8A=A4=ED=8A=B8=20?= =?UTF-8?q?=EA=B8=B0=EB=B3=B8=20=EA=B7=9C=EC=B9=99=20=EC=B6=94=EA=B0=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- AGENTS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 24ab4e44..03a6851b 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. +- Unless the user explicitly names another file, `체크리스트` means `\\Truenas\smb\Obsidian Vault\Colosseum\개발\프로토타입 체크리스트.md`. +- After completing work, always check whether the prototype checklist should be updated and reflect the new status when needed. +- If the work also changes a domain-specific checklist such as boss/player/combat, sync that checklist too. - 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.