跳到正文
cccskills
免费在 GitHub 公开

internationalization

Maintain Operately translations when adding or changing user-visible copy, fixing missing translations, or adding a supported language. Covers shared Gettext/i18next catalogs, glossaries, generation, and completeness checks; excludes translating user-authored content or general prose outside the product.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md1.7 KB
  • references/adding-a-language.md7.3 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Internationalization

References

Read the reference for the current task before making changes. Keep detailed workflows in the linked guide and skill reference.

  • Copy changes or missing translations: follow the developer guide and its linked language glossaries.
  • Adding a language: also read Adding a language. Follow its glossary-first sequence, registration checklist, commands, and verification steps.

Essential rules

  • Hardcoded system-authored, user-visible copy is forbidden. Use the existing translation wrappers and supply translations for every supported language.
  • Edit PO files, regenerate catalogs/resources, and run make test.i18n plus focused tests. Never edit generated JSON. Completeness checks do not replace the review described in the guides.
  • Preserve user content, machine identifiers, escaping, English defaults, and existing locale behavior. Keep changes within the requested scope.
  • Native-speaker review is recommended when available for glossaries, new languages, and routine copy changes. It is optional: do not block translation, merge, or release, or raise review findings solely because native-speaker approval or review metadata is absent. AI may draft terminology and translations; only claim native-speaker review when it actually occurred.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work test-first or do TDD, or otherwise raise code quality, readability, and maintainability. Also use when writing or reviewing Operately APIs or Ecto queries. Apply these rules by default when producing or changing code for a quality-conscious user.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

Defines where UI components belong in Operately (TurboUI-first). Use when creating, changing, reviewing, or migrating UI components, adding features that need UI, or deciding whether to refactor legacy app UI in app/assets/js/components or app/assets/js/features. Covers pure TurboUI components, component reuse, the app bridge pattern, and legacy migration scenarios.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change_*.ex). Use when adding, renaming, reviewing, or generating database migrations, ecto.gen.migration, Operately.Data.Change* modules, backfills, schema_migrations version collisions, mix ecto.migrate, or make gen.migration.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

help-docs

免费

Discover help documentation work from operately git history. Use when the user asks to audit what needs documenting since a release, tag, or SHA, or to identify documentation gaps from code changes. Requires a baseline SHA or tag as input.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

mcp-tools

免费

Defines how to add Operately MCP tools (API-first wrappers). Use when creating, changing, or reviewing MCP tools under app/lib/operately_web/mcp/tools/, when the user mentions MCP tools, tool catalog, @expected_tool_names, or when exposing a new Operately capability to ChatGPT/Claude MCP clients.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

Operately frontend data fetching with TanStack Query. Use when adding or changing page loaders, model hooks, Api.* calls, mutations, useLoadedData, Pages.useRefresh, or any web UI backend request. New code must use TanStack. When fixing or extending an existing surface, migrate that surface's API calls to TanStack in the same change.

中文简介正在准备中。当前显示原文说明。

operately/operately5872026年10月17日 更新

查看 operately 的全部技能

报告此技能的问题