Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

operately/operately
See how to install

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

clean-code

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

components-architecture

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

ecto-migrations

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

help-docs

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

mcp-tools

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

tanstack-query

Free

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.

The English summary is being prepared. Showing the original description.

operately/operately587Updated Oct 17, 2026

See all skills by operately

Report a problem with this skill