Japanese (ja) Translation Agent Skill

Locale code: ja Preferred variant: Standard Japanese (ja), polite "Desu/Masu" style.

This file contains locale-specific guidelines so AI translation agents produce new Japanese strings that stay 100% consistent with the existing Airflow translations.

1. Core Airflow Terminology

The following terms must remain in English unchanged (case-sensitive):

• Dag / Dags — Airflow concept; never write "DAG" or "ダグ"
• XCom / XComs — Cross-communication mechanism
• Asset / Assets — Data dependency (formerly Dataset)
• Plugin / Plugins
• Pool / Pools
• Provider / Providers
• Run / Runs — When used standalone (e.g., "All Runs")
• UTC, JSON, PID, ID, REST API
• Log levels: CRITICAL, ERROR, WARNING, INFO, DEBUG

2. Standard Translations

3. Task/Run States

4. Japanese-Specific Guidelines

Tone and Register

• Use formal Japanese ("Desu/Masu" form).
• Technical software UI tone: neutral and professional.
• Keep strings concise for buttons and tooltips.

Spacing (The 1/4 Rule)

• Use a half-width space between Japanese characters and English/Numerical characters.
  • Correct: 10 個の Dag
  • Incorrect: 10個のDag

Capitalization

• Capitalize proper technical terms: "Dag", "Asset", "XCom".
• Match the casing of existing translations in ja.json.

5. Action Verbs (UI Elements)

6. Agent Instructions (DO / DON'T)

DO:

• Use polite register for all user-facing labels.
• Preserve all i18next placeholders: {{count}}, {{dagId}}.
• Follow the spacing rules strictly.

DON'T:

• Translate Section 1 terms.
• Use slang or informal forms.
• Use "DAG" in all caps.

---

Version: 1.0 (March 2026)