グカネータ公開 (#361) (#368)

Reviewed-on: #368
Co-authored-by: miteruzo <miteruzo@naver.com>
Co-committed-by: miteruzo <miteruzo@naver.com>

AGENTS.md

@@ -158,6 +158,13 @@ npm run preview
 - Keep page-level code under `frontend/src/pages` and shared UI/feature code
   under `frontend/src/components` unless existing patterns point elsewhere.
 - Match existing Tailwind, component, and import alias conventions.
+- In TypeScript and TSX, prefer direct comparison operators such as `===` and
+  `!==` over negating a comparison like `!(a === b)`.
+- In TypeScript and TSX, prefer `++i` or `--i` over `i += 1` or `i -= 1` for
+  simple unit-step counter updates.
+- For user-facing Japanese text, prefer modern kana usage and natural current
+  phrasing over historical spellings or awkward literal wording.
+- For user-facing Japanese ellipses, prefer `……` over ASCII `...`.
 
 ### Frontend TSX style
 
@@ -179,6 +186,9 @@ npm run preview
   single physical line.
 - Always add braces around `if`, `else`, or `for` bodies when the body spans
   two or more physical lines, even if it is one statement.
+- Do not use a leading semicolon for expression statements such as
+  `;([...]).forEach(...)`; rewrite the expression to avoid ASI hazards
+  explicitly, for example with `void`.
 
 Preferred: