feat: 新增追问模式和iOS本地化,重构后端输出模型
This commit is contained in:
+5
-5
@@ -65,12 +65,12 @@ appBar: AppBar(
|
||||
|
||||
- When a repeated pattern emerges, extract a reusable component into `shared/widgets/` instead of building `AppBar` independently in each page.
|
||||
|
||||
## Divination Terminology (Must)
|
||||
## Divination Terminology
|
||||
|
||||
- Divination domain terminology must use fixed Chinese terms in code contracts, protocol fields, and UI semantic labels.
|
||||
- Do not localize or translate canonical terms such as: 六爻、爻、动爻、静爻、六亲、六神、世爻、应爻、伏神、月建、日辰、月破、日冲、空亡、五行旺衰。
|
||||
- Signature level labels (`上上签/中上签/中下签`) may be localized for UI display only, while protocol/storage values remain canonical Chinese.
|
||||
- l10n can translate explanatory copy, but must not alter canonical divination terminology semantics.
|
||||
- Protocol/storage values and backend field names remain canonical Chinese (e.g. 官鬼, 妻财, 世, 应).
|
||||
- Frontend hexagram detail MUST localize for English users: translate section headers, five-element labels, status values, and provide a legend mapping Chinese symbols to English equivalents.
|
||||
- Yao row cells keep Chinese characters (compact display); a legend card above the rows provides English translations.
|
||||
- AI English output uses Chinese parenthetical notes for key Liu Yao terms (e.g. "Officer (官鬼) line") so users can cross-reference with the Chinese characters shown in the hexagram detail.
|
||||
|
||||
## Localization Generation Rules (Must)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user