Skip to content

AGENTS.md

Latest commit

 

History

History
25 lines (20 loc) · 1.49 KB

AGENTS.md

File metadata and controls

25 lines (20 loc) · 1.49 KB

Repository Instructions

Yomitan Edit Workflow

  • Do not edit built/compiled files under GSM_Overlay/yomitan/ directly.
  • For Yomitan logic changes, edit source files in C:\Users\Beangate\GSM\yomitan-gsm\ext\ (for example: ext/js/language/text-scanner.js).
  • After source edits, rebuild and sync the overlay copy by running:
    • C:\Users\Beangate\GSM\yomitan-gsm\local-build-chrome-overlay.ps1

pytest

  • Always use .venv for running pytest to ensure dependencies are correctly managed.
  • If possible, make tests first, making sure they fail before implementing functionality, and then iterate on your solution until tests pass.
  • Increment coverage where possible.

Ruff

  • Always run Ruff after Python changes.
  • Use uv run ruff format GameSentenceMiner tests scripts from the repo root.

Localization (i18n)

  • All user-facing strings in Electron renderer components must use t("key") from useTranslation(). Never hardcode English text in JSX.
  • Locale files live in electron-src/renderer/src/i18n/ (en.json, ja.json, ukr.json).
  • When adding new UI text, add the key to en.json first, then add translations to ja.json and ukr.json.
  • Use {variable} interpolation for dynamic values: t("key", { name: value }).
  • For module-scope constants (outside React components), store i18n key strings in a labelKey field or key-map object, then translate at render time with t(item.labelKey).
  • See docs/LOCALIZATION.md for the full guide, key naming conventions, and code patterns.