応募先と面接形式に合わせ、実体験を回答用のエピソードに整理します。企業調査、想定質問、自己紹介や逆質問の準備から面接後の振り返りまで支援します。
- 面接直前に回答の要点を準備したいとき
- 実体験を面接用の話に整理したいとき
- 企業研究と逆質問を準備したいとき
Web・モバイルの翻訳カタログにある未訳項目を埋め、同期や欠落チェックで全ロケールの充足を確かめるスキルです。
Fill missing Reactive Resume translations across all configured web and mobile locales using parallel subagents, then prove catalog completeness. Use for “fill translations”, “complete translations”, missing locale strings, or a request to ensure translations are complete before release. Cover existing gaps unrelated to the current task unless the user explicitly narrows scope. Do not activate for ordinary prose translation or a read-only audit that forbids edits.
実行スコア 未検証
インストール方法を見るReactive ResumeのWeb版とモバイル版にある翻訳カタログを調べ、未訳の項目を埋めます。設定ファイルから対象ロケールを確認し、既存の訳文を保ちながら、Web版の翻訳後にモバイル版へ反映して残りを補う手順です。翻訳作業の後は、カタログが現在のソースと同期しているか、フォールバックに頼らず未訳項目が残っていないかを確認します。プレースホルダーやメッセージ構造、用語も確認対象です。
リリース前に複数ロケールの翻訳漏れを解消したいときや、現在の機能変更とは無関係な古い未訳項目も含めてカタログ全体を整えたいときに向いています。翻訳と技術的なカタログ検証をまとめて進められます。
通常の文章翻訳や、編集を禁止した読み取り専用の監査には使いません。プロジェクトのチェックアウト内で実行し、既存の依存関係とパッケージスクリプトを使います。翻訳サービスや新しい依存関係は不要です。
この紹介文は、公開されている SKILL.md をもとに AI(OpenAI Codex)が作成しました。正確な仕様は下の原文を確認してください。
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Finish every active catalog entry, including older gaps outside the current feature. Preserve existing translations and unrelated work. Technical completeness and linguistic quality are separate claims.
Run from the Reactive Resume checkout root. Follow its AGENTS.md, command wrappers, and current package scripts. Commands below match its Lingui 6 workflow; inspect installed --help if flags change. Use existing dependencies; no translation service or new dependency is required.
Read GLOSSARY.md, both apps' lingui.config.ts, relevant package scripts, and apps/mobile/scripts/seed-locales.mjs. Derive locales, source locale, and pseudo-locale from current config rather than a fixed locale count. Currently zu-ZA is a generated pseudo-locale, not Zulu translation work.
Capture git status --short and the initial diff. Save copies of catalog bytes outside the checkout so preservation checks compare against current work, not HEAD. Record pre-existing compiled locale files too. Keep staged/unstaged changes intact; no reset, checkout, clean, commit, push, or release unless separately requested.
Extract all source strings in both apps, sequentially, before dispatching workers:
pnpm --filter web lingui:extract
pnpm --filter mobile lingui:extract
The root lingui:extract currently covers web only. Web's script cleans obsolete entries and overwrites the source locale from source messages; mobile's script also seeds empty entries from web. These extraction changes are expected. Compare preservation of active nonempty target translations against the post-extraction baseline.
Run both missing checks, capturing each exit code and verbose findings even when one fails:
pnpm --filter web exec lingui check missing --mode catalog --verbose
pnpm --filter mobile exec lingui check missing --mode catalog --verbose
Inventory all missing entries by app and locale. Use installed @lingui/format-po through the owning workspace for structured inventory/edits; empty-line regexes misread multiline messages, headers, contexts, and obsolete entries. Keep msgid, context, translator comments, and source references with each work item. If no entries are missing, continue to verification without spawning translation workers.
Complete web first, seed mobile again, then translate only remaining mobile gaps. This reuses shared strings and avoids duplicate or inconsistent work.
Assign disjoint whole locale files to workers. Keep a small bounded pool within available concurrency; balance by missing-entry count, group related locales where useful, and refill slots as workers finish. Never assign two writers to the same file, even for different messages. Give workers only missing messages plus relevant existing examples and source context instead of whole catalogs when possible.
Use the environment's delegated-task tools. In T3 Code, inspect orchestrator_capabilities and use delegate_task when inherited model options require it; preserve the current provider/model/options unless the user requests another selection. Use shared-checkout tasks for disjoint files: worktrees start from committed state and can omit current uncommitted source/catalog changes. Use native subagents where supported and appropriate. If delegation is unavailable, complete the same inventory sequentially and disclose that limitation. Do not create ordinary top-level conversations.
Give each worker this brief, substituting exact paths and entries:
Fill only empty active target translations in these owned files: [paths]. Work from this post-extraction inventory: [entries/counts]. Read
GLOSSARY.md, existing locale terminology, comments, and referenced UI when meaning is ambiguous. Translate natural interface language for each locale. Preserve IDs, contexts, source messages, existing nonempty translations, headers, references, and unrelated edits. Preserve named placeholders, ICU variable names/types, select keys, exact-number branches,otherbranches, plural#, numbered rich-text tag indexes/pairing, literal URLs/config identifiers, and brands. Adapt plural categories to the target language. Keep tags attached to their corresponding meaning when word order changes. Use the installed PO parser/serializer; review round-trip diffs. English copying is acceptable only for genuine shared words, brands, and literals, never to conceal a gap. You own translation edits only: no extraction, seeding, global formatting, compilation, commits, or cleanup. Other workers share this checkout. Return paths, filled counts, unresolved IDs, uncertainties, and checks actually run. Finish every assigned entry or identify the blocker; do not claim global completion.
The parent tracks completion against the inventory, reviews returned diffs/counts, and resolves failures. Worker summaries alone are insufficient evidence. Retry only failed files/entries; do not rerun successful batches.
After every web worker finishes, seed once from the parent:
pnpm --filter mobile exec node scripts/seed-locales.mjs
pnpm --filter mobile exec lingui check missing --mode catalog --verbose
Partition remaining mobile gaps into disjoint files and apply the same workflow. Existing nonempty mobile translations remain authoritative. Finish all workers before shared commands run.
First compare parsed catalog changes with the post-extraction baseline: active IDs/contexts/source messages stay intact, existing nonempty target translations stay intact, and only missing translations are filled. Review newly added messages against original source. Compare placeholder and numbered-tag structure for every filled entry using parsed ICU/message structure, not brace regexes. Inspect installed Lingui parser utilities before using them; locale plural categories may legitimately differ. A syntactically valid message can still omit a variable, so compilation alone is insufficient. Review glossary-sensitive wording and suspicious source-identical translations.
Run every gate below and record each result. These commands are for the whole catalog, not changed locales or changed source files:
pnpm --filter web exec lingui check sync --clean --overwrite
pnpm --filter mobile exec lingui check sync --clean
pnpm --filter web exec lingui check missing --mode catalog --verbose
pnpm --filter mobile exec lingui check missing --mode catalog --verbose
pnpm --filter web exec lingui compile --strict
pnpm --filter mobile exec lingui compile --strict
pnpm pdf:translations
pnpm --filter @reactive-resume/tooling test locales/section-titles.test.ts
pnpm lint:agent
pnpm format:check
git diff --check
check sync proves catalogs reflect current source; an old but fully filled catalog is insufficient. --mode catalog proves each target catalog is filled before fallback. Default missing checks and compile --strict allow fallback and cannot replace it. Compilation adds ICU syntax/bundle validation. The tooling test must actually execute its tests; zero tests is not proof.
Compilation writes locale .js files. Before compiling, back up existing output bytes and record absent output paths. After checking, restore pre-existing outputs to those exact bytes and remove only files created by this invocation. Preserve outputs that were already untracked. If another process changes an output during verification, preserve its change and report the conflict instead of overwriting it. Retain generated PDF section-title and Present-label changes, since those are maintained artifacts. Inspect final status/diff against the initial baseline.
If synchronization fails, inspect source drift and re-extract from the parent after workers finish, seed again, translate new gaps, and repeat affected gates. If missing checks fail, continue filling. Repair translation-introduced syntax/placeholder errors. Report unrelated pre-existing failures separately; do not change lint policy, fallback config, source strings, or locale lists to manufacture a pass. Never pipe away exit codes or treat a partial, timed-out, or unrun check as passing.
Stop when all configured web and mobile catalogs are synchronized, all catalog-mode missing checks return zero, changed messages preserve their runtime structure, strict compilation and derived-artifact checks pass, and unrelated work remains intact. If a blocker prevents this, report exact outstanding app/locale/message counts and failed or unrun gates; do not claim completion.
Keep the handoff short: entries filled by app and locale count; final missing counts; commands/checks that passed or failed; unresolved linguistic uncertainty. State whether native-language review occurred. Mention parallelism only if workers actually ran. A clean catalog proves technical completeness, not native-language quality, browser/native behavior, deployment, or release readiness. Leave changes uncommitted unless asked otherwise.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
応募先と面接形式に合わせ、実体験を回答用のエピソードに整理します。企業調査、想定質問、自己紹介や逆質問の準備から面接後の振り返りまで支援します。
求人の保存から応募・面接・内定までの進捗と提出書類を記録し、次の行動や連絡期限を整理します。週次の振り返りや、お礼・状況確認などの文面作成にも対応します。
求人内容に合わせた模擬面接を行い、一問ずつ回答を掘り下げます。面接形式や難易度を選び、回答の引用を根拠にした採点と具体的な改善点を受け取れます。
内定条件の基本給・賞与・株式報酬を分けて比較し、根拠のある希望条件を整理します。条件交渉のメールや通話台本、練習、承諾・辞退の文面まで支援します。
職歴や学歴を会話で集め、Reactive Resumeに取り込める履歴書のJSONを作成します。不足情報を確認し、テンプレートや用紙、項目の配置も整えます。
履歴書や職務経歴書の業務説明を、実際の貢献や成果が伝わる短い箇条書きに整えます。質問で経験を掘り下げ、数値がない仕事も担当範囲や具体的な変化で表現します。