특정 채용 공고와 면접 형식에 맞춰 실제 경험을 답변용 이야기로 정리합니다. 출처가 있는 회사·직무 자료와 예상 질문, 자기소개를 준비하고 면접 후 복기까지 도와 다음 전형에 연결합니다.
- 면접 직전에 답변 요점 준비
- 실제 경험을 면접 이야기로 정리
- 회사 조사와 역질문 준비
Reactive Resume의 웹과 모바일 언어 카탈로그에서 누락된 번역을 채우고 기존 번역을 보존합니다. 이후 각 카탈로그가 현재 원문과 동기화되었는지, 미번역 항목이 남았는지 확인합니다.
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의 웹 및 모바일 앱 번역 카탈로그를 살펴보고 번역이 없는 항목을 채웁니다. 설정 파일에서 대상 언어를 확인하고 기존 번역을 유지하면서 웹 카탈로그를 먼저 번역한 뒤 모바일 카탈로그에 반영하고 남은 항목을 보완합니다. 작업 후에는 카탈로그가 현재 원문과 동기화되어 있는지, 대체 문구에 의존하지 않고도 미번역 항목이 남아 있는지 확인합니다. 자리표시자, 메시지 구조, 용어도 검사합니다.
출시 전에 여러 언어의 번역 누락을 해결하고 싶을 때 사용할 수 있습니다. 현재 기능 변경과 관계없는 오래된 누락 항목까지 포함해 카탈로그 전체를 정리하고, 번역과 기술 검증을 함께 진행할 때도 적합합니다.
일반 문장 번역이나 편집을 금지한 읽기 전용 점검에는 사용하지 않습니다. 프로젝트 체크아웃 안에서 실행하며 기존 의존성과 패키지 스크립트를 사용합니다. 번역 서비스나 새 의존성은 필요하지 않습니다.
이 소개문은 공개된 SKILL.md를 바탕으로 AI(OpenAI Codex)가 작성했습니다. 정확한 사양은 아래 원문을 확인하세요.
AI가 SKILL.md의 내용에서 주의가 필요한 작업과 도입 전제를 확인했습니다. 점수는 실제로 실행한 결과(실행 검증)만으로 매깁니다.
점수에는 넣지 않았습니다. 2026년 10월 25일 기준으로 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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
특정 채용 공고와 면접 형식에 맞춰 실제 경험을 답변용 이야기로 정리합니다. 출처가 있는 회사·직무 자료와 예상 질문, 자기소개를 준비하고 면접 후 복기까지 도와 다음 전형에 연결합니다.
Track job opportunities, application stages, interview dates, and the exact documents submitted. Organize follow-ups, review progress each week, and draft recruiter replies, referral requests, thank-you notes, or withdrawal messages for the user to send.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
특정 채용 공고에 맞춰 면접을 연습하고 형식과 난이도를 선택할 수 있습니다. 한 번에 한 질문에 답하고 후속 질문을 받으며, 답변에서 인용한 근거에 따른 점수와 개선 제안을 얻습니다.
기본급, 조건부 보너스와 추정 주식 보상을 구분해 채용 제안을 비교하고 근거 있는 협상안을 정리합니다. 이메일과 통화 대본 작성, 채용 담당자와의 연습, 답변 기한 연장, 수락 또는 거절 문안 준비를 지원합니다.
대화를 통해 경력, 학력, 기술 정보를 모아 Reactive Resume에 가져올 수 있는 이력서 JSON을 만듭니다. 누락된 사실을 확인하고 템플릿, A4 또는 Letter 용지, 항목과 순서를 지정할 수 있습니다.
이력서와 경력기술서의 업무 설명을 실제 기여가 드러나는 간결한 항목으로 정리합니다. 질문으로 성과와 담당 범위를 확인하고, 신뢰할 수 있는 수치가 없을 때는 업무 규모나 구체적인 변화를 표현합니다.