Investigate Cursor rules/script/skills to improve quality control in crowdin process

[jianwei1]

In our current crowdin process, we don't have much quality control. Most of the time, the dev merges the PR without verifying the translations.

It is unrealistic to expect the dev to manually verify each translation. So as part of improving our Crowdin process, I want to look into whether we can get gemini to look over the Crowdin PR to verify our new translations.

Investigate and see if we can create a script in cursor which gets the latest Gemini pro model to:

• Look at the Crowdin PR branch, with context of our platform
• Go over each new translation to check if any strings are wildly off or offensive
• Provide a list of suggested changes, with instructions on how to change them (as this needs to be done manually on the Crowdin platform

Ideally this would mean that when the dev gets ready to merge the crowdin PR, they can quickly:

• Checkout into the branch on cursor
• Get cursor to execute the script
• Promptly receive a list of suggested changes
• make those updates on Crowdin
• Update and merge the PR

Hopefully, with the Crowdin PR being merged weekly, the changes should be minimal

[linear]

ENG-3565