diff --git a/AGENTS.md b/AGENTS.md
index db88b221..89a1e5a6 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -330,7 +330,9 @@ public class NetworkedComponent : NetworkBehaviour
 - After Unity-related edits, refresh or compile as needed and check the Unity console before proceeding.
 - For networked play tests, prefer a temporary non-conflicting test port when needed and restore the default port after validation.
 - The user has a strong project preference that play mode must be stopped before edits because network ports can remain occupied otherwise.
-- Commit messages should follow the recent project history style: use a type prefix such as `feat:` or `fix:` and describe the actual gameplay/UI/system change in Korean with enough detail to understand the scope from the log alone.
+- Commit messages should follow the recent project history style: use a type prefix such as `feat:`, `fix:`, or `chore:` and write the subject in Korean so the gameplay/UI/system change is clear from the log alone.
+- When the change is substantial, include a blank line after the subject and add Korean bullet points that summarize the work by feature/purpose, similar to commit `0889bb0` (`feat: 드로그 집행 개시 패턴 및 낙인 디버프 추가`).
+- Prefer the format `type: 한글 요약` for the subject, then `- 변경 사항` bullet lines for the body. Use `feat:` for feature work, `fix:` for bug fixes, and `chore:` for non-feature maintenance such as scene/prefab cleanup, asset reorganization, or other miscellaneous upkeep. The body should mention key implementation scope, affected systems/assets, and validation or rollback notes when relevant.
 - All code comments and documentation should be in Korean
 - Use `[Min()]` attribute for numeric minimums in Inspector
 - Use `[TextArea]` for multi-line string fields