Project General Translation & Terminology Guidelines

Documentation Community

Skill notes

Phase 2: Structural Translation & Anti-Pattern Detection

LLMs naturally tend to follow the grammatical structure of the source text. Chinese technical writing often uses sprawling sentences and explanatory fillers. You must actively break these patterns.

🚫 Rule 6: Anti-Summarization (Strict Boolean & Causality Preservation)

Trigger: When applying Conceptual Compression (Rule 5) to a text block containing conditionals or explanations. The Core Conflict: Compression reduces word count by using jargon. Summarization drops critical logic. Summarization is strictly forbidden. Execution (The Boolean Mapping Rule): Treat Chinese comments like code blocks. Extract all IF/THEN/ELSE branches, prerequisites, and root causes before translating.

Phase 3: The Hardcoded Terminology Dictionary

CRITICAL: When translating, if you encounter these Chinese concepts, you MUST use the exact, first provided English term. Do not mix or alternate synonyms.

Phase 4: Strict Formatting Rules (CRITICAL)

When translating comments inside code files (.cpp, .h) or configs (.ini), apply these hard constraints: Bilingual Retention: Unless explicitly instructed to delete Chinese, ALWAYS retain the original Chinese comments. Bottom Placement: Place the English translation immediately below the Chinese line or block. Block Uniformity: Do NOT translate line-by-line (ZH-EN-ZH-EN). If a Chinese comment is a 3-line block, output it as a 3-line Chinese block followed by a 3-line English block.

Phase 5: The Post-Translation Verification Workflow (DO NOT SKIP)

If you are asked to review or update translations in a long file, you cannot rely solely on passive reading. You MUST execute this workflow: Active Scan (Regex/Search): Before reading the document, use file search tools to actively scan for known anti-patterns in the current English text (e.g., search for Screen tearing, Merged write, Replies, Source station). Fix them immediately. Format Review: Scan for ZH-EN-ZH-EN interleaving and fix it to block format.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ZLMediaKit · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 2: Structural Translation & Anti-Pattern Detection

LLMs naturally tend to follow the grammatical structure of the source text. Chinese technical writing often uses sprawling sentences and explanatory fillers. You must actively break these patterns.

02
Phase 3: The Hardcoded Terminology Dictionary

CRITICAL: When translating, if you encounter these Chinese concepts, you MUST use the exact, first provided English term. Do not mix or alternate synonyms.

03
Phase 4: Strict Formatting Rules (CRITICAL)

When translating comments inside code files (`.cpp`, `.h`) or configs (`.ini`), apply these hard constraints: Bilingual Retention: Unless explicitly instructed to delete Chinese, ALWAYS retain the original Chinese comments. Bottom Placement: Place the English translation immediately below the Chinese line or block. Block Uniformity: Do NOT translate line-by-line (`ZH-EN-ZH-EN`). If a Chinese comment is a 3-line block, output it as a 3-line Chinese block followed by a 3-line English block.

04
Phase 5: The Post-Translation Verification Workflow (DO NOT SKIP)

If you are asked to review or update translations in a long file, you cannot rely solely on passive reading. You MUST execute this workflow: Active Scan (Regex/Search): Before reading the document, use file search tools to actively scan for known anti-patterns in the current English text (e.g., search for `Screen tearing`, `Merged write`, `Replies`, `Source station`). Fix them immediately. Format Review: Scan for `ZH-EN-ZH-EN` interleaving and fix it to block format.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.