菜单
Guide daily Lingui command workflow for Next.js and React projects. Use when teams need clear extract/translate/compile/manifest routines, troubleshooting steps, and command semantics for i18n catalogs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate emoji-prefixed Conventional Commit messages and focused local commits from staged changes or a single clear unstaged change.
Commit a focused local change set with an emoji Conventional Commit message, safely stage a clear unstaged scope when needed, then push the current branch to its remote. Use when the user asks to "commit and push", "commit push", "submit and push", "push my committed change", or wants a local commit finalized on the remote. Do not create pull requests, merge requests, releases, tags, rebases, or deployment changes.
Use this skill when the user wants to decide, set, write, or use a durable coding-agent goal or /goal prompt that keeps Codex, Claude Code, or another agent working until a verifiable done condition is met. It gates autonomy, handles runtime differences, and writes copy-ready goal contracts with outcome, verification, constraints, write boundaries, iteration policy, completion evidence, and pause/ask conditions. Trigger on requests like 'should I set a goal?', 'set up a durable goal', 'give me a /goal prompt', 'turn this vague app idea into a goal', 'keep refactoring until tests pass', 'I am stepping away, have the agent finish this', migrations, refactors, ports, spec implementations, eval loops, backlog cleanup, or multi-checkpoint work. Do not use for single quick edits, running tests once, OKR/scrum goal questions, recurring reminders, or token-budget settings.
Create safe Git feature or hotfix branches with concise names. Use this whenever the user asks to create a branch, start work on a new feature or fix, wants a `feat/...` or `hotfix/...` branch name, asks for a short branch slug from a task description, or wants help before beginning local Git work. Default to recommending the branch name and command first, then create only after user confirmation. Do not push, commit, rebase, or create PRs.
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.
| name | lingui-workflow |
| description | Guide daily Lingui command workflow for Next.js and React projects. Use when teams need clear extract/translate/compile/manifest routines, troubleshooting steps, and command semantics for i18n catalogs. |
| metadata | {"author":"adonis"} |
当此 skill 被激活时，先输出以下命令速查表，再回应用户问题：
| 命令 | 作用摘要 | 可用参数 |
| ----------------- | ---------------------------------------------- | ------------------------------------------------- |
| i18n:extract | 提取源码文案到 po | — |
| i18n:translate | 统计缺失翻译 | --fill-source, --strict |
| i18n:check | 严格翻译检查，缺失即报错退出 | — |
| i18n:compile | 编译 po → mjs，自动执行 i18n:manifest | — |
| i18n:manifest | 基于已有 mjs 生成 catalog-manifest.ts | — |
| i18n:sync | 当前仅等价 i18n:extract | — |
| i18n:bootstrap | 一次执行 extract + compile(+manifest) | — |
| i18n | 组合入口；默认 extract + translate | --compile, --fill-source, --no-translate, --strict |
这个 skill 面向“已经完成 Lingui 接入后的日常使用”，帮助你稳定执行 i18n 命令链路并快速排障。
如果你需要的是“初始化/脚手架接入”，请使用 lingui-next-init，不要混用职责。
Before using this skill, confirm your project already has Lingui runtime setup:
scripts/i18n/* exists (at least index.ts, cli.ts, manifest.ts).["@lingui/swc-plugin", {}].src/locales/** catalogs and src/i18n/catalog-manifest.ts flow are already wired.推荐最短日常流程（新增/修改文案）：
pnpm --filter @your/web run i18n:extract
pnpm --filter @your/web run i18n:translate
pnpm --filter @your/web run i18n:compile
高频补充命令：
pnpm --filter @your/web run i18n:bootstrappnpm --filter @your/web run i18n:manifestpnpm --filter @your/web run i18n -- --compilepnpm --filter @your/web run i18n:check| 命令 | 作用摘要 | 可用参数 |
|---|---|---|
i18n:extract | 提取源码文案到 po | — |
i18n:translate | 统计缺失翻译 | --fill-source, --strict |
i18n:check | 严格翻译检查，缺失即报错退出 | — |
i18n:compile | 编译 po 到 mjs，并自动执行 i18n:manifest | — |
i18n:manifest | 基于现有 mjs 生成 catalog-manifest.ts | — |
i18n:sync | 当前仅等价 i18n:extract | — |
i18n:bootstrap | 一次执行 extract + compile(+manifest) | — |
i18n | 组合入口；默认 extract + translate，加 --compile 才会编译 | --compile, --fill-source, --no-translate, --strict |
详细输入/输出/副作用请看 references/i18n-commands.md。
When command semantics change, docs must be updated in the same change set.
Trigger files:
apps/web/scripts/i18n/index.tsapps/web/scripts/i18n/manifest.tsapps/web/scripts/i18n/cli.tspackages/i18n/src/lingui-config.tsRequired doc sync:
references/i18n-commands.mdreferences/workflow-daily.md (if execution sequence changed)references/maintenance-playbook.md (if maintenance workflow changed)i18n 默认会 compile。
实际：默认不会，必须显式传 --compile。
i18n:sync 是全量同步命令。
实际：当前实现仅执行 extract。
i18n:manifest 可替代 i18n:compile。
实际：manifest 依赖已有 .mjs，不会自行生成编译产物。
只在 [lang]/layout.tsx 做初始化就够了。
实际：在 Next App Router / RSC 下，服务端 page.tsx 也应在使用 t 或生成 metadata 前初始化 locale。
遇到以下错误时按顺序检查：
Lingui: Attempted to call a translation function without setting a locale
initLingui(locale) 是否执行了 i18n.activate(locale)。layout.tsx 与服务端 page.tsx 是否都调用了 initPageLingui(params)（或等价逻辑）。useLingui/Trans，避免依赖全局 @lingui/core/macro t 的初始化时序。i18n:compile 后的 manifest 是否包含对应 entry + locale loader。extract -> translate -> compile。translate 输出缺失项为预期状态（已补翻或接受占位）。build 脚本含 compile gate）。.gitignore 已忽略编译产物 web/src/locales/**/*.js|*.mjs（及兼容路径）。references/i18n-commands.mdreferences/workflow-daily.mdreferences/maintenance-playbook.mdapps/web/scripts/i18n/index.tsapps/web/scripts/i18n/manifest.ts