Use this skill when the user wants translation data for medicine, law, finance, engineering, policy, or other specialist text where the exact term matters more than a loose paraphrase. Trigger it for requests like "test whether it knows the field jargon," "make the translation use the proper technical term," or "check that it can do domain copy, not just everyday language translation."
[Case 1]
To synthesize data for this capability, you must strictly follow a 3-phase pipeline. Do not hallucinate steps. Read the corresponding reference file for each phase sequentially:
Phase 1: Environment Exploration
Read the exploration guidelines to discover raw knowledge seeds:
references/EXPLORATION.md
Phase 2: Trajectory Selection
Once Phase 1 is complete, read the selection criteria to evaluate the trajectory:
references/SELECTION.md
Phase 3: Data Synthesis
Once a trajectory passes Phase 2, read the synthesis instructions to generate the final data:
references/SYNTHESIS.md