ECShopX_mobile-frontend

按 GitLab TBID 强制校验规范提交 Git 变更并在对话中总结。提交信息必须以 [TBID:项目ID-任务编号] 开头。用户说「提交」「提交并总结」「帮我 commit」时使用；不写 .cursor/commit-summary 文件。

按用户指定目录扫描并翻译页面标题（navigationBarTitleText、SpPage title、setNavigationBarTitle）。用户说「翻译页面 title」「目录下 title 没翻译」「i18n page title」时触发。

按计划文件顺序逐文件完成 i18n（哈希键 + @/i18n 的 $t/ti，禁止页面使用 globalThis.$t），维护 subpages/i18n/locales 三语，并在对应 plan 中更新进度与统计。用户说「按计划做 i18n」「继续翻译 plans」时触发。

Summarize current code changes and optionally commit. Use when the user asks to summarize what changed, record changes, commit with a message, or "总结这次改了什么并提交"/"帮我 commit".

Use when analyzing a frontend codebase, onboarding into an existing project, or documenting stack, structure, configs, and coding conventions into .f2e-ai/handbook/.

Use when a requirement-id is ready for delivery and the next step is to summarize Git changes, write change-summary.md, commit, push, and prepare a PR.

Use when a requirement-id already has test.spec.ts and the next step is to run Playwright and persist the results in test-result.md.

Use when a confirmed requirement-id already has plan.md and the next step is to implement that plan in project code without expanding scope.

Use when a confirmed requirement-id has changed files that contain Chinese text and the project requires i18n replacement plus locale updates.

Use when a new requirement, bug, task id, Figma link, or API reference needs to be clarified and converted into structured artifacts under .f2e-ai/requirements/<id>/.

Use when a confirmed requirement-id needs test-first planning, explicit user confirmation, and a detailed implementation plan written into test.spec.ts and plan.md.