메뉴
Use when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere. Surfaces the extract workflow and footguns so the change does not fail the i18n CI check or ship an untranslated or inconsistent string.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use to open a fresh Claude session in a new terminal tab for a da-dev worktree, after `scripts/da-bootstrap.mjs` prints its READY block. Covers Warp, Windows Terminal, and a manual fallback.
Use when an extension change needs agentic verification in a real browser — content scripts, popup UI, network calls, fonts, console errors. Spawns the agent's own Chrome via the chrome-devtools-ext MCP. Complements (does not replace) human-eye verification via `pnpm dev:browser`.
Use to monitor an open PR for AI/bot review comments, evaluate them critically, push fixes for real issues, and resolve threads — capped at a sensible duration so it self-terminates. Invoke as "babysit PR
Use when about to write or modify a Playwright e2e spec under `packages/danmaku-anywhere/e2e/`. Points at the canonical doctrine and surfaces the load-bearing rules so the spec doesn't get bounced in review.
Use when you need to load a specific published preview/nightly extension build into the agent's MCP browser by run-number, branch name, or tag. Faster than rebuilding locally when you only want to exercise an existing artifact.
Use when evaluating review comments from AI reviewers (gemini-code-assist, copilot-pull-request-reviewer) on a PR. Default to assuming the reviewer is right; verify before declining. Includes reporting in chat and resolving threads after handling.
| name | i18n |
| description | Use when adding or changing user-facing strings in the extension (i18n.t calls or locale JSON) under packages/danmaku-anywhere. Surfaces the extract workflow and footguns so the change does not fail the i18n CI check or ship an untranslated or inconsistent string. |
Workflow for translation changes in packages/danmaku-anywhere. The package AGENTS.md "Gotchas" has the short version; this is the checklist.
The committed locale JSON (src/common/localization/locales/{en,zh}/translation.json) is the source of truth. i18next-cli extract seeds new keys and owns sorting and pruning, but it never overwrites an existing value, so changing copy means editing the JSON directly. CI runs extract --ci (pnpm i18n:check) and fails when the committed JSON does not match what extraction produces (missing key, unsorted, unused key).
New string is added via i18n.t with a literal key and an English default, then registered with extract:
i18n.t('infoPanel.state.idle', 'No danmaku mounted')
cd packages/danmaku-anywhere && pnpm i18n extract
Extract adds the key to en (from your default) and zh, sorted. Then translate the new zh entry in the JSON.
Changing existing English copy means editing en/translation.json directly. Extract does not pick up a changed default on an already-extracted key, so the i18n.t default and the JSON drift unless you edit the JSON.
Translating or editing zh means editing zh/translation.json directly (extract preserves existing values, it does not translate).
Keys must be static string literals so the extractor finds them: no template strings, computed keys, or runtime concatenation. For per-state or per-enum strings, enumerate them as literal keys in a lookup (see panelView.ts / entryView.ts, the "Literal i18n keys per state" pattern).
Validate with pnpm i18n:check (the same extract --ci CI runs). Must be clean before committing.
en string or a zh translation lives in the JSON, not in the i18n.t call; editing only the source default leaves the JSON (and the UI) unchanged.zh. Use a period, comma, colon, or parentheses. This is a repo-wide rule.zh vocabulary. Known glossary: "mount" is 装填 (已装填, 装填弹幕), not 加载 or 挂载. Grep the zh JSON for an existing term before coining a new one.i18n:check validates key sets, not translation quality. It will not catch a zh entry left in English or an en default that drifted from the JSON. That is on you.