القائمة
Use this skill when you need to update the localization of the PWA app (wetty-chat-mobile)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | localization |
| description | Use this skill when you need to update the localization of the PWA app (wetty-chat-mobile) |
First you should extract anything that needs to be translated by using
the following command in wetty-chat-mobile directory
npm run lingui:extract
Then you should examine translation files in locales/<language>/messages.po
msgstr "" would indicate an item is missing translation
If a string got commented out after running extract that's likely because it is not used any more. It is a good idea to remove it.
Fill in the missing translation with appropiate adaptation for the target language.
Performs a maintainability-focused code review on code that is already functionally correct. Use this skill when the user asks to review code for maintainability, readability, or code quality — not for bugs or functionality.
Triage bugs in the wetty-chat Flutter application. Use this skill whenever the user reports a Flutter app bug, describes unexpected mobile or desktop UI behavior, mentions something broken or not working in `wetty-chat-flutter`, or asks to investigate a frontend issue in the Flutter client. This includes startup and auth problems, navigation and deep-link issues, chat list or conversation timeline regressions, Riverpod state bugs, WebSocket or push notification problems, media or voice-message failures, cache or persistence issues, and performance regressions. Even if the backend may be involved, start here when the symptom is observed in the Flutter app.
Triage frontend bugs in the wetty-chat-mobile React application. Use this skill whenever the user reports a bug, describes unexpected UI behavior, mentions something broken or not working, or asks to investigate a frontend issue. This includes visual glitches, state management problems, WebSocket/real-time issues, API errors surfacing in the UI, broken navigation, notification bugs, and performance regressions. Even if the root cause might be in the backend, start here if the symptom is observed in the frontend.