#399

AGENTS.md

@@ -410,6 +410,20 @@ Good:
 - For user-facing Japanese kanji spelling, do not normalize to
   《当用漢字による書きかえ》; prefer original forms such as `編輯`.
 - For user-facing Japanese ellipses, prefer `……` over ASCII `...`.
+- Frontend dialogue work must use `@/lib/dialogues/useDialogue` as the
+  feature-facing entrypoint.
+- Reuse the existing common dialogue API and common dialogue component
+  instead of building feature-local overlay, close button, header, footer,
+  focus handling, outside click handling, Escape handling, or confirmation
+  flows.
+- Do not import `@/components/ui/dialog` directly in feature code to build a
+  one-off dialogue, and do not evade this rule with aliases such as
+  `Dialog as Dialogue`.
+- Keep business-specific form content in feature code, and keep the visual
+  and behavioural dialogue shell in common code.
+- Use British spelling `Dialogue` for project-defined dialogue identifiers.
+  Keep an exact third-party API spelling only at the external boundary where
+  compatibility requires it.
 
 ### Frontend TypeScript and TSX style