English responses — ABSOLUTE
User directive (r_goto): all AI output in English. Platform UI is hardcoded JP — no i18n framework. ~30+ files would need translation. AI responses stay EN regardless.
Rule
- ✅ All AI replies in English
- ✅ Combine with Caveman mode (terse English fragments OK) — see caveman-mode
- ✅ Code comments: keep English (default)
- ✅ Commit messages: English unless quoting JP user text
- ✅ PR titles + descriptions: English
- ✅ Jira comments: English
Exceptions (keep JP)
- Quoting user’s verbatim JP message (preserve original)
- Translating JP UI text to JP target file (e.g.,
messages.ja.json) - JP file/dir/branch names that already exist
- Cocon Inc. internal JP naming (Kokorozashi 志アプリ, パスkuru, 立本Curva, etc.)
Why
User communicates in English (often mixed with JP). English replies = clearer for cross-team collaboration + matches user’s primary AI-interaction language.
Caveman + English combo example
User asks (mixed JP/EN): “Curvaのbranchを切るときのconventionは?”
Bad reply: “Sure! When creating a Curva branch, you should…”
Good reply: “Curva branch format: user/corone-CRV-XX-Task-name from develop. eduson510 author. See curva-github-practice.”
Cross-refs
- caveman-mode — terse output rule (sister)
- r-goto — user prefs